What needs to be finished first
A list of situations, problems, or decisions is available to map (at least 8-15 items).
Relevant perspectives and decision makers are identified and represented in the workshop.
What needs to be ready before start
Large whiteboard or digital board with Cynefin map (clear, complicated, complex, chaotic, unclear in the center); sticky notes per situation; markers; wall poster with domain characteristics; timer.
A facilitator with Cynefin knowledge; 5-12 participants with context knowledge on the situations; a scribe who captures rationale for each classification; optional coach for content clarification.
Situation list sent at least one day before; Cynefin framework with domain definitions; note that this is not about finding the one correct answer but building shared understanding.
90-180 min
Place the Cynefin map centrally. Label domains with characteristics: clear (cause obvious, Sense-Categorize-Respond), complicated (expertise needed, Sense-Analyze-Respond), complex (patterns only known in hindsight, Probe-Sense-Respond), chaotic (Act-Sense-Respond), unclear in the center. Prepare sticky notes for each situation.
The one question this method answers
In which Cynefin domain is each listed situation, and which response logic (Sense-Categorize-Respond through Act-Sense-Respond) is therefore appropriate?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Framework introduction | 20 min | Facilitator introduces the five domains with examples from the work context. Explain characteristics and matching response logic for each domain. Clarify difference between clear and complicated, complicated and complex with concrete examples. | If theory runs too long, energy for classification drops. Keep intro to 20 min, then map examples from the plenary. |
2Phase 2: Solo classification | 15 min | Each participant individually places all situations on a personal map copy. Note rationale briefly for each situation. | Solo phase prevents groupthink. If discussion starts immediately, individual perspective is lost. Enforce silence. |
3Phase 3: Shared classification by situation | 60-90 min | For each situation, participants place their classification on the common map simultaneously. If diverging, discuss and exchange rationale, then agree on shared classification. Scribe documents. | Divergence is useful. If everyone classifies identically, either diversity is missing or the situation is actually clear. If disagreement persists, document both views and discuss switch hypothesis. |
4Phase 4: Derive implications | 30-45 min | Group by domain and define what fits: for complex, probe instead of plans; for complicated, use expertise instead of improvisation; for chaotic, stabilize before analysis. Define concrete next steps per situation. | Without implications Cynefin becomes a sorting exercise. Name owner and next step per situation, otherwise workshop becomes filing exercise. |
5Phase 5: Reflection and risks | 20-30 min | Reflect: which situations were handled in the wrong domain, what consequences followed, which domain transitions are expected in the future (for example complex to complicated after probes). | A common organizational error is treating complex as complicated (plan-driven), or bringing complex thinking back into complex. Reflection makes these patterns visible. |
What comes out at the end
Photo or digital Cynefin map with all situations mapped, plus per-situation rationale for domain, derived response logic, and concrete next step with owner. Optionally include overview table with status and domain transitions.
Record date, team, and situation list in header. For follow-up workshop, compare previous iteration and explicitly mark domain shifts, often complex to complicated after successful probes.
Compact working template for Cynefin Workshop with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Participants: 9 people from Product, Engineering, Ops. Situations: 11.
In the last 3 months, 3 of 4 complex situations were handled as complicated (roadmap with fixed delivery date), resulting in constant delays. New mode: for complex situations, use probes instead of plans and review after 4 weeks.
Recognize symptoms and steer against them
Workshop stays in definition debates ("Is Disorder a domain or just transition?") and no situations are classified.
Limit theory phase to 20 minutes. Keep definitions practical. Document disagreements for later and move immediately into concrete classification practice.
Situations are classified as complicated because the team likes it to be predictable, even though they are actually complex.
Test question: "Can we know the result in advance?" If no, it is not complicated. Keep domain diversity in the room. If consensus is "complicated," assign a devil's advocate.
Routine work ends up in "complicated" because the team does not do it often. Domain boundary becomes blurry.
Clear means standard, established best practice everyone can follow. Complicated means expert required. Question "Is there a best practice?" creates separation.
Acute crisis situations are classified as complex and team starts analysis instead of stabilization.
Chaotic requires Act-Sense-Respond: stabilize first, then understand. If damage increases each minute, domain is chaotic and analysis is wrong.
Map is sorted but workshop ends and team works as before.
Define concrete next step with owner and date for each situation. Domain changes action logic; without owner, Cynefin remains a sorting exercise.
Participants classify situations they do not know personally; outcomes are arbitrary.
Ensure each situation has at least one participant with first-hand context. If not, remove situation from workshop or require pre-read briefing.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.