Clear
- Cause & effect
- Constraints
- Your job
Drag a card onto a domain - or click it, then click where it goes. Double-click to rename. With a card focused, 1-5 assigns a domain and 0 sends it back.
Before you choose what to do, work out what kind of place you are standing in. Cynefin sorts situations by how cause and effect behave - and each terrain demands a different first move. Getting the terrain wrong is how good decisions fail.
Pick a region on the sheet. The panel beside it gives the domain’s decision sequence, the kind of practice that works there, and the way people most often come unstuck.
The value of the framework is not the five boxes - it is the traffic between them. Some crossings you engineer on purpose. One happens to you.
The only crossing with no gradient. Rules that worked for years stop working all at once, and because nobody was watching for it, there is no shallow water to stand in. Recovery is expensive and slow. Complacency is the mechanism.
Out of chaos you go to Complex, not to Clear. Act to stabilize, then start probing. Leaders who try to jump straight back to best practice re-create the conditions of the fall.
When probes keep producing the same pattern, the pattern becomes analysable. This is where exaptation lives too: something built for one purpose gets radically repurposed under constraint, and the new use is knowable even though its origin was not.
Expert judgment calcifies into “the way we do it.” Useful, and quietly dangerous: entrained thinking is what stops you seeing the edge approach.
Chaos is the cheapest place to be novel, because no established practice is defending itself. You can enter it on purpose and briefly to break entrained thinking - then pull back into Complex before the turbulence costs you.
Two questions. The first sorts you; the second checks whether you flattered yourself. Answer for one specific decision in front of you right now - not for the whole project.
Loading…
The center is not one state but two. Aporia is the active one: you know you do not know, and you hold the question open on purpose. Confusion is the passive one: you have not noticed, so you drift toward whichever domain you are most comfortable in. Only the second is a failure state, and the way out of both is the same: stop treating the mess as one thing, break it into parts, and place each part separately.
Most of these come from Snowden himself, usually with more force than this.
“Is deployment complicated or complex?” is the wrong question. The same deployment is Clear to the team that has done it two hundred times and Complex to the team meeting the system for the first time. The domain describes you and it, together, today.
The neat quadrant drawing - including the one above - misleads. Four of the boundaries are gradients you cross gradually and can reverse. The Clear / Chaotic boundary is a cliff. Treating them as equivalent edges is the single most common reading error.
A program of work is never “a complex project.” It is payroll (Clear), a migration (Complicated), an adoption question (Complex), and one incident that is on fire (Chaotic). Assigning a single domain to a whole initiative throws away the entire point.
The first domain went Simple → Obvious → Clear, because calling it simple invited contempt for the people working in it and blinded everyone to how quickly it can collapse. The center likewise stopped being plain Disorder and split in two: aporia, the active state where you know you do not know, and confusion, the passive one where you have not noticed. Snowden notates them A and C. They are not synonyms, and only confusion is a failure mode.
Outside Clear it is at best a starting hypothesis. Importing a playbook that worked somewhere else into a Complex situation is how organizations spend a year proving that their context is different.
Under Confusion, people do not choose a domain - they fall back to the one they are most comfortable acting in. Analysts see Complicated everywhere; firefighters see Chaotic. Knowing your own default is most of the defense against it.