1 / 17
Masterclass

The Cynefin Framework

A Sensemaking Model for Navigating Complexity, Making Better Decisions, and Leading Through Uncertainty

Dave Snowden · Cynefin Centre for Organizational Complexity

2 / 17

Today's Journey

3 / 17

The Problem With Jumping to Answers

"Most management failures are not decision failures — they are domain errors. The leader who applies best-practice thinking to a complex problem has already failed, before making a single decision."

The habit of reaching for solutions before understanding context is the most common — and most costly — mistake in leadership.

4 / 17

What is Cynefin?

Cynefin (Welsh: ky-NEV-in) — "habitat" or "place of your multiple belongings"

Created by Dave Snowden at IBM, rooted in complexity science and cognitive anthropology.

It's a sensemaking framework, not a classification matrix.

The core insight: Same action succeeds in one context, fails in another. Context determines method. There is no single best practice that works everywhere.

5 / 17
Domain 1

Obvious / Clear

The domain of known unknowns. Clear cause-effect relationships. Repetition.

Sense → Categorize → Respond

When in doubt: follow the process. Don't reinvent the wheel.

6 / 17
Domain 1 — Examples

Obvious / Clear in Practice

SituationAppropriate Response
Processing a standard invoiceFollow AP workflow; escalate only exceptions
Onboarding a new hire (paperwork)Run the standard checklist
Compliance reporting (quarterly)Use the prescribed template and process
Scheduling recurring meetingsStandard calendar and room process
Equipment failure under warrantyFile warranty claim by the book

⚠️ When leaders apply "visionary thinking" to routine processes, they create unnecessary variability and confusion.

7 / 17
Domain 2

Complicated

The domain of unknown unknowns that can be discovered. Cause-effect exists but requires expertise to find.

Sense → Analyze → Respond

Ask: "Who has done this before and what did they learn?" — experts exist.

8 / 17
Domain 2 — Examples

Complicated in Practice

Systems Integration

Legacy system migration requires expert analysis of dependencies. Right answer exists but takes investigation to find.

Medical Diagnosis (non-trivial)

Symptoms suggest multiple possible causes. Needs differential diagnosis by an experienced clinician.

Financial Restructuring

Multiple debt instruments, tax implications, stakeholder interests. Expert analysis needed to optimize.

Product Performance Issue

Multiple potential root causes. Requires structured investigation: root-cause analysis, DOE.

The distinction between "complicated" and "complex" is the most important — and most frequently confused — boundary in the framework.

9 / 17
Domain 3

Complex

The domain of emergence. Cause-effect can only be understood in retrospect. Unknown unknowns dominate.

Probe → Sense → Respond

This is where most strategic change initiatives fail — because leaders treat them as complicated.

10 / 17
Domain 3 — Core Pattern

Probe-Sense-Respond

The fundamental leadership move in complex terrain:

"In complex systems, you don't analyze your way to understanding. You experiment your way there."

Key difference from Complicated: in Complicated, analysis comes before action. In Complex, action comes before analysis — because you can only analyze what has already happened.

11 / 17
Domain 3 — Tools

Designing Safe-to-Fail Probes

Instead of this (Complicated thinking)Try this (Complex thinking)
Develop a comprehensive 3-year strategyRun a 6-week pilot with 3 possible directions
Analyze the market until confidentApproach 10 real customers and see what happens
Design the perfect organizational structureCreate a team that tries a new approach for one quarter
Plan the change fully before actingDo something small, watch the response, adjust
Identify all risks and mitigate upfrontMake failure small enough to learn from, not large enough to harm you
12 / 17
Domain 4

Chaotic

The domain of crisis and emergency. No clear cause-effect. Urgent action required.

Act → Sense → Respond

First: stop the bleeding. Then figure out what kind of problem you have.

13 / 17
Domain 4 — Examples

Chaotic in Practice

Product Recall Crisis

Multiple deaths reported. Immediate action required: halt production, communicate publicly, mobilize crisis team. No time for committee analysis.

Server Outage Taking Down Production

Revenue bleeding every hour. Restore first, root-cause analysis second. The probe is the fix.

Key Executive Quits Without Warning

Team is panicking, clients are asking questions. Immediate stabilization before strategic planning.

Market Crash / Flash Crisis

Algorithmic cascade selling. Trying to "understand" the market delays response. Act to stabilize first.

14 / 17
Domain 5

Disorder

Confusion. Unclear which domain applies. Mixed signals, competing narratives.

When you don't know which domain you're in:

Most strategic planning meetings happen in disorder. The first task is to get enough clarity to know whether this is a complicated problem or a complex one.

15 / 17

Domains Are Dynamic

No domain is permanent. Systems shift. The key skill is continuous re-diagnosis:

"The most dangerous moment is when something that worked before stops working — but nobody notices the domain has changed."
16 / 17

Case Studies

NASA Columbia Disaster (2003)

Domain error: The shuttle program had evolved from "complicated" to "complex" (new failure modes emerging from known causes) but was still being managed with complicated-domain thinking. Warning signs were analyzed as if they could be fully understood before acting. They couldn't. Decision-making in a complex system requires acting on partial information.

Netflix Culture Evolution

Domain: Complex, over years. Netflix ran continuous safe-to-fail probes: unlimited vacation policy → observed → adjusted. No master plan. They sensed the system's response and responded accordingly.

Toyota Quality Movement

Transition: Complicated → Complex. As Toyota scaled globally, standardized processes hit their limits. They moved to a probe-sense-respond model (Genchi Genbutsu — go see for yourself) to handle emergent quality issues.

17 / 17

Key Takeaways

"The leader's job is not to have all the answers. It is to know which kind of question they are facing."

Cynefin Framework · Dave Snowden · Cynefin Centre