What goes wrong when you ignore that making organizational schemas explicit?

The most common reason fails: Treating schema surfacing as an intellectual exercise rather than a practical intervention. An organization that surfaces its schemas but does not decide what to do about them has created awareness without change — and awareness without change produces cynicism. ('We had a big workshop about our assumptions, and then nothing happened.') Every schema surfacing exercise should conclude with a decision: For each surfaced schema, is it (a) accurate and adaptive — keep it, (b) outdated but harmless — acknowledge it, or (c) outdated and costly — commit to revising it. Without this decision step, the surfacing exercise is organizational navel-gazing.

The fix: Run a schema surfacing session with your team or leadership group. Choose one strategic question the organization is currently debating. Ask each participant to independently write answers to three prompts: (1) 'I believe the fundamental challenge we face is...' (2) 'I believe the right approach to this challenge is...' (3) 'I believe we will know we have succeeded when...' Collect and compare the answers anonymously. The divergences reveal where organizational schemas differ — and the convergences reveal where schemas are so deeply shared that they may be operating as unexamined assumptions. For each convergence, ask: 'Is this belief a fact we have evidence for, or an assumption we have not tested?' Document the assumptions. This is the beginning of a schema inventory.

The underlying principle is straightforward: Surfacing and documenting the organization's shared assumptions is the first step to improving them. The practice of making schemas explicit transforms invisible forces into visible choices — choices that can be examined, tested, and deliberately maintained or revised.