Cynefin Framework
Dave Snowden's Cynefin Framework sorts problems into obvious, complicated, complex, chaotic or disorder, because the right way to decide depends on which kind you're facing.
How can it be useful to you?When you need to figure out what kind of problem you're facing, so you can pick the right way to tackle it.
1. Obvious: Follow the Recipe
Baking a cake from a recipe. The problem is straightforward and the answer is known. Follow the steps and you get the cake.
2. Complicated: Call the Expert
Fixing a car engine. You may not know what's wrong at first, but analysis or a good mechanic will find it. Once the problem is diagnosed, there's a clear fix.
3. Complex: Experiment and Adapt
Raising a child. There's no manual, and what works for one kid may flop with another. You try things, watch what happens and adjust as you go.
4. Chaotic: Act First
A house fire. You don't analyse; you get everyone out and contain the damage. Only once things are under control do you work out what caused it and how to prevent it next time.
5. Disorder: Find the Light Switch
You don't yet know which kind of situation you're in, like walking into a dark room. The job is to gather information until you can tell which of the other four domains you're dealing with.
The big lesson is that different problems need different approaches. Treat a fire like a recipe, or a child like an engine, and things go wrong fast. Cynefin is a good antidote to Maslow's hammer, the urge to treat every problem as a nail for your favourite tool.
Cynefin is popular with managers, agile coaches and public-sector planners, but it's a sense-making framework, not a tested scientific theory, and it has drawn steady criticism. The main objections:
Fuzzy termsWilliams and Hummelbrunner (2010) found key words such as "known", "knowable", "sense" and "categorize" ambiguous. That matters, because deciding which domain you're in is the whole point, and the framework offers no firm test for it.
Too thin a foundationFirestone and McElroy (first in 2003) called the framework confusing and in need of a more rigorous foundation, and argued it covers too narrow a range of contexts to serve as the general model of knowledge management it was sometimes presented as.
Little empirical evidenceCynefin is built from complexity theory and practitioner experience. There's little controlled research showing that teams who use it make better decisions than teams who don't, so its value rests mostly on case studies and testimonials.
The labels keep movingThe domains have been renamed several times, from "known" and "knowable" (Kurtz and Snowden, 2003), to "simple" and "complicated" (Snowden and Boone, 2007), to "obvious" (2014) and now "clear", while the central "disorder" domain became "confusion". The refinements may be improvements, but they also mean different books, courses and slides describe subtly different models.
It leaves out power and politicsLean management writer Bob Emiliani argues that Cynefin treats decisions as purely technical, while real leaders operate inside a culture of privilege that lets them ignore or deny inconvenient problems. He suggests the framework fits frontline problem-solving better than executive decision-making.
Borrowed science, loosely usedCritics such as Tom Graves (2010) note that the framework offers no tactics for genuinely chaotic systems, and others argue that it uses "chaos" in its everyday sense rather than the precise mathematical one its complexity-science framing implies.
None of this stops Cynefin from being useful. Its central message, that different kinds of problems call for different responses (and that the same old tool won't fit everything, the trap of Maslow's hammer), is sound. The fair reading is to treat it as a structured conversation starter, not as a measurement instrument.
Resources
Most bad decisions aren't bad because the decider was stupid. They're bad because the decider used the right method on the wrong kind of problem. The Cynefin Framework, created by Dave Snowden, is built to prevent exactly that: it helps organizations work out what kind of situation they're in before choosing how to respond. It draws on complexity theory, knowledge management and cognitive psychology.
The framework has five domains:
Simple (or Obvious)Cause and effect are clear to anyone. Established best practices work, and solutions can be applied quickly.
ComplicatedCause and effect exist but take expertise to see. Several good solutions may exist, and choosing among them requires careful analysis.
ComplexCause and effect can only be understood in hindsight. Solutions emerge through iterative experiments, learning and adaptation, much as Gall's law says working complex systems grow out of simple ones that worked.
ChaoticTurbulence with no discernible pattern. The first job is to act and stabilize the situation; solutions are usually novel and temporary.
DisorderThe centre of the framework, where it's unclear which of the other four domains applies. The goal here is to work out which domain you're actually in.
Cynefin links to several other principles and fields:
Complexity theoryThe study of how complex systems and patterns emerge from simple interactions between parts. Cynefin's complex domain draws heavily on it (Mitchell, 2009).
Systems thinkingAn approach that focuses on the structure and interconnections within a system. Cynefin reflects it by treating problems as embedded in interconnected systems rather than in isolation (Meadows, 2008).
Heuristics and biasesCognitive psychology shows we lean on mental shortcuts that can produce systematic errors. By forcing decision-makers to ask what kind of problem they face, Cynefin helps counter the reflex of applying a familiar solution everywhere, a reflex better known as Maslow's hammer (Kahneman, 2011).
Agile methodologiesAgile emphasizes iteration, flexibility and collaboration. It fits the complex domain well, since both favour experimenting and adapting under uncertainty (Cohen et al., 2010).
References
- Snowden, D. J., & Boone, M. E. (2007). A leader's framework for decision making. Harvard Business Review, 85(11), 68-76.
- Mitchell, M. (2009). Complexity: A Guided Tour. Oxford University Press.
- Meadows, D. H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing.
- Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
- Cohen, D., Lindvall, M., & Costa, P. (2010). An introduction to agile methods. Advances in Computers, 80, 1-66.
