methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session90-180 minWorkshopCynefin Map

Session: Cynefin Workshop

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 4-20. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Cynefin Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 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. Hint: If theory runs too long, energy for classification drops. Keep intro to 20 min, then map examples from the plenary.

    FacilitatorCynefin Map
  2. 2

    Phase 2: Solo classification

    15 min

    Each participant individually places all situations on a personal map copy. Note rationale briefly for each situation. Hint: Solo phase prevents groupthink. If discussion starts immediately, individual perspective is lost. Enforce silence.

    FacilitatorDomain-specific Actions
  3. 3

    Phase 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. Hint: 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.

    FacilitatorSensemaking Notes
  4. 4

    Phase 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. Hint: Without implications Cynefin becomes a sorting exercise. Name owner and next step per situation, otherwise workshop becomes filing exercise.

    FacilitatorCynefin Map
  5. 5

    Phase 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). Hint: A common organizational error is treating complex as complicated (plan-driven), or bringing complex thinking back into complex. Reflection makes these patterns visible.

    OwnerDomain-specific Actions
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerCynefin Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Cynefin Workshop

Goal

Artifact: Cynefin Map

Working Question

In which Cynefin domain is each listed situation, and which response logic (Sense-Categorize-Respond through Act-Sense-Respond) is therefore appropriate?

Context

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.

Setup

  • Format: Method session
  • Duration: 90-180 min
  • Mode: Workshop
  • Participants: 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.
  • Owner: A facilitator with Cynefin knowledge
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Cynefin Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

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.

Preparation

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.

Agenda

  1. Phase 1: Framework introduction (20 min) Owner: Facilitator Action: 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. Hint: If theory runs too long, energy for classification drops. Keep intro to 20 min, then map examples from the plenary. Output: Cynefin Map

  2. Phase 2: Solo classification (15 min) Owner: Facilitator Action: Each participant individually places all situations on a personal map copy. Note rationale briefly for each situation. Hint: Solo phase prevents groupthink. If discussion starts immediately, individual perspective is lost. Enforce silence. Output: Domain-specific Actions

  3. Phase 3: Shared classification by situation (60-90 min) Owner: Facilitator Action: 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. Hint: 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. Output: Sensemaking Notes

  4. Phase 4: Derive implications (30-45 min) Owner: Facilitator Action: 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. Hint: Without implications Cynefin becomes a sorting exercise. Name owner and next step per situation, otherwise workshop becomes filing exercise. Output: Cynefin Map

  5. Phase 5: Reflection and risks (20-30 min) Owner: Owner Action: 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). Hint: A common organizational error is treating complex as complicated (plan-driven), or bringing complex thinking back into complex. Reflection makes these patterns visible. Output: Domain-specific Actions

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Cynefin Map

Closeout

  • Update result artifact: Cynefin Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Cynefin Map: Cynefin Workshop

Working Question

In which Cynefin domain is each listed situation, and which response logic (Sense-Categorize-Respond through Act-Sense-Respond) is therefore appropriate?

Context

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.

Participants

  • Owner: A facilitator with Cynefin knowledge
  • Participants: 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.

Input

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.

Template

Cynefin Workshop Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Cynefin Map:
  • Domain-specific Actions:
  • Sensemaking Notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Cynefin Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Cynefin Workshop Working Template

View templateCompact working template for Cynefin Workshop with context, input, output artifacts, and next step.
canvas

cynefin-workshop-working-template.md

Compact working template for Cynefin Workshop with context, input, output artifacts, and next step.

Cynefin Workshop Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Cynefin Map:
  • Domain-specific Actions:
  • Sensemaking Notes:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Cynefin Map.
  • 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.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.