A comprehensive collection of 15+ proven decision-making frameworks used by leaders, strategists, and critical thinkers. Each framework includes a clear explanation, step-by-step process, when to use it, and real-world examples.
- Why Frameworks Matter
- Frameworks
- 1. OODA Loop
- 2. Eisenhower Matrix
- 3. Second-Order Thinking
- 4. Inversion
- 5. Pre-Mortem Analysis
- 6. 10/10/10 Rule
- 7. WRAP Framework
- 8. Six Thinking Hats
- 9. Cynefin Framework
- 10. Regret Minimization Framework
- 11. Pareto Analysis (80/20)
- 12. Decision Matrix (Weighted Scoring)
- 13. PDCA Cycle
- 14. Vroom-Yetton Decision Model
- 15. Kepner-Tregoe Analysis
- 16. Boyd's Law of Iteration
- 17. Reversible vs Irreversible Decisions
- Choosing the Right Framework
- Further Resources
- Contributing
- License
Every day we make thousands of decisions — from trivial choices to life-altering ones. Without a structured approach, we fall prey to cognitive biases, emotional reasoning, and analysis paralysis. Decision frameworks provide:
- Structure — A repeatable process to evaluate options
- Objectivity — Reduced influence of cognitive biases
- Speed — Faster decisions through systematic elimination
- Communication — A shared language for teams to discuss trade-offs
"The quality of your decisions determines the quality of your life." — Tony Robbins
Origin: Colonel John Boyd, U.S. Air Force fighter pilot strategist
The Cycle:
Observe → Orient → Decide → Act → (repeat)
How it works:
| Phase | Description | Key Question |
|---|---|---|
| Observe | Gather raw data from the environment | What is happening right now? |
| Orient | Analyze and synthesize observations using mental models, culture, experience | What does this mean? |
| Decide | Select a course of action from available options | What should I do? |
| Act | Execute the decision | Implement and observe the results |
When to use: Fast-changing environments, competitive situations, military/business strategy, startup pivots.
Example: A product manager notices user engagement dropping (Observe), identifies that a recent UI change caused confusion (Orient), decides to A/B test a rollback (Decide), and ships the test within 24 hours (Act).
Key insight: Speed through the loop matters more than perfection at any single stage. The entity that cycles through OODA fastest gains a decisive advantage.
Origin: Dwight D. Eisenhower, 34th U.S. President
The Matrix:
URGENT NOT URGENT
┌─────────────────┬─────────────────┐
IMPORTANT │ DO FIRST │ SCHEDULE │
│ Crisis, │ Strategic │
│ deadlines, │ planning, self- │
│ emergencies │ improvement │
├─────────────────┼─────────────────┤
NOT │ DELEGATE │ ELIMINATE │
IMPORTANT │ Interruptions,│ Time wasters, │
│ some meetings,│ busywork, │
│ some emails │ distractions │
└─────────────────┴─────────────────┘
When to use: Prioritizing daily/weekly tasks, managing workload, preventing burnout.
Common pitfall: Most people spend too much time in Quadrant 1 (Urgent + Important) and Quadrant 3 (Urgent + Not Important), neglecting Quadrant 2 (Not Urgent + Important) where the highest-leverage activities live.
Origin: Howard Marks, investor and author of The Most Important Thing
Process:
- Identify the first-order consequence of a decision
- Ask: "And then what?" for each consequence
- Map the chain of effects through 2-3 levels
- Evaluate the full cascade before deciding
Template:
Decision: [Your decision]
├── 1st Order: [Immediate effect]
│ ├── 2nd Order: [Effect of the effect]
│ │ └── 3rd Order: [Further downstream impact]
│ └── 2nd Order: [Another branch]
└── 1st Order: [Another immediate effect]
└── 2nd Order: [Its downstream impact]
Example:
Decision: Offer 50% discount to boost sales
├── 1st Order: Sales volume increases significantly
│ ├── 2nd Order: Customers anchor to discount price, resist full price later
│ │ └── 3rd Order: Brand positioned as "discount brand," margins permanently compressed
│ └── 2nd Order: Support team overwhelmed by volume
└── 1st Order: Competitors respond with their own discounts
└── 2nd Order: Price war erodes industry profitability
When to use: Strategic decisions, policy making, investment analysis, product launches.
Origin: Carl Jacobi (mathematician), popularized by Charlie Munger
Process:
- Define the goal you want to achieve
- Invert: Ask "What would guarantee failure?"
- List all the ways to fail
- Systematically avoid each failure mode
Example:
Goal: Build a successful startup
Inverted question: "How do I guarantee my startup fails?"
- Ignore customer feedback
- Burn through cash without tracking unit economics
- Hire based on resume alone, not culture fit
- Build features nobody asked for
- Avoid measuring anything
- Never talk to customers after launch
Now invert again: Do the opposite of each item above.
When to use: Goal setting, risk management, quality assurance, strategic planning.
Key insight: It's often easier to identify and avoid stupidity than to pursue brilliance. As Munger says: "All I want to know is where I'm going to die, so I'll never go there."
Origin: Gary Klein, research psychologist
Process:
- Assume the project has already failed spectacularly
- Each team member independently writes down reasons for the failure
- Share and consolidate the list
- Prioritize the most likely/impactful failure modes
- Create mitigation plans for each
Template:
## Pre-Mortem: [Project Name]
**Date:** [Date]
**Assumption:** The project launched and failed completely.
### Failure Reasons
| # | Failure Mode | Likelihood (1-5) | Impact (1-5) | Score | Mitigation |
|---|-------------|-------------------|---------------|-------|------------|
| 1 | [reason] | [1-5] | [1-5] | [LxI] | [plan] |
| 2 | [reason] | [1-5] | [1-5] | [LxI] | [plan] |When to use: Before launching any significant project or initiative.
Advantage over post-mortems: Prospective hindsight (imagining an event has already occurred) increases the ability to identify reasons for outcomes by 30%.
Origin: Suzy Welch, business writer
Process: Ask yourself three questions about the decision:
- How will I feel about this 10 minutes from now?
- How will I feel about this 10 months from now?
- How will I feel about this 10 years from now?
When to use: Emotionally charged decisions, impulsive situations, career choices, relationship decisions.
Example:
Should I confront my colleague about taking credit for my work?
- 10 minutes: Anxious, heart racing
- 10 months: Glad I stood up for myself, better working relationship
- 10 years: Won't remember the anxiety, but the pattern of self-advocacy shaped my career
Origin: Chip & Dan Heath, Decisive: How to Make Better Choices in Life and Work
W - Widen your options (avoid narrow framing)
R - Reality-test your assumptions (consider the opposite)
A - Attain distance before deciding (overcome short-term emotion)
P - Prepare to be wrong (bookend the future)
Detailed steps:
| Step | Action | Technique |
|---|---|---|
| Widen | Generate more than two options | "What would you do if none of these options were available?" |
| Reality-test | Seek disconfirming evidence | Run small experiments, find someone who's solved this before |
| Attain distance | Reduce emotional bias | 10/10/10 rule, "What would I advise my best friend?" |
| Prepare | Plan for multiple outcomes | Set tripwires, define success/failure criteria upfront |
Origin: Edward de Bono
Each "hat" represents a different thinking mode:
| Hat | Color | Focus | Key Question |
|---|---|---|---|
| 🔵 | Blue | Process & control | What's our thinking process? |
| ⚪ | White | Facts & data | What do we know? What data do we need? |
| 🔴 | Red | Emotions & intuition | What does my gut say? |
| ⬛ | Black | Risks & caution | What could go wrong? |
| 🟡 | Yellow | Optimism & benefits | What are the advantages? |
| 🟢 | Green | Creativity & alternatives | What else is possible? |
When to use: Group decision-making, brainstorming sessions, evaluating proposals.
Process: The facilitator (Blue Hat) guides the group through each hat sequentially. Everyone wears the same hat at the same time, preventing adversarial dynamics.
Origin: Dave Snowden, IBM Global Services
Categorizes situations into five domains:
┌───────────────────┬───────────────────┐
│ COMPLEX │ COMPLICATED │
│ │ │
│ Probe-Sense- │ Sense-Analyze- │
│ Respond │ Respond │
│ │ │
│ "Emergent │ "Good practice" │
│ practice" │ │
├───────────────────┼───────────────────┤
│ CHAOTIC │ CLEAR │
│ │ │
│ Act-Sense- │ Sense-Categorize-│
│ Respond │ Respond │
│ │ │
│ "Novel practice" │ "Best practice" │
└───────────────────┴───────────────────┘
DISORDER (center)
| Domain | Characteristics | Approach |
|---|---|---|
| Clear | Obvious cause-effect | Follow best practices |
| Complicated | Cause-effect requires analysis | Engage experts, analyze |
| Complex | Cause-effect only clear in hindsight | Experiment, probe, learn |
| Chaotic | No clear cause-effect | Act first, stabilize, then assess |
| Disorder | Don't know which domain you're in | Break problem into parts |
Origin: Jeff Bezos
Process:
- Project yourself to age 80
- Look back at the decision point
- Ask: "Which choice would I regret NOT taking?"
- Minimize lifetime regret
Bezos's story: Used this framework to decide whether to leave his Wall Street job to start Amazon. At 80, would he regret not trying? The answer was clear.
When to use: Major life decisions, career pivots, entrepreneurial leaps, one-way door decisions.
Process:
- List all problems or options
- Score each by impact/value
- Sort descending
- Identify the top 20% that account for 80% of the impact
- Focus resources on those vital few
Template:
| Item | Impact Score | Cumulative % | Category |
|------|-------------|--------------|----------|
| A | 45 | 45% | Vital Few |
| B | 25 | 70% | Vital Few |
| C | 15 | 85% | Vital Few |
| D | 8 | 93% | Useful Many |
| E | 7 | 100% | Useful Many |
Process:
- List options as rows
- List criteria as columns
- Assign weights to criteria (must sum to 100%)
- Score each option against each criterion (1-10)
- Multiply scores by weights, sum for total
Template:
| Option | Cost (30%) | Quality (40%) | Speed (20%) | Risk (10%) | Total |
|--------|-----------|---------------|-------------|------------|-------|
| A | 8 (2.4) | 7 (2.8) | 5 (1.0) | 6 (0.6) | 6.8 |
| B | 5 (1.5) | 9 (3.6) | 3 (0.6) | 8 (0.8) | 6.5 |
| C | 9 (2.7) | 5 (2.0) | 8 (1.6) | 4 (0.4) | 6.7 |
Origin: W. Edwards Deming
Plan → Do → Check → Act → (repeat)
| Phase | Action |
|---|---|
| Plan | Identify problem, analyze root cause, develop hypothesis |
| Do | Implement on small scale, collect data |
| Check | Analyze results against expectations |
| Act | Standardize if successful, or adjust and repeat |
When to use: Continuous improvement, process optimization, quality management.
Helps leaders decide how much team involvement a decision requires:
| Style | Description | When to Use |
|---|---|---|
| Autocratic I | Decide alone with available info | Clear answer exists, time pressure |
| Autocratic II | Gather info from team, decide alone | Need data but not buy-in |
| Consultative I | Consult individuals, decide alone | Need diverse perspectives |
| Consultative II | Consult group, decide alone | Need group dynamics/ideas |
| Group | Facilitate group consensus | Need buy-in, no clear answer |
Four phases:
- Situation Appraisal — Identify and prioritize concerns
- Problem Analysis — Find root cause using IS/IS NOT comparisons
- Decision Analysis — Evaluate alternatives against must-have and want criteria
- Potential Problem Analysis — Identify risks and create contingency plans
Principle: Speed of iteration beats quality of iteration.
- It's better to make many small decisions quickly and correct course than to agonize over one perfect decision
- Ship an MVP, gather feedback, iterate
- The cost of delay often exceeds the cost of imperfection
When to use: Product development, agile environments, competitive markets.
Origin: Jeff Bezos (Type 1 vs Type 2 Doors)
| Type | Characteristics | Approach |
|---|---|---|
| Type 1 (One-way door) | Irreversible, high-stakes | Deliberate, analyze thoroughly |
| Type 2 (Two-way door) | Reversible, recoverable | Decide fast, iterate |
Key insight: Most decisions are Type 2 but get treated as Type 1, causing unnecessary slowness. Reserve careful deliberation for truly irreversible choices.
| Situation | Recommended Framework |
|---|---|
| Time-sensitive, competitive | OODA Loop |
| Task prioritization | Eisenhower Matrix |
| Strategic, long-term impact | Second-Order Thinking |
| Risk assessment | Inversion + Pre-Mortem |
| Emotionally charged | 10/10/10 Rule |
| Comparing multiple options | Decision Matrix |
| Group decision | Six Thinking Hats |
| Uncertain complexity level | Cynefin Framework |
| Life-changing decision | Regret Minimization |
| Process improvement | PDCA Cycle |
- Books: Thinking, Fast and Slow (Kahneman), Decisive (Heath), The Great Mental Models (Parrish)
- Practice: For more real-world decision scenarios and actionable principles, check out KeepRule — a platform that maps frameworks to everyday decisions.
Contributions are welcome! If you have a framework to add or improvements to suggest:
- Fork this repository
- Create a feature branch
- Add your framework following the existing format
- Submit a pull request
This project is licensed under the MIT License — see the LICENSE file for details.