What does it mean that making organizational schemas explicit?

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.

Example: A B2B SaaS company had struggled for two years to enter the enterprise market despite strong product-market fit with mid-market customers. Three attempts at enterprise sales had failed. The CEO, Priya, commissioned a schema surfacing exercise with her leadership team. She asked each of the seven leaders to independently complete the sentence 'We believe that our ideal customer is...' and 'We believe that enterprise sales requires...' The responses revealed the problem. Six of seven leaders described the ideal customer as 'a technical buyer who evaluates our product on its merits' — a schema formed during the company's developer-led growth phase. Only the new VP of Sales described the ideal customer as 'an executive buyer who evaluates our product on business outcomes.' Similarly, six of seven described enterprise sales as requiring 'a better product and more features.' The VP of Sales described it as requiring 'executive relationships, business case development, and procurement process navigation.' The company did not have an enterprise sales problem. It had an organizational schema problem. Its schema of how sales works — built during a period when technical buyers found the product and bought it without a traditional sales process — was incompatible with enterprise procurement. The solution was not a new sales playbook or more enterprise sales reps. It was a new organizational schema: a revised shared mental model of how the company creates value for enterprise customers. Making the existing schema explicit was the prerequisite. Until the leadership team could see the schema they were operating from, they could not see why their enterprise attempts kept failing.

Try this: 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.