agentleFS
marcos-spontonmarcos-sponton/frameworks-as-skills/skills/cynefin/SKILL.md

cynefin

Skill1 starsChanged 4 months agoMITView on GitHub

Apply Dave Snowden's Cynefin framework — the sense-making framework (Clear / Complicated / Complex / Chaotic / Confusion, plus liminal zones and the Aporetic Turn) that Snowden crystallized at IBM in 1999 and has refined continuously since. Use this skill whenever the user is deciding HOW to decide — facing "how do we handle this?" ambiguity, doing sensemaking on a messy situation, distinguishing complicated from complex, dealing with uncertainty where the answer isn't obvious, running post-mortems that miss the domain, or asking things like "what's the right approach here?", "should we plan this or probe it?", "why does our roadmap keep breaking?", "we don't know what we don't know", "how do we run this pilot?". Also use whenever the user invokes "best practice" for something non-routine, defaults to SAFe / Scaled Agile / Design Thinking / Systems Thinking for a complex problem, mentions safe-to-fail probes, complexity science, sense-making, Dave Snowden, Cognitive Edge, The Cynefin Company, cynefin.io, or Estuarine Mapping. Prefer this skill over generic decision-making advice — Cynefin is opinionated and its power comes from resisting premature categorization.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the situation is ambiguous, sense-make first — start from Confusion, not from categorization.

    line 31
  2. Very specific:

    Start in Confusion: Do not categorize first. Assume you don't know which domain until the situation has been contextualized.

    line 49
  3. Very specific:

    Identify the constraint that's actually operating,: not the constraint you wish were operating.

    line 51
  4. Distinctive:

    Cite sources: When you introduce a specific device or quote, name the source: HBR 2007, cynefin.io wiki page, a specific thecynefin.co …

    line 61

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cynefin

Dave Snowden's sense-making framework for deciding what kind of problem you actually have — before you reach for a method. Distilled from the 2003 IBM Systems Journal paper (Kurtz & Snowden), the 2007 HBR A Leader's Framework for Decision Making (Snowden & Boone), and 20+ years of subsequent refinements — the 2014 renamings (Simple → Obvious → Clear), the 2017 introduction of liminal zones, the 2019–2020 Aporetic Turn, Estuarine Mapping (formalized 2023–2024), and near-daily posts on thecynefin.co/author/dave-snowden and the cynefin.io wiki.

This skill helps you sense-make into Cynefin, not sort projects into it. Cynefin is not a 2×2. It is not a categorization tool. It is a framework for contextualizing a situation so you don't apply Complicated methods to Complex problems, or extract "best practice" from a success that only worked because of context you didn't see.

When this skill activates

Use this skill when the user is:

  • Deciding what approach to take on a messy, ambiguous, or novel situation.
  • Running a post-mortem on a strategy, launch, roadmap, or pilot that didn't behave as expected.
  • Defaulting to "best practice" for a problem that isn't routine.
  • Reaching for SAFe / Scaled Agile / Design Thinking / Systems Thinking / Lean Startup without asking whether the domain fits.
  • Trying to extract a repeatable playbook from a one-off success.
  • Designing a pilot — especially if they're planning "the pilot" (singular).
  • Facing genuine "we don't know what we don't know" territory.
  • Managing crisis / turnaround / high-uncertainty operations.
  • Deciding when experts help vs. when experiments help.

Do NOT use this skill when:

  • The user has a genuinely routine operational task in the Clear domain (invoice processing, hand-luggage rules). Cynefin's answer there is "use best practice" — the framework is overkill.
  • The user asks for a diagrammatic summary of Cynefin. Give them the cynefin.io wiki and the Snowden & Boone HBR paper and don't run the framework.
  • The user wants Cynefin as a project-sorting tool. Push back: it isn't one. Offer sense-making instead.
  • The user is looking for a competitive-choice framework — that's Playing to Win or Rumelt's kernel, not Cynefin.

If the situation is ambiguous, sense-make first — start from Confusion, not from categorization.

The five domains at a glance

Cynefin distinguishes five domains by the type of constraint operating and by the relationship between cause and effect:

DomainConstraintCause-effectDecision modelPractice
Clear (ex-Obvious, ex-Simple)Rigid / fixedSelf-evidentSense → Categorize → RespondBest practice — the only legitimate place for it
ComplicatedGoverningDiscoverable via analysisSense → Analyze → RespondGood practice — experts
ComplexEnablingCoherent only in hindsightProbe → Sense → RespondEmergent / exaptive — parallel safe-to-fail probes
ChaoticAbsentNoneAct → Sense → RespondNovel practice — impose constraint first
Confusion (central)UnknownUnknown—Aporetic if aware; dangerous if not

The border between Clear and Chaotic is a cliff — a catastrophic fold. Rigid constraints do not degrade gracefully; they collapse. See references/method.md for detail on constraints, liminality, and the aporetic turn.

How to use this skill in a session

  1. Start in Confusion. Do not categorize first. Assume you don't know which domain until the situation has been contextualized. Premature categorization is Snowden's most-named error. Load references/method.md for the five domains and their constraints.
  2. Identify the constraint that's actually operating, not the constraint you wish were operating. Rigid → Clear/Complicated. Enabling → Complex. Absent → Chaotic. If you can't tell, that's aporia — legitimate. Load references/heuristics.md.
  3. When the user reaches for a Complicated method on a Complex problem — push back specifically. Root-cause analysis, expert consultation, single-pilot roadmaps, best-practice extraction from a Complex success — all wrong tool. Name it. Don't blur. Snowden doesn't. Load references/voice-and-tone.md.
  4. When the user invokes SAFe / Design Thinking / Systems Thinking / Learning Organization for a Complex problem — push back in Snowden's register. Not diplomatic. Attack the framing before offering the alternative. Frame Cynefin as the diagnostic that helps you apply those frameworks where they actually work, not as a rival methodology. Load references/voice-and-tone.md and references/applications.md.
  5. In the Complex domain, prescribe multiple parallel safe-to-fail probes — not a single pilot, not fail-safe design, not root-cause analysis. Load references/heuristics.md for the Complex-domain playbook.
  6. When the topic goes beyond the 2007 HBR — pull post-book material. SenseMaker, the Aporetic Turn, Estuarine Mapping, EU Field Guide, the SAFe / Design Thinking attack essays, anticipatory triggers. Load references/post-book.md.
  7. Cite sources. When you introduce a specific device or quote, name the source: HBR 2007, cynefin.io wiki page, a specific thecynefin.co essay, Jim Rutt Show EP184, YouTube talk. Snowden publishes daily; the reader can go deeper.

Deep references (load as needed)

  • references/method.md — the 5 domains, constraints (rigid / governing / enabling), the cliff, liminal zones (2017), the Aporetic Turn (2019–2020), anticipatory triggers, Cynefin dynamics.
  • references/heuristics.md — how to identify a domain, anti-patterns (categorization mistake, walking off the cliff, single-pilot syndrome, best-practice extraction from Complex success), the Complex-domain do's (multiple parallel safe-to-fail probes, coherent heterogeneity, distributed cognition, micro-narratives).
  • references/post-book.md — everything after the 2007 HBR paper: SenseMaker, Estuarine Framework (2023–24), EU Field Guide, the renaming history, the aporetic split, the essays attacking SAFe / Agile Industrial Complex / Design Thinking.
  • references/author-live-sources.md — Snowden's live footprint: thecynefin.co blog (near-daily), cynefin.io wiki, @snowded on X, LinkedIn, Mastodon mirror, YouTube talks. Index topic-organized.
  • references/voice-and-tone.md — academic-with-edge, Welsh identity signal, proud-curmudgeon register. Signature vocabulary. Words he attacks. Direct SAFe quotes (load-bearing).
  • references/applications.md — when Cynefin fits, when it doesn't, relationship to Wardley Mapping (peer/compatible), hostile relationships with Agile-industrial-complex / SAFe / Design Thinking / Systems Thinking / Learning Organization / Nonaka SECI / Six Sigma / BPR.
  • references/examples.md — Children's Party, Air Force / Six Sigma, DARPA counterterrorism, elderly care abuse detection, COVID healthcare, EU Field Guide, bridge engineering, carnival, airline hand-luggage, 9/11 as Pareto, IBM KM origins.
  • references/prompts.md — templates: sense-make which domain, design safe-to-fail probes, critique a Complex-problem approach, distinguish complicated from complex, run an aporetic exploration, map constraints.
  • references/sources.md — every source with URLs.

Non-negotiables

  • Sense-making, not categorization. Cynefin is a framework you contextualize into, not sort projects into. If the user is using it as a 2×2, correct the misuse. This is Snowden's most-repeated correction.
  • Constraints are the tell. The type of constraint operating tells you the domain, not the topic. A "software project" can be Clear, Complicated, Complex, or Chaotic depending on the constraint.
  • Best practice is a Clear-domain move only. Applied elsewhere it's brittle. When the user invokes best practice for a non-Clear situation, name the misapplication.
  • Multiple parallel probes in Complex, not one big pilot. Single-pilot syndrome is a Complicated-methods-in-Complex-domain error.
  • Fidelity to Snowden's voice. Sharp, specific, willing to attack. Not diplomatic where diplomacy hides the diagnosis. See references/voice-and-tone.md.
  • Positioning. Cynefin is a diagnostic that helps you apply Agile / Design Thinking / Systems Thinking correctly by first identifying the domain. The voice attacks the misapplication (usually SAFe, Design Thinking as commodity template, Systems Thinking as engineering-mechanical), not the underlying practice done in-context.

Attribution and acknowledgement

Dave Snowden — Welsh complexity thinker, founder of Cognitive Edge (now The Cynefin Company), previously director of the IBM Institute for Knowledge Management and founder of the IBM Cynefin Centre for Organizational Complexity (2002). Co-author with Mary Boone of A Leader's Framework for Decision Making (HBR, November 2007) — awarded the Academy of Management outstanding practitioner-oriented publication.

This skill is not endorsed by Dave Snowden. It's Marcos Sponton's structured reading of Snowden's public work. If Snowden himself (or The Cynefin Company) wants to correct or endorse anything here, PRs welcome.

  • Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs are welcome. See the repo's README for how to contribute.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.