What goes wrong when you ignore that strategy is an organizational schema?

The most common reason fails: Confusing a strategic plan with a strategy schema. A plan is a list of actions. A schema is a mental model. An organization can have a detailed plan — 'Launch product A in Q2, expand to Europe in Q3, hire 50 engineers by year-end' — without having a strategy schema. The plan tells people what to do. The schema tells people how to think. Without the schema, people follow the plan mechanically when it applies and improvise randomly when it does not. With the schema, people can make coherent decisions in situations the plan did not anticipate — which is most situations, because plans cannot anticipate the future with precision.

The fix: 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.

The underlying principle is straightforward: 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.