Most leaders who commission a strategic review believe their organization has a strategy problem. The research suggests otherwise. The problem is usually a classification problem — a failure to correctly identify what kind of challenge is actually being faced before deciding how to respond to it. The strategy that gets built is often technically coherent. What it fails to account for is the structural nature of the problem it was designed to solve.
The distinction matters because different categories of problems respond to fundamentally different interventions. Applying the wrong intervention is not just inefficient — it can actively worsen the situation by consuming resources, producing false confidence, and foreclosing the option of a more appropriate response until the window for that response has closed.
The Complicated vs. Complex distinction
The Cynefin Framework, developed by Dave Snowden and Mary Boone and published in a landmark Harvard Business Review paper, draws a critical distinction between Complicated and Complex problems. A Complicated problem is difficult but solvable through expert analysis — the path forward is knowable, the relationships between cause and effect are discoverable, and applying the right methodology to sufficient data will surface the answer. Sending a rocket to the moon is Complicated. The engineering is extraordinarily difficult, but it is solvable by expert analysis operating within known physical laws.
A Complex problem is one where the solution cannot be derived analytically because it depends on the behaviour of multiple actors whose interests are not aligned and whose interactions produce emergent outcomes that no analysis can fully anticipate. Transforming a health system's approach to chronic disease is Complex. The technical clinical evidence may be clear. What is not clear — what cannot be made clear through analysis alone — is how dozens of independent actors with competing incentives will actually behave when asked to change their practice. That is a coordination problem, and it requires a different response.
The misclassification that produces expensive failure
The evidence from large-scale systems failures is instructive. The US healthcare.gov rollout in 2013 failed not because the technical architecture was poorly designed, but because the coordination problem among dozens of contractors with different mandates, timelines, and accountability structures was never resolved. The UK's NHS electronic records program — one of the most expensive IT programs in history — produced years of consultancy reports but failed to produce a functioning system because the analytical work never addressed the fundamental question of whose behaviour needed to change and under what conditions they would change it.
These are not outliers. They are illustrations of a pattern the research documents repeatedly: Complicated interventions applied to Complex problems produce excellent documentation of why the situation is difficult. They do not produce solutions. The analysis is real. The failure is structural.
Why organizations keep misclassifying
The incentive structure of most organizations rewards the production of confident analytical outputs. Strategy consultants are hired to produce recommendations. Leadership teams are evaluated on the clarity of their strategic direction. The whole apparatus of organizational strategy is designed around the assumption that the right answer is findable through sufficient rigour. Admitting that a problem is Complex — that the path forward is genuinely uncertain and will require multi-stakeholder co-creation rather than expert analysis — is organizationally uncomfortable. It means the deliverable is a process, not a plan, and the timeline is measured in behaviour change, not slide decks.
The result is a vicious cycle: the organization commissions analysis, the analysis produces a strategy, the strategy fails at execution, the organization commissions more analysis to understand why the strategy failed. Each iteration depletes the organizational credibility available for the next attempt. At some point, the accumulated failures make it genuinely difficult to convene the stakeholders whose alignment is required to solve the problem — because those stakeholders have learned, correctly, that the process does not produce actionable outcomes.
The diagnostic as the first intervention
The most valuable thing a leader can do before commissioning a strategic intervention is to correctly classify the problem. This is not a two-week analytical exercise. It is a structured set of questions that can be answered in a single focused session: Who are the actors whose behaviour must change for the outcome to materialize?
Do those actors have competing incentives? Is the path forward unknown because the evidence is insufficient, or because the evidence is clear but the coordination required to act on it is not in place? Is this a resource problem, an analytical problem, or a coordination problem?
The answers to these questions determine the category of intervention required. For Complicated problems, deploy analysis. For Complex problems, design a process that convenes the right actors, surfaces the real constraints, and produces a strategy those actors helped build and therefore have a stake in executing. Confusing the two is not a minor error. It is the hidden cause of most of the expensive strategy failures that appear, on the surface, to be something else entirely.
Frequently Asked Questions
What is the difference between a Complicated problem and a Complex one?
A Complicated problem is difficult but solvable through expert analysis — the path forward is knowable, and applying the right methodology to sufficient data will surface it. A Complex problem is one where the solution cannot be derived analytically because it depends on the behaviour of multiple actors whose interests are not aligned and whose interactions produce emergent outcomes that no analysis can fully anticipate. Misclassifying a Complex problem as Complicated — and deploying expert analysis in response — produces a strategy that fails at the point of execution, when the human coordination problem that was never addressed reasserts itself.
Why do organizations systematically misclassify complex problems as complicated ones?
The incentive structure of most organizations rewards the production of confident analytical outputs. Strategy consultants are hired to produce recommendations. Leadership teams are evaluated on the clarity of their strategic direction. The whole apparatus of organizational strategy is designed around the assumption that the right answer is findable through sufficient rigour. Admitting that a problem is complex — that the path forward is genuinely uncertain and will require multi-stakeholder co-creation rather than expert analysis — is organizationally uncomfortable. It means the deliverable is a process, not a plan, and the timeline is measured in behaviour change, not slide decks.
What is the cost of deploying the wrong tool for a complex problem?
The direct cost is a failed initiative — resources deployed, a strategy that looked good on paper, and execution that stalled at the first point of real-world friction.
The indirect cost is often larger: the credibility of the strategy process itself is damaged, the organization becomes harder to align on the next attempt, and the window of opportunity the original initiative was designed to capture has often closed. Research on complex transformation failures consistently finds that the single most common root cause was not inadequate planning — it was inadequate attention to the human coordination problem that made execution structurally impossible from the start.