An Operating System for Strategy

The Problem. Most organizations do not actually have a strategy. They have goals, plans, initiatives, and lists of priorities. When results disappoint, leaders blame execution. The diagnosis is wrong, and so is the cure.

The Cause. Strategy fails because the discipline itself is poorly understood. Leaders treat it as a document, a framework, or an annual offsite. They have rarely been taught how to do strategy as a systematic capability. They reach for the framework that worked last time, and improvise the rest.

The Path Forward. Better strategy requires a complete operating system: a shared definition, a structured way to make strategic choices, a process for designing and updating strategy continuously, an honest reading of context, and the underlying capabilities of strategic thinking and strategic leadership. The five components are not optional. The weakest of them sets the ceiling on what strategy can do.

Strategy failure rates have been stuck above 70 percent for decades. The conventional explanation — that execution is the problem — has produced a generation of execution frameworks, scorecards, and discipline programs, with no measurable improvement in outcomes.

The deeper problem is that most organizations do not have a strategy at all. They have a list of priorities, a set of goals, or a plan, and they call it strategy. Weak strategies lead to poor execution, not the other way around.

Even when leaders try to do strategy properly, they encounter a fragmented field. Each framework offers a slice of the problem. Each thought leader emphasizes a different dimension. None of them, taken alone, equips a leadership team to do strategy as a systematic, continuous practice.

The Better Strategy OS is an attempt to integrate that fragmented field into a single coherent system. It rests on five components: a clear definition of strategy, a structured framework for making strategic choices, a systematic process for designing and adapting strategy, a disciplined reading of context, and the underlying capabilities of strategic thinking and strategic leadership. This article walks through why each component is required, what happens when it is missing, and how the five fit together.

Get the pdf

The dominant explanation for why strategies fail is that they were poorly executed. The plan was sound. The thinking was clear. The organization simply could not carry it through. The conclusion that follows is intuitive: the answer to weak results lies in tighter implementation, sharper accountability, more disciplined follow-through.

This explanation is wrong in most cases. And the cost of getting it wrong is enormous.

What organizations call strategy frequently isn’t one. It is a list of priorities, a set of goals, a five-year plan, or a slide deck of initiatives. The artifacts look like strategy, the processes that produce them feel like strategy, and the language used to discuss them borrows from strategy. But the substance is missing. There is no clear diagnosis of the central challenge, no coherent approach to overcoming it, and no real choices about what the organization will and will not do. When the results disappoint, leaders default to the explanation closest to hand: execution failed. The strategy itself is rarely interrogated.

The data tells a different story. In a recent strategy& survey, executives reported that their own organizations’ strategies were not bold enough, not differentiated enough, not clear enough, not adequately resourced, and not translated into action. These are not execution problems. They are design problems. The strategy was weak before anyone tried to execute it.

A second pattern compounds the first. Most senior leaders have never been taught how to do strategy. A study of 10,000 executives found that only a third had received any formal training in setting strategy. Strategy is treated as a capability that emerges from experience, intuition, or seniority — not as a discipline that has to be learned. Leaders are promoted into roles that require them to set direction, and they improvise. The MBA covered some classics. The consulting firm offered a framework. Beyond that, the practice is largely self-taught.

The cost of this gap is not abstract. Boards consistently rank strategic thinking as the single most important capability they look for in CEO candidates. Across 250,000 leaders, McKinsey found that setting strategic direction is the most important role of any senior leader. And yet only thirteen percent of managers report feeling confident making strategic decisions under uncertainty. The gap between what organizations need from their leaders and what those leaders have been equipped to do has become the central problem in strategic management — and the one most consistently misdiagnosed.

The argument of this article is that better strategy will not come from another framework. It will come from treating strategy as what it actually is: a system. An operating system, in the same sense that an organization runs on an operating system. That system has five components, each necessary, none sufficient on its own. We call it the Better Strategy OS.

Before introducing the system, we have to be precise about what is breaking. In our work with leadership teams over the past two decades, four distinct failure modes recur. Most organizations exhibit at least two of them at any given time. We call them the four killers of strategy.

The first and most common failure is that the strategy itself is weak. It does not identify the central challenge facing the organization. It does not commit to an approach for overcoming that challenge. It does not make the trade-offs that real strategy requires. What passes for strategy is, in most cases, a list of initiatives or a set of aspirational goals.

A recent example illustrates the pattern. A leadership team we worked with had received a strategy presentation from one of Europe’s better-known management consultancies. The deck was professional. The analysis was thorough. The recommendations were clear. And the document, on close reading, contained no strategy at all.

The slide labelled “Strategy” listed three top priorities: grow selected services, strengthen sales, leverage efficiency potentials. Underneath each priority sat a list of initiatives. Each initiative had been scored for impact and ease of implementation. The leadership team had been asked to approve or reject each item. They approved almost all of them.

What was missing was any answer to the strategic questions. What is the central challenge this organization needs to overcome? Why are these the right priorities, rather than three different ones? What is the underlying logic that makes these initiatives reinforce each other? What are we choosing not to do? The deck did not address these questions, because the consultancy had not been engaged to answer them. It had been engaged to produce a list. And a list, however well-presented, is not a strategy.

Strategy Myth: “We have a strategy because we have priorities.” Goals, priorities, and initiatives are inputs to strategy or outputs of it — not strategy itself. Strategy is the coherent approach that explains why these priorities, in this order, with this logic. Without the underlying approach, a list of priorities is just a list.

Richard Rumelt has argued that good strategy is rare, and that what is most often called strategy is some combination of goal-setting, motivational language, and operational planning. Our experience confirms this. Across hundreds of engagements, we have found that weak strategy is the rule, not the exception. And weak strategies lead to poor execution. They cannot be rescued by better follow-through.

Diagnosing whether what you have qualifies as strategy at all is its own discipline. We have developed a structured way to do that — evaluating strategy across three dimensions of quality — which we describe in detail in this article:

The second failure mode is that the process for doing strategy is itself broken. Most organizations approach strategy as a periodic event: an offsite, a quarterly review, an annual planning cycle. The process produces a document. The document is presented, filed, and forgotten until the next cycle.

This approach made sense in stable industries with predictable competitive dynamics. It does not work in environments where the assumptions underlying the strategy have to be tested, refined, and updated continuously. And it produces two specific problems that we see repeatedly in client work.

The first is low ownership. When strategy is developed at the top and handed down, the people who have to live with its consequences feel little obligation to it. They were not consulted, they did not contribute to the diagnosis, and they cannot easily explain why this strategy rather than another. When circumstances change, they default to their own judgment, because the strategy was never really theirs.

The second is poor translation. Even when the corporate or business strategy is sound, organizations struggle to translate it into the daily decisions of teams and functions. The strategy lives in the deck. Daily work proceeds according to its own logic. The two never quite meet.

Both problems are process failures. They are solvable, but only if the process is treated as part of the strategy itself rather than as a separate operational matter.

The third failure mode is leadership behavior. Even a well-designed strategy, embedded in a sound process, can fail if the leaders responsible for it do not consistently lead by it. Strategic leadership is the practice of providing direction, shaping the environment, and mobilizing people so that everyday decisions consistently support the strategy.

The failure mode here is subtle. The strategy exists. The process is in place. But in board meetings, capital allocation decisions, hiring choices, and resource trade-offs, leaders behave as if the strategy did not exist. They re-litigate decisions that the strategy already settled. They fund initiatives that contradict the chosen direction. They protect parts of the organization that the strategy implied should be wound down.

When this happens, the rest of the organization concludes — correctly — that the strategy is decorative. People stop referring to it. Local managers revert to local logic. Execution drift becomes the operating norm. The strategy formally exists. It does not actually live anywhere.

The fourth failure mode is more personal. Strategic thinking is the cognitive capability to diagnose complex situations, make consequential choices under uncertainty, and determine what truly matters under constraint. It is the foundation on which every other element of strategy depends. And it is, by a wide margin, the capability most consistently underdeveloped in senior leaders.

The data here is striking. Eighty-two percent of hiring managers identify strategic thinking as the number one leadership skill gap when hiring senior leaders. Boards consistently rank it as the top capability they look for in CEO succession. And yet, two-thirds of organizations report lacking a coherent set of frameworks for thinking about strategy at all. Leaders are expected to think strategically, are evaluated on whether they think strategically, and have rarely been taught what strategic thinking actually involves.

The result is a particular kind of failure. Smart, capable leaders gather, deliberate, and produce a strategy. The strategy is internally consistent. It uses the right vocabulary. It looks like strategy. But it has not been pressure-tested by the kind of disciplined thinking that real strategy requires. The diagnosis is shallow. The trade-offs are avoided. The alternatives have not been seriously considered. And the result, predictably, fails to produce the outcomes that were promised.

These four killers are not independent. Weak thinking produces weak content. Weak leadership corrupts strong content during execution. Weak process amplifies weak thinking by failing to challenge it. They reinforce each other, and they have to be addressed together. No amount of work on any single dimension will fix a system in which the others are broken.

If the four killers describe the problem, the question becomes what to do about it. The answer is not another framework. The field already has more frameworks than any leader can use. The answer is integration: treating strategy as a system rather than a collection of techniques, and building the system the discipline actually requires.

We call that system the Better Strategy OS.

The Better Strategy OS is built on five components. Each addresses one of the four killers, with strategic thinking and leadership treated together as the meta-layer that makes the other four possible. The components are:

1. A clear, universal definition of strategy.

2. A structured framework for making strategic choices.

3. A systematic process for doing strategy continuously.

4. A disciplined reading of context.

5. The underlying capabilities of strategic thinking and strategic leadership.

The components are sequential in logic but operate simultaneously in practice. A leadership team using the OS does not work through them in order; it works across them at the same time, using each to test and sharpen the others.

The five components rest on a deeper structural distinction in strategy: between the content of a strategy (the what of strategy), the process by which it is made (the who and how of strategy), and the context in which it operates (the where of strategy). The OS addresses content through its first two components, process through the third, and context through the fourth. We explore the implications of that underlying architecture in:

Most strategy conversations break down within the first ten minutes. Not because participants disagree about the answer, but because they disagree about the question. Five executives in a room will offer five different definitions of strategy, often without realizing they are doing so. One thinks of strategy as long-term planning. Another thinks of it as competitive positioning. A third treats it as resource allocation. A fourth conflates it with goal-setting. The conversation proceeds as if everyone is working on the same problem, and the resulting strategy is incoherent because no one was ever clear about what strategy actually is.

Better strategy starts with a shared definition. The definition we use, drawn from Rumelt and others before him: strategy is the coherent approach an organization uses to overcome the key challenges that stand between its current situation and its ambitions.

Three things make this definition useful. First, it is universal. It works for business strategy, corporate strategy, functional strategy, be it HR strategy, IT strategy, Cybersecurity strategy, etc., and also outside the business realm, personal strategy, military strategy, and public policy. An organization that uses one definition for marketing strategy, another for HR strategy, and a third for corporate strategy has no shared language across the disciplines at all. A universal definition forces consistency.

Second, it is challenge-based. It treats strategy as a response to a real problem rather than as a planning exercise. If there is no challenge — no obstacle between current state and ambition — there is no need for strategy. A plan will do. The challenge orientation forces leaders to identify what specifically they are trying to overcome, and that single act of clarification often reveals the gap between what an organization claims to be doing strategically and what it is actually doing.

Third, it is operational. It produces a clear test. Any strategy can be evaluated by asking four questions: What is the ambition? What is the challenge that stands between us and that ambition? What is our coherent approach to overcoming the challenge? What actions follow from that approach? A strategy that cannot answer these questions is not a strategy. It is something else, possibly useful, but not strategy.

Important Distinction. Ambitions are what an organization wants to achieve. Challenges are what stands in the way. Strategy is the approach to overcoming the challenges. Actions are what the approach commits the organization to do. Conflating these — as most strategy documents do — is the single most common source of strategic confusion.

What does this definition mean for business strategy? While every organization will face its own challenges, there’s a set of universal strategic challenges and choices that each company must make. For that, leaders need a framework that organizes the decisions strategy actually requires — and recognizes that those decisions differ depending on the level at which strategy is being made.

Strategy operates at four distinct levels. At each level, the strategic question is different, the choices are different, and the tools for making those choices are different. Treating all four as the same conversation is one of the most common sources of confusion in strategy work.

Network strategy operates at the highest level of aggregation. The question is where the organization should compete and where it should cooperate. Airline alliances offer a clear example: airlines that compete on most routes choose to cooperate on others, sharing booking systems, codeshares, and frequent flyer programs. The strategic question at this level is the structure of inter-firm relationships.

Corporate strategy operates at the group level. The question is which businesses the organization should be in and how to manage them. The Lufthansa Group has decided to be in passenger airlines, aviation services, and business functions. Some years ago, it decided to exit private jets, on the reasoning that private jet customers tended to fly point-to-point rather than feeding into long-haul flights, eliminating the synergy that justified being in the business. That is a corporate strategy choice: which businesses to be in, which to exit, how the portfolio reinforces itself.

Business strategy operates at the level of an individual business or operating unit. The question is how to compete and win in a specific market. Within the Lufthansa Group, the strategy for Lufthansa Airlines (premium experience, multi-hub-and-spoke) differs sharply from Eurowings (value carrier, point-to-point), which differs again from Lufthansa Cargo or Lufthansa Technik. Each business needs its own strategy, made on its own terms, even though they sit under the same corporate umbrella.

Functional, departmental, or team strategy operates at the most granular level. The question is how to align the function’s activities and resources with the business strategy above it. Lufthansa Airlines’ premium experience strategy requires specific functional choices: a redesigned in-flight product, a renewed app experience, a new on-board service offering. Functional strategy is what makes business strategy real.

At the Better Strategy School, each level uses its own canvas. The Business Strategy Canvas asks where and how to compete. The Corporate Strategy Canvas asks different questions about portfolio configuration. The Network Strategy Canvas focuses on cooperation versus competition. The Functional Strategy Canvas focuses on alignment to the level above.

The framework is not a checklist. It is a discipline. When a strategy conversation drifts — and they almost always do — the framework lets the leadership team locate themselves: which level are we discussing, which choices are on the table, which canvas applies. That single act of orientation is often the difference between a strategy session that produces clarity and one that produces a longer list.

Most organizations approach strategy as an event. The leadership team gathers once a year, typically off-site, and produces a document. The document goes into a binder. The binder goes onto a shelf. Eleven months later, the cycle repeats.

This approach has a name in classical strategy: think, then do. It assumes a clear separation between formulation and implementation. The strategists think; the rest of the organization executes; the cycle repeats annually. It works, in theory, when the environment is stable enough that the strategy designed in January is still appropriate in November.

For most of our clients, those conditions no longer hold. Markets shift faster than annual cycles. Customer behavior changes mid-quarter. Competitive moves arrive without warning. A strategy that cannot be tested, refined, and updated continuously becomes obsolete before the binder gathers dust.

The alternative we recommend is what we call think-while-doing. The core idea is that strategy is a continuous learning process, not a periodic planning event. The leadership team starts with a strategic hypothesis — a coherent approach to a defined challenge — and immediately puts that hypothesis into action. They observe what happens. They make sense of the signals. They update the approach. Then they repeat.

This sounds informal. It is not. The think-while-doing process has a clear architecture, which we call the Strategy Launchpad:

• Align on the current reality. What is happening in the company, in the market, in the environment? This is shared diagnosis, not data dump. The goal is a leadership team that sees the situation in roughly the same way.

• Define the challenge. Out of that shared diagnosis, identify the central challenge that strategy must address. Not all problems are strategic, and not all strategic challenges are equally urgent.

• Design strategy options. Develop two or three coherent approaches to overcoming the challenge. Strategy as a single answer is rarely strategy; strategy as a choice between alternatives is.

• Test and validate. Pressure-test each option against evidence, against the framework, against the four-killers diagnostic. Choose the approach that survives.

• Activate. Strategy that is announced is not strategy that is alive. Activation requires translation into the language of teams and functions, alignment of incentives, and the rhythm of decision-making that keeps the strategy in front of leaders rather than behind them.

• Live the strategy. Execution is not a separate phase. It is the ongoing work of making the strategy real, adapting as evidence comes in, and updating the approach when the environment shifts.

The client we mentioned earlier provides a useful illustration. Their original strategy committed to a self-service media platform for medium-sized broadcasters. Six months in, evidence accumulated that the self-service model was too complex for the target customer to adopt without support. The core direction — focusing on medium-sized broadcasters with limited technical capability — remained correct. What changed was the operating model: from self-service to assisted setup. The strategy did not change. The approach to delivering the strategy did. That distinction — direction stable, delivery adaptive — is what think-while-doing produces, and what an annual planning cycle cannot.

Concept Clarification: Always-On Strategy. Treating strategy as a continuous practice rather than an annual event does not mean abandoning structure. It means building a different structure: one in which the cadence of review, the discipline of evidence-gathering, and the willingness to update the approach are designed into the operating rhythm of the leadership team. The annual offsite is replaced by a permanent operating system.

A strategy that ignores its context is not a strategy. It is a wish.

Every strategic choice operates within a set of conditions that shape what is possible, what is hard, and what is foolish. Those conditions are not fixed — context can be shaped, as Napoleon reminded his generals — but they cannot be ignored. The leadership team that designs a strategy as if context did not exist produces a strategy that cannot survive contact with reality.

We organize context along four dimensions:

Industry context. What are the structural dynamics of the industry the organization operates in? How is it changing? What does the trajectory of suppliers, buyers, competitors, substitutes, and potential entrants look like over the relevant horizon? Industry analysis is not a one-time exercise; it is a continuous reading of how the competitive landscape is evolving and what that evolution implies for strategic choice.

Organizational context. What are the internal conditions — culture, structure, capabilities, processes, systems, resources — that the strategy will have to work with or work against? An organization with a deeply embedded operational excellence culture will struggle to execute a strategy that depends on rapid experimentation, regardless of how well that strategy is designed. Reading organizational context honestly is one of the harder disciplines in strategy, because leaders are often blind to the conditions they live inside.

International context. How are international and geopolitical dynamics shaping the organization’s options? The conditions of the past three years — supply chain restructuring, geopolitical realignment, regulatory divergence — have made international context a first-order strategic variable rather than a footnote. Strategies designed for a globalizing world have to be re-examined against a world that is not.

Situational context. Beyond the structural conditions, what is the specific situation the organization is in right now? Is the environment stable enough to support a strategic planning approach, or is it volatile enough to require a strategy-as-learning approach? Are resources abundant or scarce? Is the leadership team aligned or fractured? The right strategic process for one situation is the wrong process for another.

The discipline here is honesty. Most leadership teams under-read context because reading it accurately would require them to confront uncomfortable conclusions about their own organization, their own industry, or their own assumptions. The OS forces that confrontation by treating context as a component of the strategy itself, not as a backdrop to it.

The four components above are organizational. They live in shared frameworks, shared processes, shared language. The fifth component is personal. It lives in the minds and behavior of individual leaders.

Strategy, strategic thinking, and strategic leadership are often used as synonyms. They are not. They operate at different levels and serve different functions, and conflating them is one of the most common sources of confusion in strategic management.

Strategy is the coherent approach the organization commits to. It resides in the organization as shared coordinating logic. Its function is to provide directional coherence across decentralized decisions. Without it, organizations are busy but directionless.

Strategic thinking is the cognitive capability that makes strategy possible. It resides in individual leaders. Its function is judgment and prioritization under uncertainty: diagnosing complex situations, identifying what matters most, recognizing trade-offs, evaluating implications. Without it, organizations produce activity without clarity.

Strategic leadership is the practice that makes strategy real. It resides in leadership behavior. Its function is to embed and sustain coordinated action: setting direction, designing governance, aligning incentives, shaping norms, mobilizing commitment. Without it, strategy exists on paper but not in behavior.

The three depend on each other in a specific sequence. Strategic thinking enables the design of good strategy. Strategy provides direction for the organization. Strategic leadership turns the direction into lived practice. An organization can have capable strategic thinkers and still produce an incoherent strategy, if the thinking is not channelled through a shared framework. It can have a coherent strategy and still fail to make it show up in daily decisions, if leadership behavior is inconsistent with the strategy. And it can have vigorous leadership activity and still lack any meaningful strategic direction, if there is no underlying strategy to lead.

Each of these failures is common. Each requires a different response. And each one points to the same conclusion: the OS is incomplete without the personal capabilities that animate it.

Developing strategic thinking and strategic leadership is its own subject. We have written separately about why these three concepts — strategy, strategic thinking, and strategic leadership — are routinely conflated, what each one actually is, and why the distinction matters for how organizations build the capability. That argument is laid out in:

For the purposes of this article, the point is structural: the four organizational components of the OS will not produce results if the leaders running them have not developed the personal capabilities the system depends on. The OS is a technology. Strategic thinking and strategic leadership are what make the technology useful.

The Better Strategy OS is not something a leadership team installs in a quarter. It is built over time, through repeated practice, in the actual work of designing and leading strategy. But the work has to start somewhere, and the place to start is diagnostic.

We recommend five moves.

Before building anything, locate the failure. Of the four killers, which is most active in your organization right now? Most leadership teams default to the assumption that execution is the issue. The diagnostic question is more specific: is the content weak, is the process weak, is the leadership behavior inconsistent, or is the underlying thinking shallow? In our experience, leadership teams discover that the killer they assumed was the problem is rarely the most damaging one. The first act of strategic discipline is an honest diagnosis of which component is broken.

The single most consequential change a leadership team can make is to stop using the word “strategy” loosely. Spend the time required to land on a shared definition — challenge-based, universal, operational — and then enforce it in every strategy conversation that follows. Conversations about goals, plans, priorities, and initiatives are useful, but they are not strategy conversations unless they connect explicitly to the underlying strategy. The discipline of language is the discipline of thought.

When a strategy conversation feels stuck, the most common cause is that the team is mixing levels. Corporate strategy questions get answered with business strategy logic. Business strategy questions get answered with functional strategy moves. The four-level framework forces orientation: which level is this conversation, which canvas applies, which choices are on the table. Tools matched to the level produce sharper conversations than tools applied generically.

Replace the annual strategy event with a continuous strategy practice. The transition does not require dismantling planning processes; it requires layering a different rhythm on top of them. Quarterly review of the strategic hypothesis. Monthly review of the evidence. Weekly review of the choices being made under the strategy. The cadence matters less than the principle: strategy is something the leadership team does continuously, not something it produces annually.

Strategic thinking and strategic leadership are capabilities, not personality traits. They develop through deliberate practice, structured exposure to multiple strategic perspectives, and feedback on actual strategic decisions. The leadership teams that produce the strongest strategic results, in our experience, are not the ones with the most charismatic individual leaders. They are the ones that treat the development of these capabilities as an ongoing organizational priority rather than as something that happens incidentally on the job.

These five moves are not a sequence. They are simultaneous. A leadership team that does all five — even imperfectly — operates differently from one that does none of them. The difference compounds over time, and it shows up in the quality of the strategy that the organization produces.

The argument of this article is that strategy fails for reasons that have very little to do with execution. It fails because the discipline itself has been treated as a collection of frameworks rather than as a system. Leaders pick the framework that resonates, ignore the others, and end up with strategy that is internally incoherent and externally fragile. The four killers describe the symptoms. The Better Strategy OS describes the system the symptoms point to.

That system has implications beyond any single organization. The decade ahead will be unforgiving for organizations that treat strategy as a periodic exercise. The pace of change in industries, technologies, and geopolitical conditions will continue to outrun annual planning cycles. The cost of weak strategy — of priorities without coherence, of plans without diagnosis, of execution without direction — will rise. The organizations that prosper will be the ones that have developed strategy as a practiced capability, not as a deliverable.

The question worth sitting with is not whether your organization has a strategy. Most organizations have something they call a strategy. The more consequential question is whether your organization has built the operating system that strategy actually requires — and whether the weakest of its five components is the one quietly determining your results.

Download the pdf of this article

Dr. Marc Sniukas is co-founder of The Better Strategy School. He has worked with leadership teams globally for more than two decades, helping leaders and organizations make strategy a genuine capability — developed through the real work of designing, executing, and continuously improving their actual strategy.

The Better Strategy School is a professional school for experienced leaders who carry strategic responsibility and want to lead it with greater precision, confidence, and impact. The School develops strategy as a practiced capability — through structured diagnosis, real application, and progressive mastery. Learn more at www.makebetterstrategy.com.