Complexity Domain Sort

The Complexity Domain Sort triages a situation by how knowable its causal structure is, then picks the response posture that fits: sense-categorize-respond for the clear, probe-sense-respond for the complex, and so on. It is descriptively named here; the framework it derives from is Cynefin, and its evidence is conceptual only. This skill runs the sort honestly. It leads with that caveat, then forces the one thing the bare label omits and that makes the sort worth running at all: a concrete next action tied to the domain, because saying "this is complex" is not a decision.

Before you run this: the evidence caveat

This sort is descriptively named; the framework it derives from is Cynefin, a trademark of The Cynefin Co. (Dave Snowden, 1999). Its evidence is tier C (conceptual): it is a coherent, widely taught sense-making heuristic, but no controlled study shows that classifying a problem this way improves decisions versus not classifying it. The 2021 PMC review applying it to internal-medicine diagnostic reasoning states the point plainly: the framework "is now widely used for teaching and as a simple heuristic; however, scientific proof of its validity has yet to be provided." The dominant failure mode is the cargo cult: stopping at the label ("ah, this is complex, we should probe") is satisfying to say and changes nothing. So the placement is a contested framing, not a found fact, and the deliverable is the next action it implies, not the bucket name.

When to Use

• The user asks for this complexity sort (or Cynefin) by name and you should run it honestly rather than refuse.
• A team is applying the wrong management style to the problem type (running an emergent initiative on a rigid best-practice plan, or smothering a routine task in deliberation) and naming that mismatch out loud would help.
• As a front end to picking how to act, where the value is legitimizing safe-to-fail experiments in the complex domain and flagging the confusion trap, not the five-box picture.

When NOT to Use