methodatlas

Decision Making Decision method

Cynefin Workshop

A Cynefin workshop sorts cases into suitable domains and derives actions that fit their degree of clarity or complexity.

A Cynefin workshop classifies situations by their degree of order, uncertainty, and complexity. The classification indicates where analysis, experiments, or rapid stabilisation fit.

Core question
Which context does each concrete case inhabit, and which decision logic fits it?
Participants
4-20
Time
90–150 minutes for 12–30 concrete cases and derived response logics.

The steps express the method mechanics; feedback may reopen an earlier step.

Paper illustration for Cynefin Workshop.
  1. Cases

    Granular case set

    Capture concrete situations as short stories with trigger, observed course, and current decision need.

  2. Domains

    Shared domain criteria

    Explain Clear, Complicated, Complex, Chaotic, and Confused through causality and matching response logic.

  3. Sort

    Provisional domain map

    Place cases individually first, then compare rationale and evidence; keep genuine uncertainty in Confused.

  4. Boundaries

    Resolved boundary cases

    Examine disputed cases, movement between domains, and the Clear-to-Chaotic cliff; decompose bundles when needed.

  5. Respond

    Context-aware action plan

    Choose a domain-appropriate response for each case; for complex cases define safe-to-fail probes and signals.

At review, add evidence, update assumptions, and version the next cycle.

A good fit when

Wenn Probleme unklar, chaotisch oder nur scheinbar bekannt sind, greifen Standardrezepte zu kurz. Ein Cynefin Workshop sortiert Situationen nach ihrer Problemart und verbindet sie mit passender Handlungslogik.

Ideal for

  • Strategy work
  • Incident learning
  • Complexity sensemaking

Not good for

  • Pure prioritization without context
  • Teams unwilling to work with ambiguity

Outputs

  • Context-aware action plan

    Cynefin case map with domain rationale, boundary cases, and a matching response for each case.

Cynefin Workshop · working structure

Fictional example

Fictional values demonstrate the method-specific fields.

Cynefin Workshop · working structure
CaseEvidenceCausalityDomainResponseNext step
Returns routineAdd rationale and evidence.Same flow in 17 casesCause and effect knownClearSense–categorise–respondContinue standard
Machine selectionAdd rationale and evidence.Three viable technical modelsSeveral right answers; expertise requiredComplicatedSense–analyse–respondExpert comparison
Express congestionAdd rationale and evidence.Patterns differ by SaturdayEffect only clear in hindsightComplexProbe–sense–respondTwo safe slot probes
Coolant leakAdd rationale and evidence.Immediate hazardNo time for analysisChaoticAct–sense–respondIsolate, then reassess
  1. 1. Evidence

    Returns routine
    Same flow in 17 cases
    Machine selection
    Three viable technical models
    Express congestion
    Patterns differ by Saturday
    Coolant leak
    Immediate hazard
  2. 2. Causality

    Returns routine
    Cause and effect known
    Machine selection
    Several right answers; expertise required
    Express congestion
    Effect only clear in hindsight
    Coolant leak
    No time for analysis
  3. 3. Domain

    Returns routine
    Clear
    Machine selection
    Complicated
    Express congestion
    Complex
    Coolant leak
    Chaotic
  4. 4. Response

    Returns routine
    Sense–categorise–respond
    Machine selection
    Sense–analyse–respond
    Express congestion
    Probe–sense–respond
    Coolant leak
    Act–sense–respond
  5. 5. Next step

    Returns routine
    Continue standard
    Machine selection
    Expert comparison
    Express congestion
    Two safe slot probes
    Coolant leak
    Isolate, then reassess

All values are fictional.

Reference · original teaching example

First step

Bound one decision landscape and collect 12–30 concrete situations rather than abstract themes.

Open the method guide

Deep dive

Purpose

When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.

How it works

Cases are classified not by gut feeling but by the kind of order, uncertainty, or complexity they involve. This shows where analysis, where experimentation, and where fast stabilization make sense. It strengthens shared sensemaking ahead of premature solutions.

In detail

A Cynefin Workshop uses the framework as a sorting and conversation surface for real situations. Challenges are not only evaluated but also examined for the kind of causality, uncertainty, and action logic they contain. That helps teams distinguish whether best practices, expertise, experiments, or immediate stabilization are appropriate. The output is a situational map with differentiated next steps.

Facilitation

Prepare clear domain descriptions, real cases, and a large sorting surface. Have participants place examples individually first and then discuss the differences. Avoid long framework lectures; work quickly with concrete situations and derive action principles from them.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics
Artifact templates
Cynefin Workshop: WorksheetSet subject, evidence, roles, flow, and review.
markdown

cynefin-workshop-working-template.md

Set subject, evidence, roles, flow, and review.

Cynefin Workshop: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 90–150 minutes for 12–30 concrete cases and derived response logics.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Concrete case cards, Cynefin domain surface, evidence notes, boundary area, and action log
  • Roles: Facilitator experienced with Cynefin · case owners · domain perspectives · decision owner for experiments and stabilisation
  • Advance information: Bound one decision landscape and collect 12–30 concrete situations rather than abstract themes.
  • Overall time needed: 90–150 minutes for 12–30 concrete cases and derived response logics.
  • Setup: Divide the workspace into Collect cases · Calibrate domains · Sort independently · Test boundaries · Match response; keep sources, assumptions, and decisions separate.

Prepare for the work steps

Cases: Granular case set

  • Bound one decision landscape and collect 12–30 concrete situations rather than abstract themes.
  • Concrete case cards, Cynefin domain surface, evidence notes, boundary area, and action log

Domains: Shared domain criteria

  • Granular case set

Sort: Provisional domain map

  • Shared domain criteria

Boundaries: Resolved boundary cases

  • Provisional domain map

Respond: Context-aware action plan

  • Resolved boundary cases

Cynefin Workshop · working structure

CaseEvidenceCausalityDomainResponseNext step
Returns routine
Machine selection
Express congestion
Coolant leak
  • Returns routine: Add rationale and evidence.
  • Machine selection: Add rationale and evidence.
  • Express congestion: Add rationale and evidence.
  • Coolant leak: Add rationale and evidence.

The blank worksheet contains prompts only.

Reference · original teaching example

Cases: Granular case set

Expected artifact: Granular case set

Capture concrete situations as short stories with trigger, observed course, and current decision need.

Entry:

...

  • Does each card describe an actual case rather than a category or solution wish?

Domains: Shared domain criteria

Expected artifact: Shared domain criteria

Explain Clear, Complicated, Complex, Chaotic, and Confused through causality and matching response logic.

Entry:

...

  • Can everyone explain domains through causality and response rather than importance or difficulty?

Sort: Provisional domain map

Expected artifact: Provisional domain map

Place cases individually first, then compare rationale and evidence; keep genuine uncertainty in Confused.

Entry:

...

  • Is every placement justified by observable causality or lack of predictability?

Boundaries: Resolved boundary cases

Expected artifact: Resolved boundary cases

Examine disputed cases, movement between domains, and the Clear-to-Chaotic cliff; decompose bundles when needed.

Entry:

...

  • Are divergent placements, domain movement, and subproblems visible?

Respond: Context-aware action plan

Expected artifact: Context-aware action plan

Choose a domain-appropriate response for each case; for complex cases define safe-to-fail probes and signals.

Entry:

...

  • Does each action match domain logic and have an owner, signal, and review?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/cynefin-workshop/run-sheet

Alternatives and neighbors

Fitting alternatives with decision guidance, followed by other related methods.

All methods
Constraints and origin
MediumWorkshop60-180 min

Profile

Method form
Decision method
Participants
4-20
Time
60-180 min
Maturity
Established
Origin
Dave Snowden
Paper illustration for OODA Loop.
Next up: OODA Loop