Decision-Making Frameworks I Actually Use

I used to think good leaders made good decisions through intuition and experience. And sure, those help. But the best leaders I've worked with all had one thing in common: they had systems for making decisions, not just opinions.

Here are the frameworks that have survived years of real-world use for me.

1. The Reversibility Test (Type 1 vs Type 2)

This comes from Jeff Bezos, and it's the single most useful mental model I've encountered:

  • Type 1 decisions (one-way doors): Irreversible or very costly to reverse. These deserve careful analysis, broad input, and deliberation.
  • Type 2 decisions (two-way doors): Easily reversible. These should be made quickly by individuals or small groups.

The mistake most organizations make: treating every decision like a Type 1. This creates slowness, bureaucracy, and a culture of risk-aversion.

My Rule of Thumb

Before any decision, I ask: "What happens if we get this wrong?"

  • If the answer is "we can roll it back in a day" → decide fast, execute, iterate
  • If the answer is "we're stuck with this for years" → slow down, gather data, consult

Examples:

Decision Type Approach
Choosing a database technology Type 1 Careful evaluation, POC, team input
A/B testing a new onboarding flow Type 2 Just ship it, measure, adjust
Hiring a key team member Type 1 Structured interviews, references, trial
Trying a new project management tool Type 2 Use it for 2 weeks, see what happens
Signing a 3-year vendor contract Type 1 Legal review, negotiation, alternatives

2. RACI (But Simplified)

The classic RACI matrix:

  • Responsible — does the work
  • Accountable — makes the final call (always ONE person)
  • Consulted — provides input before the decision
  • Informed — told after the decision

Most teams over-complicate RACI into a massive spreadsheet. Here's how I actually use it:

For any important decision, answer three questions:

  1. Who makes the final call? (A)
  2. Who must be consulted before the call? (C)
  3. Who needs to know after? (I)

That's it. Write it down. Make it visible. Move on.

The Golden Rule

If you can't identify the single person accountable for a decision, that decision will either never get made or will be made badly.

I've seen this pattern dozens of times: a decision lingers for weeks because "the team" is responsible. No one wants to be the one to make the call. So nothing happens.

3. The 10/10/10 Framework

When I'm stuck on a decision, I ask:

  • How will I feel about this decision in 10 minutes?
  • How will I feel about it in 10 months?
  • How will I feel about it in 10 years?

This is surprisingly effective at cutting through short-term anxiety. Most decisions that feel scary in the moment are completely irrelevant in 10 years. And some decisions that feel fine right now will haunt you for a decade.

Example: Should I have a difficult conversation with an underperforming team member?

  • 10 minutes: Uncomfortable, anxious
  • 10 months: Glad I did it — they either improved or we parted ways cleanly
  • 10 years: Won't even remember the conversation

Decision: Have the conversation.

4. Pre-mortem Analysis

Instead of asking "what could go right?", ask "It's 6 months from now and this failed. Why?"

This is a pre-mortem, and it's one of the most underused tools in decision-making. Here's the process:

  1. State the decision or plan
  2. Imagine it's the future and things went wrong
  3. Each person independently writes down reasons for the failure
  4. Share and discuss
  5. Address the most likely and most dangerous failure modes

Why It Works

Our brains are wired for optimism bias. We naturally focus on why things will work. Pre-mortems force you to engage your critical thinking before you're emotionally invested in the outcome.

I do this even for personal decisions. Before starting a new project, I write down:

If this project fails in 6 months, the top 3 reasons would be:
1. ____________________
2. ____________________
3. ____________________

For each: What can I do NOW to prevent this?

5. The Eisenhower Matrix (With a Twist)

The classic urgent/important matrix:

                    URGENT          NOT URGENT
                ┌───────────────┬───────────────┐
   IMPORTANT    │     DO IT     │   SCHEDULE    │
                │    (now)      │   (calendar)  │
                ├───────────────┼───────────────┤
   NOT          │   DELEGATE    │   ELIMINATE   │
   IMPORTANT    │  (or batch)   │   (say no)    │
                └───────────────┴───────────────┘

My twist: I add a fifth category — "Decide if it's important."

Most items that feel urgent aren't actually urgent. And most items that seem important haven't been validated. Before placing something in the matrix, I spend 2 minutes asking:

  • Is this actually urgent, or does it just feel urgent?
  • Is this important to our objectives, or just interesting?
  • What happens if we do nothing?

You'd be surprised how often the answer to that last question is "nothing bad happens."

6. Disagree and Commit

This isn't a framework for making decisions — it's a framework for what happens after a decision is made.

The principle: You can disagree during the discussion, but once a decision is made, everyone commits fully.

This is critical because:

  • Not every decision will have consensus
  • Half-hearted execution is worse than a "wrong" decision fully committed to
  • You can always revisit after gathering data

How I Implement It

After any contested decision:

  1. Acknowledge the disagreement openly: "I know not everyone agrees with this direction."
  2. Explain the reasoning: "Here's why we're going this way..."
  3. Set a review point: "Let's revisit in 4 weeks with data."
  4. Ask for commitment: "Can everyone commit to giving this their best effort?"

Bringing It All Together

Here's my actual decision-making workflow:

  1. Classify the decision — Is it Type 1 or Type 2?
  2. Clarify ownership — Who's the one person accountable?
  3. Gather input — From those who should be consulted
  4. Check your gut — 10/10/10 for emotional clarity
  5. Stress test — Pre-mortem for high-stakes decisions
  6. Decide and commit — Make the call, communicate it, move forward

I don't use every framework for every decision. That would be its own form of paralysis. But having these tools in my mental toolkit means I can match the right process to the right decision.

The best decision is rarely the perfect one. It's the good-enough one, made at the right time, with full commitment behind it.