Cynefin Framework
The name comes from Welsh and refers to the idea that we are products of multiple experiences, places, and identities. Snowden chose this name to emphasize that the model is not a static classification model but an acknowledgment that contexts have their own history and context.
The five domains
Obvious domain (formerly: "simple")
Cause-and-effect relationships are predictable, repeatable, and known to everyone. Best practices exist and are the right response.
Recommended response: sense → categorize → respond. Apply the established practice.
Examples: processing a standard invoice, resolving a support incident with a documented procedure.
Risk: classifying a situation as obvious when it is actually complicated or complex. The comfort of "we've always done it this way" can mask signs of change.
Complicated domain
Cause-and-effect relationships exist and are knowable, but they are not evident to everyone: expert analysis is needed to identify them. There are multiple right answers.
Recommended response: sense → analyze → respond. Consult experts, analyze options, choose among good practices.
Examples: software architecture design, medical diagnosis, structural engineering.
Risk: "analysis paralysis": the complicated domain can become a trap if the perfect solution is sought instead of one that is good enough.
Complex domain
Cause-and-effect relationships can only be recognized in hindsight. There are no predefined right answers. The system is emergent and is understood by experimenting with it.
Recommended response: probe → sense → respond. Run safe-to-fail experiments so that knowledge and direction can emerge.
Examples: developing a new digital product, organizational change management, innovation.
Relationship with agility: agile project management—Scrum, Kanban—is the methodological response to the complex domain. Short sprints, continuous inspection and adaptation, and iterative delivery are precisely the "probe → sense → respond" mechanism that the complex domain requires.
Chaotic domain
There are no recognizable cause-and-effect relationships. The situation is turbulent and requires immediate action to stabilize it. There is no time for analysis.
Recommended response: act → sense → respond. Act to establish order, then sense the effect and respond.
Examples: a serious crisis in production, a cyberattack in progress, a disaster.
Disorder domain
It is not known which domain the situation is in. It is the central domain of the diagram and the highest-risk state: people interpret the situation from their usual perspective without questioning whether that framing is the right one.
How to Use Cynefin to Choose the Management Approach
Cynefin does not say that agility is always the right answer. It says that the right answer depends on the domain:
| Domain | Management approach | Why |
|---|---|---|
| Clear | Predictive management, standard processes | Best practices exist and should be followed |
| Complicated | Predictive management with expert analysis | Solutions can be planned with sufficient knowledge |
| Complex | Evolutionary management (Scrum, Kanban) | Iterative experimentation is needed to discover the solution |
| Chaotic | Crisis response, directive leadership | There is no time for analysis; you have to act and stabilize |
Cynefin and AI
Generative AI introduces a new source of complexity into the Cynefin domains: the interactions among people, systems, and AI agents in real projects have emergent effects that cannot be predicted from the outset. This places many AI development projects in the complex domain, reinforcing the relevance of an agile approach based on short, iterative experimentation.
Common mistake
Using Cynefin to justify agility in every context. Cynefin is a tool for choosing the right approach, not for defending a preferred one. An ERP integration project with fully defined requirements and prior experience may well fall in the complicated domain: it needs expert analysis and rigorous planning, not two-week sprints. Cynefin challenges both the manager who always applies predictive management and the agilist who always applies Scrum.
Resources
🔧 Cynefin Framework ToolResources · Scrum Manager
References
- Snowden, David J.; Boone, Mary E. (2007). "A Leader's Framework for Decision Making". Harvard Business Review, November 2007.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.