Core Primitive
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.
Strategy is not a document
Henry Mintzberg spent three decades challenging the conventional view of strategy as a deliberate plan. In his landmark study of strategic management, Mintzberg distinguished between "intended strategy" (the plan leadership articulates) and "realized strategy" (the pattern of decisions the organization actually makes). He found that realized strategy often diverges significantly from intended strategy — not because execution fails, but because the plan cannot anticipate the stream of decisions that the organization faces daily. What determines the realized strategy is not the plan but the mental model — the schema — through which decision-makers interpret situations and evaluate options (Mintzberg, 1994).
This is why organizations with brilliant strategic plans can execute poorly, and why organizations with simple strategic frameworks can execute brilliantly. The plan is a document that sits on a shelf or a wiki. The schema is a mental model that lives in people's heads and shapes their decisions in real time, without reference to the document. When an engineer decides which feature to build next, when a sales rep decides which prospect to prioritize, when a support agent decides how to handle an unusual request — these micro-decisions are not informed by the strategic plan. They are informed by the strategy schema: the decision-maker's mental model of what the organization values, who it serves, and how it wins.
Roger Martin and A.G. Lafley made this point operational in Playing to Win, where they defined strategy as a set of integrated choices that establish a unique and valuable position. The key word is "integrated" — the choices must cohere into a system where each choice reinforces the others. This coherence is what a schema provides. A strategy schema is not a list of choices but a mental model of how the choices relate to each other and to the organization's purpose. When the schema is clear, every member can see how their individual choices contribute to the organizational pattern. When the schema is unclear, individual choices are locally rational but globally incoherent (Lafley & Martin, 2013).
The strategy-as-schema framework
Viewing strategy as a schema rather than a plan changes how you create, communicate, and maintain strategic direction.
A strategy schema is a model, not a list. A strategic plan lists objectives, initiatives, and metrics. A strategy schema describes the causal model — the theory of how the organization creates value. "We win because we do X, which enables Y, which our customers value because of Z." The causal model is what enables distributed decision-making: when a team lead faces an unexpected choice, they can reason through the model rather than searching for a relevant directive in the plan.
Richard Rumelt argued that the core of good strategy is a "kernel" consisting of three elements: a diagnosis (what is the challenge?), a guiding policy (what is our approach to the challenge?), and coherent actions (what specific actions follow from the approach?). The guiding policy is the strategy schema — the mental model that connects the diagnosis to the actions. Without this connecting model, strategy degenerates into a list of goals (aspirations without a theory of how to achieve them) or a list of actions (activities without a theory of why they will work) (Rumelt, 2011).
A strategy schema must be shareable. The most elegant strategy is worthless if it exists only in the CEO's head. The purpose of articulating strategy as a schema is to make it transmissible — to enable every member of the organization to internalize the same mental model and use it to make locally coherent decisions. This means the schema must be simple enough to remember, specific enough to guide action, and clear enough to resolve ambiguity.
The test of a shareable strategy schema is not "Can you recite it?" but "Can you use it to make a decision the leadership team would agree with, in a situation the strategy document does not address?" If team leads consistently make decisions that leadership would endorse without leadership's involvement, the strategy schema is effectively shared. If team leads regularly make decisions that leadership overrules, the schema is either unclear or unshared.
A strategy schema makes tradeoffs explicit. Michael Porter's foundational insight was that strategy is fundamentally about tradeoffs — about what the organization chooses not to do. "The essence of strategy is choosing what not to do," Porter wrote. A strategy schema makes these tradeoffs visible by defining the organization's priorities in terms of "more X, less Y" rather than "all of the above." "We prioritize speed over polish" is a strategy schema. "We value both speed and polish" is not — it provides no guidance when speed and polish conflict, which is when strategic guidance is most needed (Porter, 1996).
How strategy schemas fragment
Even when an organization establishes a clear strategy schema, it tends to fragment over time through predictable mechanisms.
Interpretation drift. Different functions interpret the strategy schema through their functional lens. "Customer-centric" means different things to sales (close deals customers want), product (build features customers need), engineering (build systems that serve customers reliably), and support (resolve customer issues quickly). Each interpretation is reasonable. Each is incomplete. Over time, the functional interpretations diverge further, and the organization loses strategic coherence — not because anyone rejected the strategy but because each function adapted the schema to fit its own context.
Growth dilution. As the organization grows, new members learn the strategy schema through secondhand transmission — from their manager, their team, their onboarding documents — rather than from the original context that produced it. Each transmission introduces small distortions. After several generations of transmission, the schema that new members hold may differ significantly from the schema the leadership team intended. Patrick Lencioni observed that organizational alignment degrades logarithmically with communication distance — each layer between the source and the recipient halves the fidelity of the message (Lencioni, 2012).
Success amnesia. When the strategy works, the organization forgets why it works. The behaviors that the strategy schema produces become habitual — people do them without referencing the schema. When the environment changes and the behaviors need to change, the organization has lost access to the reasoning behind the behaviors. It knows what it does but no longer knows why it does it, which makes adaptation difficult because the organization cannot distinguish between behaviors that remain adaptive and behaviors that have become obsolete.
Schema bloat. Organizations tend to add strategic priorities without removing existing ones. Each annual planning cycle adds new initiatives, new focus areas, new strategic pillars — without retiring the old ones. Over several cycles, the strategy schema becomes overloaded: it says the organization values everything, which means it provides guidance about nothing. Jim Collins emphasized that a strategy's power comes from its constraints — from what it excludes rather than what it includes. A strategy that includes everything is not a strategy (Collins, 2001).
Maintaining strategy schema clarity
Keeping the strategy schema clear and shared requires ongoing practice, not a one-time exercise.
The hallway test. Periodically stop random employees at different levels and functions and ask: "What is our strategy?" Not "What are our goals?" or "What are you working on?" but "How does this organization win?" The hallway test reveals the actual state of the strategy schema across the organization. If the answers are consistent, the schema is shared. If the answers vary wildly, the schema has fragmented.
Decision audits. Review recent decisions through the lens of the strategy schema. For each decision, ask: "Was this decision consistent with our strategy? If not, was the inconsistency deliberate (a conscious exception) or unconscious (a schema failure)?" Decision audits reveal whether the strategy schema is actually guiding behavior or merely decorating presentations.
Tradeoff exercises. Regularly present the organization with real or hypothetical tradeoffs that the strategy schema should resolve. "We can ship this feature fast with technical debt, or slow with clean architecture. Which does our strategy say to choose?" If the answer is clear and consistent across the organization, the schema is working. If the answer is ambiguous or contested, the tradeoff has exposed a gap in the schema that needs to be addressed.
The Third Brain
Your AI system can help you develop, test, and maintain strategy schemas. Share your organization's current strategic materials — the plan, the pitch deck, the investor narrative — with the AI and ask: "What is the strategy schema embedded in these materials? State it as a single causal model: 'We win by doing X because Y.' Is the causal model clear, or are there ambiguities and contradictions?"
The AI can also stress-test your strategy schema against specific decisions: "Our strategy schema says [X]. Here is a decision we face: [description]. What does the schema say we should do? If the answer is ambiguous, what element of the schema needs to be clarified?" This exercise reveals gaps in the schema before they produce incoherent decisions.
For ongoing strategy schema maintenance, use the AI to perform the hallway test at scale: share the strategy schema and then present a series of hypothetical scenarios across different functions. "A product manager faces [scenario]. An engineer faces [scenario]. A sales rep faces [scenario]. In each case, what does the strategy schema prescribe?" If the AI identifies scenarios where the schema is ambiguous or contradictory, those are the scenarios where your organization's real-world decision-making will be inconsistent — and therefore the scenarios where the schema needs refinement.
From strategy to process
Strategy is the highest-level organizational schema — the mental model that describes how the organization creates value. But strategy must be translated into action through a second type of schema: process. Process schemas encode the organization's model of how work should flow, how decisions should be made, and how quality should be ensured.
The next lesson, Process is an organizational schema, examines how standard operating procedures and workflows function as organizational schemas — codified mental models that determine how the organization converts strategic intent into operational reality.
Sources:
- Mintzberg, H. (1994). The Rise and Fall of Strategic Planning. Free Press.
- Lafley, A. G., & Martin, R. L. (2013). Playing to Win: How Strategy Really Works. Harvard Business Review Press.
- Rumelt, R. P. (2011). Good Strategy Bad Strategy: The Difference and Why It Matters. Crown Business.
- Porter, M. E. (1996). "What Is Strategy?" Harvard Business Review, 74(6), 61-78.
- Lencioni, P. (2012). The Advantage: Why Organizational Health Trumps Everything Else in Business. Jossey-Bass.
- Collins, J. (2001). Good to Great: Why Some Companies Make the Leap and Others Don't. HarperBusiness.
Frequently Asked Questions