Complexity Domains Sorting

Purpose

The complexity domains framework, developed by Dave Snowden, is a sense-making tool that helps groups understand what kind of situation they are in before deciding how to act. Different domains demand different approaches: Clear situations need best practices, Complicated ones need expert analysis, Complex ones need experiments, and Chaotic ones need immediate action. Mismatching the approach to the domain is one of the most common management mistakes.

At a glance

How to run

1. Introduce the framework (10 min). Draw the complexity domains diagram: Clear (bottom-right), Complicated (top-right), Complex (top-left), Chaotic (bottom-left), Confused (center). Explain each domain and its response mode:

• Clear: Sense → Categorize → Respond (apply best practice)
• Complicated: Sense → Analyze → Respond (consult experts)
• Complex: Probe → Sense → Respond (run safe-to-fail experiments)
• Chaotic: Act → Sense → Respond (stabilize first)

1. List current challenges (10 min). Each person writes 2–3 current challenges on sticky notes.
2. Place on the framework (10 min). One by one, participants place their challenges on the complexity domains diagram and briefly explain why. The group discusses placement — disagreements are valuable.
3. Match strategies (10 min). For each cluster, identify the appropriate response strategy. Are we using the right approach for this domain? Where are we applying complicated thinking to complex problems (a common error)?
4. Action commitments (5 min). For the most important mismatched challenges, commit to trying the domain-appropriate approach.

Materials needed

• Large complexity domains diagram on wall or whiteboard
• Sticky notes and markers
• Domain response cheat sheet per participant
• Timer

Pitfalls & common mistakes

• Treating the framework as a categorization tool. It is a sense-making framework — situations shift between domains. The boundary between Complex and Chaotic is especially dynamic.
• Defaulting to Complicated. Most managers are trained in expert analysis. When faced with complexity, they commission more analysis instead of running experiments.
• Confusing "Clear" with "Easy." Clear means the cause-effect relationship is obvious — not that it is easy to implement.
• Ignoring the "Confused" domain. If you do not know which domain you are in, you are in Confused. That is the starting point, not a failure.

Inclusion & accessibility

• The framework gives language to intuitions that diverse team members may already have.
• Frontline workers often have better sense-making about complexity than managers — include them.
• Use visual placement (sticky notes on diagram) so all participants can engage.
• Provide a plain-language explanation of each domain.

Variations

• Complexity domains for retrospectives: Categorize past incidents by domain and assess whether the response matched.
• Complexity domains for strategy: Map strategic initiatives across domains.
• Domain dynamics: Discuss how challenges might move between domains over time.

When NOT to use this

• When the group is in genuine chaos and needs immediate action, not sense-making.
• When a simpler framework would suffice (not every decision needs this framework).
• When the group is not willing to accept that some problems cannot be analyzed into solutions.

Source & further reading

• Snowden, D. J. & Boone, M. E. (2007). "A Leader's Framework for Decision Making." *Harvard Business Review*, Nov.
• Snowden, D. J. (2002). "Complex Acts of Knowing." *Journal of Knowledge Management*, 6(2).
• Cognitive Edge / Cynefin Co. https://thecynefin.co