cynefin-framework

name	cynefin-framework
description	Applies Cynefin framework for sense-making and decision-making across different contexts. Use when analyzing problem types, determining appropriate responses, making decisions under uncertainty, or when user mentions complexity, chaos, sense-making, problem classification, or asks which approach to use for a situation.

Cynefin Framework

Use the Cynefin framework to understand the nature of situations and determine appropriate decision-making approaches.

What is Cynefin?

Cynefin (pronounced "kuh-NEV-in") is a sense-making framework that helps categorize situations into five domains, each requiring different approaches:

┌─────────────────┬─────────────────┐
│                 │                 │
│    Complex      │   Complicated   │
│                 │                 │
│  Probe-Sense-   │  Sense-Analyze- │
│    Respond      │    Respond      │
│                 │                 │
├────────┬────────┴─────────────────┤
│        │                          │
│ Chaos  │  Confused/Disorder       │
│        │                          │
│ Act-   │    (Don't know which     │
│ Sense- │      domain you're in)   │
│ Respond│                          │
│        │                          │
├────────┴──────────────────────────┤
│                                   │
│          Clear/Obvious            │
│                                   │
│      Sense-Categorize-Respond     │
│                                   │
└───────────────────────────────────┘

Key Insight: Different situations require fundamentally different decision-making approaches. Using the wrong approach for the domain leads to failure.

The Five Domains

1. Clear/Obvious Domain (Formerly "Simple")

Nature: Known knowns - cause and effect are clear to everyone

Characteristics:

• Repeatable, predictable
• Best practices exist
• Right answer is self-evident
• Process-oriented
• Rules and procedures work

Decision Approach: Sense - Categorize - Respond

1. Sense: Assess the facts
2. Categorize: Apply appropriate category/rule
3. Respond: Execute the standard response

Management Style:

• Standard operating procedures
• Legitimate best practices
• Efficiency and consistency
• Training and compliance
• Process automation

Examples:

• Following a recipe
• Assembly line production
• Processing payroll
• Password reset procedures
• Simple customer service scripts

Dangers:

• Complacency: Success breeds over-confidence
• Entrained thinking: Missing context changes
• Complacent → Chaotic shift: Sudden crisis when assumptions break

When to Use: Routine, well-understood, stable situations

---

2. Complicated Domain

Nature: Known unknowns - cause and effect require analysis/expertise

Characteristics:

• Multiple right answers exist
• Requires expert analysis
• Cause and effect discoverable but not self-evident
• Good practices exist (not best practices)
• Expertise matters

Decision Approach: Sense - Analyze - Respond

1. Sense: Gather data and information
2. Analyze: Engage experts to assess options
3. Respond: Select and implement appropriate solution

Management Style:

• Expert-driven decision making
• Analytical approaches
• Good practices (context-dependent)
• Multiple valid solutions
• Consulting and expertise

Examples:

• Engineering design problems
• Medical diagnosis
• Financial planning
• Legal analysis
• Architecture decisions

Dangers:

• Analysis paralysis: Over-analysis
• Expert disagreement: Conflicting expert opinions
• Over-complication: Making simple things complicated
• Ivory tower syndrome: Experts disconnected from reality

When to Use: Problems requiring expertise but with discoverable solutions

---

3. Complex Domain

Nature: Unknown unknowns - cause and effect only coherent in retrospect

Characteristics:

• Emergent patterns
• Unpredictable outcomes
• No right answers, only emergent practices
• Many interacting agents
• Retrospective coherence only

Decision Approach: Probe - Sense - Respond

1. Probe: Run safe-to-fail experiments
2. Sense: Observe what emerges
3. Respond: Amplify good patterns, dampen bad ones

Management Style:

• Experimentation and learning
• Emergent practices
• Pattern recognition
• Distributed decision-making
• Fail-safe experimentation

Examples:

• Organizational culture change
• Market dynamics
• Ecosystem management
• Startup product-market fit
• Social movements
• Parenting teenagers

Key Principles:

• Safe-to-fail experiments: Small, reversible probes
• Parallel experiments: Try multiple approaches
• Amplify/Dampen: Strengthen what works, weaken what doesn't
• Diversity: Multiple perspectives enhance sensing
• Coherence emerges: Patterns become clear over time

Dangers:

• Premature convergence: Settling on solution too early
• Applying complicated practices: Seeking the "right" answer
• Over-constraint: Limiting emergence
• Ignoring weak signals: Missing early patterns

When to Use: Novel situations, many unknowns, emergent dynamics

---

4. Chaotic Domain

Nature: Unknowable unknowns - no cause-effect relationships perceivable

Characteristics:

• High turbulence
• No time for analysis
• Need for immediate action
• Crisis mode
• Novel circumstances

Decision Approach: Act - Sense - Respond

1. Act: Take immediate action to stabilize
2. Sense: Assess impact of action
3. Respond: Work to establish order, move to complex

Management Style:

• Direct, authoritative action
• Crisis management
• Rapid stabilization
• Move to complexity quickly
• Novel practice (doing something new)

Examples:

• Emergency response (fire, medical)
• System outages/crises
• 9/11 immediate response
• Market crashes
• Natural disasters

Key Principles:

• Act decisively: Delay is dangerous
• Establish order: Create stability
• Communicate clearly: Reduce confusion
• Don't seek consensus: Too slow
• Transition out: Move to complex as soon as possible

Dangers:

• Staying too long: Chaos shouldn't be normal state
• Creating dependence: Hero leadership becoming expected
• Manufacturing chaos: Creating crisis to justify authority
• Decision exhaustion: Burn-out from sustained crisis

When to Use: Crisis, emergencies, need for immediate stabilization

---

5. Confused/Disorder (Center)

Nature: Don't know which domain you're in

Characteristics:

• Uncertainty about situation type
• Multiple people seeing different domains
• Default to personal preference
• Lack of shared understanding

Response: Assess and Categorize

1. Break down the situation into components
2. Categorize each component into appropriate domain
3. Apply appropriate approaches to each part

Dangers:

• Personal bias: Defaulting to familiar approach
• Analysis paralysis: Getting stuck in assessment
• Domain confusion: Misclassifying the situation

When to Use: When unclear which domain applies - get clarity fast

---

Decision-Making Patterns by Domain

Domain	Approach	Key Action	Output Type
Clear	Sense-Categorize-Respond	Apply best practice	Known solution
Complicated	Sense-Analyze-Respond	Expert analysis	Good practice
Complex	Probe-Sense-Respond	Safe-fail experiments	Emergent practice
Chaotic	Act-Sense-Respond	Decisive action	Novel practice

Cynefin Assessment Workflow

Use this workflow to categorize situations and determine approaches:

Assessment Checklist:
- [ ] Step 1: Describe the situation
- [ ] Step 2: Assess cause-effect clarity
- [ ] Step 3: Determine domain
- [ ] Step 4: Identify appropriate response pattern
- [ ] Step 5: Apply domain-specific approach
- [ ] Step 6: Monitor for domain shifts

Step 1: Describe the Situation

Clearly articulate the problem or decision:

• What is happening?
• What needs to be decided/solved?
• Who is involved?
• What's the context?

Step 2: Assess Cause-Effect Clarity

Ask these diagnostic questions:

Is cause-effect clear to everyone?

• Yes → Likely Clear
• No, but discoverable with analysis → Likely Complicated
• No, only clear in retrospect → Likely Complex
• No, not perceivable at all → Likely Chaotic

Are there established practices?

• Best practices exist → Clear
• Good practices exist (multiple valid) → Complicated
• Emergent practices only → Complex
• No practices applicable → Chaotic

What's the urgency?

• Crisis requiring immediate action → Chaotic
• Time for experiments → Complex or Complicated
• Routine timing → Clear

Step 3: Determine Domain

Use the domain characteristics from DOMAINS.md for detailed assessment.

Quick domain indicators:

Clear Domain:

• ✓ Everyone agrees on cause-effect
• ✓ Documented best practices exist
• ✓ Repeatable process works
• ✓ Training solves the problem

Complicated Domain:

• ✓ Experts needed for analysis
• ✓ Multiple valid solutions exist
• ✓ Requires investigation
• ✓ Good practices available

Complex Domain:

• ✓ Many unknowns and interactions
• ✓ Outcomes unpredictable
• ✓ Patterns emerge over time
• ✓ Small changes have big impacts

Chaotic Domain:

• ✓ Crisis or emergency
• ✓ No time for analysis
• ✓ Immediate action needed
• ✓ High turbulence

Step 4: Identify Appropriate Response Pattern

Match the domain to its decision pattern:

• Clear → Sense-Categorize-Respond
• Complicated → Sense-Analyze-Respond
• Complex → Probe-Sense-Respond
• Chaotic → Act-Sense-Respond

Step 5: Apply Domain-Specific Approach

Execute using domain-appropriate methods. See PRACTICES.md for detailed guidance.

Step 6: Monitor for Domain Shifts

Situations can move between domains:

• Chaos → Complex (stabilization)
• Complex → Complicated (pattern emergence)
• Complicated → Clear (standardization)
• Clear → Chaotic (complacency collapse)

Monitor for shift indicators:

• Increased/decreased uncertainty
• New information changing understanding
• Crisis emergence or resolution
• Pattern stabilization or disruption

Domain Dynamics and Movement

The Complacency Shift (Clear → Chaotic)

Most dangerous transition: Success in Clear domain breeds complacency, assumptions ossify, then crisis hits.

Warning signs:

• "We've always done it this way"
• Ignoring context changes
• Over-reliance on process
• Dismissing weak signals
• Efficiency at expense of resilience

Prevention:

• Regular assumption testing
• Scan for context changes
• Maintain diversity
• Encourage questions
• Build resilience, not just efficiency

Intentional Movement

Chaos → Complex: Stabilize through decisive action, then shift to experimentation

Complex → Complicated: As patterns emerge and stabilize, expert analysis becomes possible

Complicated → Clear: Standardize proven solutions into repeatable processes

Clear → Complicated: When context changes, re-examine with experts

Complex → Chaos: Sometimes necessary to break entrenched patterns (rare, risky)

Constraints Framework

Cynefin uses three types of constraints to understand domains:

Governing Constraints (Clear domain):

• Fixed, rigid rules
• No deviation allowed
• "Must follow this process"

Enabling Constraints (Complex domain):

• Boundaries that enable coherence
• Encourage exploration within bounds
• "Here are the guard rails, explore within them"

Lack of Constraints (Chaotic domain):

• No effective constraints
• Anything goes
• Need to establish constraints quickly

Complicated domain: Mix of governing and enabling constraints

Common Cynefin Mistakes

Mistake 1: Using Complicated Approach in Complex Domain

What it looks like:

• Seeking the "right" answer in complex situations
• Over-reliance on expert analysis for unknowable outcomes
• Long planning phases for emergent situations

Why it fails:

• Complex situations don't have predetermined answers
• Expertise can't predict emergence
• Plans become obsolete quickly

Correct approach:

• Run experiments
• Iterate rapidly
• Learn from emergence

Mistake 2: Using Clear Approach in Complicated Domain

What it looks like:

• Applying one-size-fits-all solutions
• Ignoring expert input
• Following rigid processes for nuanced problems

Why it fails:

• Misses important context
• Overlooks better solutions
• Wastes expertise

Correct approach:

• Engage experts
• Analyze options
• Select context-appropriate solution

Mistake 3: Staying in Chaotic Domain

What it looks like:

• Constant crisis management
• Hero leadership as normal state
• No time for reflection

Why it fails:

• Burnout
• Unsustainable
• Prevents learning

Correct approach:

• Stabilize quickly
• Move to complex domain
• Build resilience

Mistake 4: Forcing Complex to Clear

What it looks like:

• Demanding certainty when none exists
• Requiring detailed plans for unknowable situations
• Punishing experimentation

Why it fails:

• Stifles innovation
• Prevents necessary learning
• Creates false confidence

Correct approach:

• Acknowledge uncertainty
• Enable safe-to-fail experiments
• Learn from outcomes

Cynefin in Practice: Examples

Software Development

Clear: Deploying standard updates, password resets Complicated: Architecture decisions, performance optimization Complex: Product-market fit, adoption patterns, cultural transformation Chaotic: Production outage, security breach

Business Strategy

Clear: Standard financial reporting, compliance procedures Complicated: Market entry strategy, competitive analysis Complex: Culture change, innovation programs, market disruption Chaotic: Sudden market crash, regulatory crisis

Leadership

Clear: Performance reviews using standard criteria Complicated: Organizational restructuring, strategic planning Complex: Building organizational culture, change management Chaotic: Crisis response, major incident management

Decision Template

When applying Cynefin to a decision:

# Cynefin Analysis: [Situation/Problem]

## Situation Description
[Describe what's happening]

## Domain Assessment

**Cause-Effect Clarity:**
[Clear to all / Discoverable / Retrospective / Not perceivable]

**Domain Classification:**
[Clear / Complicated / Complex / Chaotic / Confused]

**Rationale:**
[Why this domain?]

## Decision Approach

**Pattern to Apply:**
[Sense-Categorize-Respond / Sense-Analyze-Respond / Probe-Sense-Respond / Act-Sense-Respond]

**Specific Actions:**
1. [Action step 1]
2. [Action step 2]
3. [Action step 3]

## Domain Shift Monitoring

**Watch for:**
- [Signal 1 indicating domain shift]
- [Signal 2 indicating domain shift]

## Constraints

**Type:**
[Governing / Enabling / Lack of / Mixed]

**Current Constraints:**
[List relevant constraints]

Quick Reference

When facing a situation, ask:

1. Is cause-effect clear?

   • To everyone → Clear
   • To experts → Complicated
   • Only in retrospect → Complex
   • Not at all → Chaotic

2. What's the right response?

   • Clear → Apply best practice
   • Complicated → Analyze with experts
   • Complex → Experiment and learn
   • Chaotic → Act decisively, stabilize

3. What's dangerous?

   • Clear → Complacency
   • Complicated → Analysis paralysis
   • Complex → Premature convergence
   • Chaotic → Staying too long

4. How do I know it's working?

   • Clear → Efficiency, consistency
   • Complicated → Expert consensus, good outcomes
   • Complex → Emergent patterns, learning
   • Chaotic → Stabilization, moving to complex

Remember: The framework is for sense-making, not categorization. Use it to understand situations and choose appropriate responses.