Skip to content

Decision Frameworks Are Tools, Not Religions

No single decision framework fits every problem. Select Cynefin, OODA, RAPID, or commander's intent by complexity, reversibility, and time horizon, set a deadline, and record the decision.

Framework fluency, knowing which decision framework fits which problem, matters more than loyalty to any single one. Classify the decision by complexity with Cynefin and by reversibility with the one-way and two-way door test, then match it to OODA, RAPID, probe-sense-respond, scenario analysis, or commander’s intent.

Why does framework loyalty fail?

Framework loyalty fails because decision problems vary across several dimensions (complexity, stakes, and reversibility), and no single framework addresses all configurations of these dimensions.

I watched a product team apply the Cynefin framework to a reversible pricing experiment that needed a quick OODA loop, not a prolonged sense-making exercise. I watched an executive team apply RAPID to a complex organizational restructuring that required emergent strategy, not predefined decision rights. In both cases, the framework was sound. The application was wrong. The teams were fluent in their chosen framework and illiterate in the landscape of alternatives.

How do you select the right framework for the right problem?

Select by classifying the decision along several axes: complexity (simple, complicated, complex, chaotic), stakes (reversible or irreversible), and time horizon (hours, weeks, months).

Step 1: Classify the problem complexity using Cynefin

Before choosing a decision framework, determine the nature of the problem. Simple problems have clear cause-and-effect (use a checklist). Complicated problems have discoverable cause-and-effect (use expert analysis). Complex problems have emergent cause-and-effect (use probe-sense-respond). Chaotic problems have no perceivable cause-and-effect (use act-sense-respond). This classification takes little time and prevents the most common error: applying analytical tools to complex problems that require experimentation.

Step 2: Assess reversibility

Jeff Bezos’s framework of one-way and reversible doors remains the most useful reversibility test. Irreversible decisions are one-way doors (organizational restructuring, major platform migrations, pricing model changes). Reversible decisions are doors you can walk back through (feature launches, process experiments, tool trials). Irreversible decisions deserve far more deliberation than reversible decisions. Most organizations apply irreversible-decision rigor to reversible decisions, which produces analysis paralysis, or reversible-decision speed to irreversible decisions, which produces costly mistakes.

Step 3: Match the framework to the classification

  • Simple + Reversible: No framework needed. Decide and move. If you are spending more than 15 minutes on a reversible decision with clear cause-and-effect, you are over-engineering.
  • Complicated + Reversible: Use OODA (Observe, Orient, Decide, Act). Set a tight loop of short cycles and iterate. Good for pricing experiments, process changes, tool evaluations.
  • Complicated + Irreversible: Use RAPID (Recommend, Agree, Perform, Input, Decide). Define clear decision rights and ensure the right expertise is consulted. Good for vendor selections, architecture decisions, hiring.
  • Complex + Reversible: Use probe-sense-respond from Cynefin. Run small experiments in parallel, measure outcomes, amplify what works. Good for market entry, product-market fit exploration, organizational change.
  • Complex + Irreversible: Use a structured decision analysis with scenario planning. Document assumptions explicitly. Seek disconfirming evidence. Set decision criteria before evaluating options. Good for M&A, major pivots, platform bets.
  • Chaotic: Use commander’s intent. Define the outcome, not the method. Empower the nearest competent person to act. Review and adjust after stability is restored. Good for incident response, crisis management, market disruptions.

Step 4: Set the decision deadline before starting deliberation

Every decision has a cost of delay. A high daily revenue impact means each day of deliberation carries a real cost, in addition to whatever the decision framework consumes. I set explicit decision deadlines based on cost of delay: reversible decisions get the shortest deadlines, complicated irreversible decisions get longer ones, and complex irreversible decisions get the longest. No decision runs past a fixed outer limit. If you cannot decide in 30 days, you do not have a decision problem. You have an information problem.

Step 5: Document the decision, not just the outcome

Record which framework you used, why you chose it, what alternatives you considered, and what you would watch for to know if the decision was wrong. This creates a feedback loop for improving your framework selection over time. After a sustained period of documenting decisions, patterns emerge: which types of problems you consistently over-analyze, which types you consistently under-analyze, and which frameworks produce the best outcomes for your specific organizational context.

What does framework fluency look like in practice?

Framework fluency means a team can identify the decision type, select the appropriate framework, and begin deliberation quickly rather than defaulting to their comfort zone.

I trained leadership teams in this selection methodology. After sustained practice, the average time from “we need to make a decision” to “we are using this framework and here is our deadline” dropped from days (the time previously spent debating how to decide) to minutes. The quality of decisions, measured by post-decision regret surveys taken after the fact, improved markedly compared to the pre-training baseline.

The goal is not to master every framework. It is to know enough about each one to recognize when it fits. A carpenter who only owns a hammer will use it on screws. A carpenter with a full toolbox will reach for the right tool without thinking about it. Decision frameworks are tools. Treat them accordingly.

adam@adam-analytics.com writes about AI systems, software architecture, and the philosophy of technology at .