What does it mean that strategy is an organizational schema?

A strategy is not a plan or a set of goals. It is a shared mental model of how the organization creates and captures value — a schema that tells every member what to prioritize, what to ignore, and how their work connects to the organization's purpose. When the strategy schema is clear and shared, the organization acts with coherence. When it is vague or fragmented, even talented people pull in contradictory directions.

Example: A growth-stage software company had a sixty-page strategic plan, updated annually, presented at an all-hands meeting, and posted on the company wiki. The plan covered market analysis, competitive positioning, product roadmap, financial projections, and organizational initiatives. It was thorough, data-driven, and largely unread. When the VP of Product, Marcus, asked twelve team leads to independently answer 'What is our strategy?' he received twelve different answers. Three said 'Be the market leader in our category.' Two said 'Build the best product.' Two said 'Grow revenue to prepare for an IPO.' Three said 'Expand into enterprise.' Two could not articulate the strategy at all. The sixty-page plan contained all of these elements, which was precisely the problem: it described everything the organization was doing without establishing a shared mental model of why it was doing those things or how they connected. Marcus replaced the sixty-page plan with a single strategic statement: 'We win by making [category] so easy that non-technical teams can do it without IT support. We prioritize ease of use over feature depth, mid-market over enterprise, and self-serve over sales-assisted.' The statement was not a plan — it was a schema. It told people what to prioritize (ease of use), what to deprioritize (feature depth), and who the organization existed to serve (non-technical mid-market teams). When a product decision arose, every team lead could apply the schema independently and arrive at the same answer. The organization's decision quality improved not because the decisions were centralized but because the shared schema enabled distributed decisions that were coherent.

Try this: Write your organization's strategy as a single schema statement — not what the organization does, but what it believes about how it creates value. Use this format: 'We win by [doing X] for [audience Y] in a way that [differentiator Z].' Then ask two colleagues to write the same statement independently. Compare the three statements. Where they converge, the strategy schema is shared. Where they diverge, the strategy schema is fragmented — and the divergence tells you exactly where the organization's strategic confusion lives.