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.
These numbers are alarming enough on their own. But the more important question is: why do strategies fail? The answer that keeps emerging across sectors, decades, and organizational types is not incompetence, insufficient data, or lack of leadership commitment. It is the systematic application of the wrong methodology to the wrong type of problem.
Complicated vs. Complex: A Distinction That Changes Everything
The Cynefin Framework, developed by Dave Snowden and published in a landmark 2007 Harvard Business Review paper, classifies organizational challenges into distinct domains. In the Complicated domain, cause-and-effect relationships are knowable — they may be hidden or require expertise to uncover, but expert analysis can find them. Traditional consulting excels here. In the Complex domain, cause-and-effect relationships are only visible in retrospect; the environment is non-linear and shifts in response to interventions. Expert analysis fails here not because it is poorly executed, but because the system cannot be modelled in advance.
The research confirms that this boundary is where most strategy failures occur — not because organizations are making poor decisions, but because they are making Complicated-domain decisions for Complex-domain problems. The Cynefin literature describes this as "the cliff": when leaders treat a complex, dynamic situation as a simple, linear one, they apply rigid standard operating procedures that eventually push the system into chaos from which recovery is exceptionally difficult.
What Misclassification Looks Like at Scale
The 2013 collapse of the HealthCare.gov launch is one of the most thoroughly documented cases of problem misclassification in recent government history. The U.S. Centers for Medicare and Medicaid Services treated the national health insurance marketplace — involving 55 separate contractors, dynamic federal policy, and divergent state-level requirements — as a complicated IT project with a fixed technical solution. Project costs surged from $292 million to $2.1 billion. On launch day, only six people successfully enrolled. The system's complexity — its polycentric governance structure, its multiple actors with independent veto power — was never accounted for in the methodology.
The UK's National Programme for IT tells the same story. A £12.4 billion effort to digitize the entire NHS was delivered as a top-down centralized procurement. It failed because it ignored the social complexity of local hospitals and clinics: doctors and nurses rejected systems that disrupted their workflows, not because the technology was wrong, but because the implementers had never been part of building it. A post-mortem published in the BMJ concluded that the programme's failure was rooted in treating a complex socio-technical transformation as a manageable engineering problem.
The pharmaceutical industry produces perhaps the clearest cases. Sarepta Therapeutics' Exondys 51 — the first FDA-approved treatment for Duchenne muscular dystrophy — faced a near-immediate commercial crisis despite its approval. Sarepta had solved the complicated problem: clinical data, regulatory strategy, orphan drug designation. What they had not solved was the complex one. Payers, including major insurers and pharmacy benefit managers, had never been convened around the drug's value evidence. Coverage denials were widespread at launch, and patient access remained severely constrained for years. The FDA approval was real. The execution ecosystem had never been built.
The Vicious Cycle
The Strategy Institute's 2024 analysis identified what it calls "The Vicious Cycle of Misdiagnosis": when an initiative fails, leaders typically attribute the failure to the strategy itself — the analysis wasn't deep enough, the recommendations weren't specific enough — rather than to the methodology. They commission another report. They hire another analytical firm. The diagnosis remains wrong, and the result is the same.
Breaking the cycle requires a prior question: before asking "what is the solution?" organizations need to ask "what kind of problem is this?" That classification decision — Complicated or Complex, Analytical or Village Problem — is not a preliminary formality. It is the single most consequential strategic choice a leadership team will make.
At Mind Meeting Group, the first thing we do is not propose a solution. It is help leaders see the problem type clearly — and understand why the intervention their instincts are reaching for will not close the gap between strategy and execution.