Coding

thinking-cynefin

Try it

When the right response mode is unclear, classify the cause-effect domain first; decompose disorder.

What it does

When the right response mode is unclear, classify the cause-effect domain first; decompose disorder.

The skill document

Cynefin Classification

Classify by cause-effect, then use only the matching response mode. Wrong-domain method is the failure mode.

When to Use

  • Unsure whether to run a playbook, analyze, probe, or stabilize.
  • A method keeps failing and domain mismatch is plausible.
  • A novel or mixed problem needs approach selection before solution work.

When NOT to Use

  • Domain and method are already agreed—execute.
  • Task is finding a specific cause, not choosing an approach.
  • Classification done; switch to the domain method—do not re-label endlessly.
  • Pure mechanical edits with no approach uncertainty.

Procedure

  1. State the unit. Name the decision, incident, or subsystem; if mixed, list separable parts.
  2. Probe cause-effect. Is the link obvious, expert-analyzable, retrospective only, or imperceptible in turbulence? Check predictability, urgency, and probe safety.
  3. Assign one domain per unit:
    • Clear — obvious → Sense → Categorize → Respond with a runbook.
    • Complicated — expert-analyzable → Sense → Analyze → Respond; several valid answers.
    • Complex — emergent → Probe → Sense → Respond with safe-to-fail probes; amplify/dampen signals.
    • Chaotic — no safe sensing time → Act → Sense → Respond; stabilize first.
    • Disorder — unknown → split and classify each part.
  4. Mismatch check. Reject Clear if its runbook fails; Complicated if analysis cannot predict; Complex if probing is unsafe; Chaotic once safe probing becomes possible.
  5. Commit and stop. Output domain + first actions. Re-classify only on evidence of domain shift.

Stop when every unit has one domain, first actions, and a falsifier—or disorder is decomposed.

Output

unit: 
domain: clear | complicated | complex | chaotic | disorder
evidence: 
response_mode: 
first_actions: <1-3 concrete steps>
falsifier: 
parts: 

Verification

  • Falsify: Reliable prediction → not Complex. No safe probe → Chaotic. Working runbook → Clear.
  • Stop: Stop classifying once the matched action is clear.
  • Over-application guard: Do not call work Complex to avoid analysis or Complicated to avoid a standard fix. One label per unit; decompose multi-domain work.

Related skills

Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.

1 installs

Activate when: 'our best practices keep failing', 'experts disagree on the right answer', 'the old playbook isn't working', 'we're in crisis and don't know w...

1 installs3 stars

When unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).

2 installs

Use when search or investigation could run forever. Set an explicit good-enough threshold first, then stop at the first option that clears it.

1 installs

When one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.

1 installs

Deciding what to build or why adoption fails. Recover the progress users hire a solution for under a circumstance, then rank by outcome and competing workarounds.

1 installs