Skip to main content
Category: Models
Type: Sense-Making Framework
Origin: David Snowden, 1999
Also known as: Cynefin Sense-Making Framework, Complexity Decision Model
Quick Answer — The Cynefin Framework is a decision-making and sense-making model developed by Dave Snowden in 1999 while at IBM. It classifies situations into five domains—Obvious, Complicated, Complex, Chaotic, and Disorder—each requiring different leadership approaches. The framework helps leaders move beyond “best practice” thinking and match their response to the nature of the situation they face.

​
What is the Cynefin Framework?

The Cynefin Framework is a conceptual tool for helping leaders make sense of the situations they face and choose appropriate responses. The word “Cynefin” (pronounced KUH-neh-vin) is a Welsh word meaning “habitat” or “place of familiar belonging,” reflecting how our past experiences shape how we perceive and respond to new situations.
“The leader’s job is not to provide all the answers, but to ask the right questions in the right way.” — Dave Snowden
The framework identifies five domains:
  1. Obvious (or Simple): The realm of “best practices.” Cause and effect are clear, relationships are known, and the right answer is obvious to anyone with domain knowledge. Situations here follow predictable patterns.
  2. Complicated: The realm of “good practices.” Multiple right answers exist, and expertise is required to find them. Cause and effect can be understood but require analysis. Experts can analyze and recommend solutions.
  3. Complex: The realm of “emergent practices.” Cause and effect can only be seen in retrospect. No one has the complete answer. Outcomes are unpredictable. The approach is to probe, sense, and respond—to experiment and see what emerges.
  4. Chaotic: The realm of “novel practices.” There is no clear cause-effect relationship. Action is needed immediately to establish order. The priority is to act, sense, and respond to stabilize the situation.
  5. Disorder: The state of confusion where it’s unclear which domain applies. Leaders must first decide which domain they are in before taking action.

​
The Cynefin Framework in 3 Depths

  • Beginner: Think of cooking a recipe. If it’s a simple dish with clear instructions (Obvious), follow the recipe exactly. If it’s a more complex dish requiring technique (Complicated), consult an expert cook. If you’re inventing a new dish (Complex), you experiment with ingredients and see what works. If the kitchen is on fire (Chaotic), you act immediately to put it out before thinking about recipes.
  • Practitioner: Before solving a problem, first identify what kind of situation you’re dealing with. A process improvement in a stable environment is Simple. Launching a new product in a familiar market is Complicated. Entering an entirely new market with a novel product is Complex. A PR crisis is Chaotic. Each requires a fundamentally different approach.
  • Advanced: Recognize that situations can shift between domains. What was Simple can become Complex as circumstances change. The most critical skill is domain awareness—knowing when to apply which approach. Expert individuals can become liabilities when they apply Complicated solutions to Complex problems, forcing patterns that don’t exist.

​
Origin

Dave Snowden developed the Cynefin Framework in 1999 while working at IBM’s Institute for Knowledge Management. The framework emerged from his research into knowledge management and organizational learning, particularly his work on narrative approaches to understanding how people make sense of their experiences. Snowden was influenced by anthropology and complexity science, particularly the work of Donella Meadows on systems thinking and the Santa Fe Institute’s research on complex adaptive systems. The framework was designed to help organizations move beyond simplistic “best practice” thinking and develop more nuanced approaches to different types of challenges. The Cynefin Framework has been widely adopted in fields ranging from business strategy and organizational change to military planning and healthcare management. It has influenced approaches to innovation, change management, and leadership development across numerous industries.

​
Key Points

1

Context determines the right approach

No single management approach works in all situations. What works in a Simple domain may fail catastrophically in a Complex one. Leaders must develop situational awareness and resist the temptation to apply familiar solutions to unfamiliar contexts. The first question is always: “What kind of situation is this?”
2

Expertise has limits in complex domains

Experts excel in the Complicated domain where their knowledge can be applied to find solutions. But in Complex domains, expertise can actually be a liability—experts may force patterns that don’t exist or resist emergent solutions that contradict their mental models. The Complex domain often rewards beginners who lack preconceptions.
3

Complex problems require different methods

In Complex domains, traditional planning and prediction fail. Instead, leaders should “probe, sense, and respond”—run small experiments, observe outcomes, and evolve approaches based on what emerges. This is fundamentally different from the “sense-analyze-decide” approach that works in Complicated situations.
4

Chaos requires immediate action first

In Chaotic situations, there is no time for analysis. Leaders must act quickly to establish order, then step back to assess whether the situation has stabilized into one of the other domains. Waiting for perfect information in a Chaotic situation leads to disaster.

​
Applications

Strategic Decision Making

Use the framework to determine the appropriate approach for different business challenges. Routine operations are Simple. Product development in familiar domains is Complicated. Entering new markets or disrupting industries is Complex. Crises require Chaotic responses.

Innovation Management

Apply Complex-domain approaches to innovation initiatives. Instead of detailed planning, use rapid prototyping, pilot programs, and iterative learning. Accept that outcomes cannot be predicted and focus on organizational capability to adapt.

Change Leadership

Recognize that organizational change is Complex, not Simple. There are no proven recipes for successful change. Different parts of the organization may require different approaches depending on their complexity and readiness.

Crisis Response

Distinguish between Complex problems (which require patience and experimentation) and Chaotic situations (which require immediate decisive action). Many failed crisis responses result from treating Complex situations as if they were Simple.

​
Case Study

The response to the 2008 financial crisis illustrates the Cynefin domains in action. In the early days of the crisis, when Lehman Brothers collapsed and markets were in freefall, the situation was Chaotic—immediate action was required to prevent complete systemic collapse. Governments and central banks acted decisively, providing liquidity and backstopping critical institutions. Once the acute panic subsided, the situation moved into the Complex domain. The causes were debated endlessly, and no one could predict with certainty which policy responses would work. Different countries tried different approaches—some pursued aggressive stimulus, others focused on austerity. The appropriate response was to probe (try different policies), sense (observe results), and respond (adjust course). However, many policymakers continued to operate as if they were in the Complicated domain—analyzing complex economic models and believing they could engineer specific outcomes. This approach often proved inadequate for a truly Complex situation. The lesson: recognizing which domain you’re in is the first step toward an effective response.

​
Boundaries and Failure Modes

Real-world situations don’t always fit neatly into one domain. The same situation may appear Simple in some respects and Complex in others. Leaders may disagree about which domain applies, leading to conflict about the appropriate approach.
The framework’s simplicity is both its strength and weakness. Some users oversimplify the framework, treating it as a rigid categorization rather than a heuristic for thinking about situations. This can lead to mechanical application rather than genuine sense-making.
The framework requires a certain humility about prediction and control. In cultures or organizations that prize certainty and expertise, the Complex domain approach of “we’ll figure it out as we go” may face resistance. The framework is not value-neutral.

​
Common Misconceptions

The Cynefin Framework is often misunderstood in ways that limit its effectiveness. One common error is treating Simple and Complicated as inherently better than Complex—many people assume that Complex situations are problems to be solved rather than conditions to be navigated. Another mistake is assuming that expertise always helps—experts can be less effective in Complex domains because their existing mental models may not fit. Some users also treat the framework as a decision tree rather than a sense-making tool—it should guide thinking, not replace judgment. The Cynefin Framework connects to several related thinking tools. Complexity Theory (from /models/complexity-theory) provides the scientific foundation for understanding why some problems cannot be solved through traditional analysis. OODA Loop (from /models/ooda-loop) offers a decision-making process particularly suited to Complex and Chaotic domains. Understanding Systems Thinking (from /models/systems-thinking) helps leaders recognize interconnections that make situations Complex.

​
One-Line Takeaway

Don’t assume every problem can be solved with the same approach. Use the Cynefin Framework to identify what kind of situation you’re facing—Simple, Complicated, Complex, or Chaotic—and match your response accordingly.