Use this when you're about to act on a problem and need to know what kind of problem it actually is. The Cynefin Framework sorts situations into domains — clear, complicated, complex, chaotic, and disorder — so you can match your response to the nature of the challenge rather than defaulting to the same playbook regardless of context.
Section 1
What This Tool Does
The most expensive mistake in decision-making isn't choosing the wrong option. It's applying the right answer to the wrong kind of problem. A founder who treats a complex market-entry challenge like a complicated engineering problem will build beautiful plans that shatter on contact with reality. A crisis leader who treats a chaotic supply-chain collapse like a complex system requiring patient experimentation will watch the building burn while gathering data. The mismatch between problem type and response type destroys more value than any individual bad decision — because it doesn't just produce the wrong answer, it produces the wrong kind of answer, and the team won't even recognise the error until the damage is done.
Dave Snowden developed the Cynefin Framework (pronounced kuh-NEV-in, from the Welsh word for habitat or place) in 1999 while working at IBM's Institute for Knowledge Management. His insight was deceptively fundamental: not all situations have the same relationship between cause and effect, and the appropriate decision-making approach depends entirely on which cause-and-effect relationship you're facing. In a clear domain, cause and effect are obvious to everyone — sense, categorise, respond. In a complicated domain, cause and effect exist but require expertise to identify — sense, analyse, respond. In a complex domain, cause and effect are only coherent in retrospect — probe, sense, respond. In a chaotic domain, there is no perceivable relationship between cause and effect — act, sense, respond. And then there's disorder: the state of not knowing which domain you're in, which is where most teams actually operate most of the time.
The framework's core intervention is forcing you to diagnose the nature of the situation before prescribing a response. That sounds obvious. It isn't. The default human behaviour is to treat every problem as if it belongs to the domain you're most comfortable in. Engineers default to complicated-domain thinking: analyse, find the right answer, implement. Entrepreneurs default to complex-domain thinking: experiment, iterate, pivot. Military commanders default to chaotic-domain thinking: act decisively, establish order, then assess. None of these defaults is wrong — each is perfectly suited to its native domain. The damage happens when the default gets applied to the wrong domain. An engineer's analytical rigour becomes analysis paralysis in chaos. An entrepreneur's experimental mindset becomes reckless in a complicated system where the right answer is knowable. A commander's decisive action becomes destructive in a complex system where the intervention itself changes the dynamics.
Snowden's framework has evolved since 1999. The "simple" domain was renamed "clear" (and later "obvious" in some versions, then back to "clear") to avoid the implication that the problems themselves are trivial. The boundaries between domains — which Snowden calls "liminal zones" — received more attention, particularly the cliff edge between clear and chaotic, where complacency in seemingly obvious situations leads to catastrophic failure. The framework is not a 2×2 matrix. It's not a spectrum. It's a sense-making model — a tool for understanding what kind of understanding is even possible in your current situation.
