Index

Cynefin Framework

A sense-making framework that classifies problems into five domains — clear, complicated, complex, chaotic, and confused — each requiring a distinct management approach.

Cynefin prevents misapplied best practices by categorizing situations into domains that each demand a different style of response.

What domain is this problem in, and am I using the response style that domain demands?

A product team treats user growth as a complicated problem and hires analysts. When growth stalls, they realize adoption is complex — driven by community behavior — and shift to safe-to-fail experiments instead of predictive models.

  1. 1.Assess whether the situation has clear causality, expert-discoverable causality, emergent patterns, or no visible patterns.
  2. 2.Match the domain to its response: sense-categorize-respond for clear, sense-analyze-respond for complicated, probe-sense-respond for complex, act-sense-respond for chaotic.
  3. 3.Avoid applying best practices from one domain to another.
  4. 4.Reassess the domain as conditions evolve — problems can shift between domains.
  • ·Treating complex problems as merely complicated and over-planning.
  • ·Defaulting to chaotic-mode urgency when the situation is actually complex and needs patience.
  • ·Arguing about domain classification instead of using it to choose a response style quickly.

When is Cynefin most useful?

When a team is stuck because their standard approach isn't working. Cynefin often reveals they are applying the wrong category of response.

How does Cynefin relate to agile methods?

Agile practices like iteration and retrospectives align well with the complex domain. Cynefin helps explain why agile fails when misapplied to clear or chaotic contexts.

  • Fog of War

    Decide with incomplete information and changing conditions.

  • OODA Loop

    Observe, orient, decide, act, then repeat faster with better learning.

  • Map Is Not Territory

    Models are abstractions, not reality itself.