DEV Community

王凯
王凯

Posted on

The 10-10-10 Rule for Quick Decision Making

The 10-10-10 Rule for Quick Decision Making

It was 11pm on a Tuesday. My manager had just asked me to present at a company-wide meeting the next morning. A senior engineer had dropped out, and I was the backup. My stomach churned. I wanted to say no.

Then I ran the 10-10-10:

  • 10 minutes from now: I'll feel anxious, unprepared, and stressed.
  • 10 months from now: I'll either regret missing the opportunity or be glad I pushed through the discomfort.
  • 10 years from now: It won't matter at all -- unless it opened a door I wouldn't have found otherwise.

I said yes. The presentation was mediocre. But the VP who attended introduced me to a team working on a problem I was passionate about. Six months later, I transferred to that team. It changed my career trajectory.

The 10-10-10 rule didn't tell me what to decide. It helped me see past the immediate emotional noise.

The Framework

The 10-10-10 rule, popularized by Suzy Welch, is brutally simple:

For any decision, ask yourself:

  1. How will I feel about this in 10 minutes?
  2. How will I feel about this in 10 months?
  3. How will I feel about this in 10 years?

That's it. Three questions. The power comes from forcing you to zoom out from the immediate emotional state that dominates most decisions.

Why It Works

Neuroscience has a term for why decisions feel so hard in the moment: the "affect heuristic." Your brain prioritizes immediate emotional signals -- anxiety, excitement, fear, comfort -- over rational long-term analysis. These signals are useful for survival but terrible for career decisions, technical trade-offs, and life choices.

The 10-10-10 creates temporal distance. By explicitly considering three time horizons, you break the grip of the immediate emotional response and engage your prefrontal cortex -- the part of your brain responsible for long-term planning.

It's like the difference between looking at a painting from six inches away (all you see is brushstrokes) versus stepping back ten feet (you see the whole picture).

Application 1: Career Decisions

"Should I leave my comfortable job for a riskier startup role?"

  • 10 minutes: Excited and terrified. The uncertainty feels overwhelming.
  • 10 months: If it works, I'll have grown enormously. If it doesn't, I'll have learned what startup life is actually like and I'll find another job.
  • 10 years: I'll either be glad I took the risk, or I'll regret spending my thirties in a comfortable but unchallenging role.

The 10-year view almost always favors action over comfort. Regrets of inaction compound in ways that regrets of action rarely do.

Application 2: Technical Decisions

"Should we rewrite this legacy service or keep patching it?"

  • 10 minutes: The team wants the rewrite because the legacy code is painful. The instinct is to say yes to make everyone happy.
  • 10 months: If we rewrite, we'll spend months not shipping features. Customers won't notice any improvement. If we patch, we keep shipping but the tech debt grows.
  • 10 years: The legacy service won't exist in either scenario. The question is whether the rewrite accelerates or delays the product goals that matter at the 10-year scale.

This reframe often kills rewrite projects -- not because rewrites are always wrong, but because the 10-month pain of delayed features usually outweighs the 10-month satisfaction of clean code. And at the 10-year scale, neither option matters because the system will have been replaced regardless.

Application 3: Interpersonal Decisions

"Should I give this engineer blunt feedback about their code quality?"

  • 10 minutes: Uncomfortable. They might get defensive. I might come across as harsh.
  • 10 months: If I give the feedback, they'll have had months to improve. If I don't, the quality issues will compound and I'll eventually have to have a much harder conversation.
  • 10 years: The version where I gave honest feedback early is clearly better. Either they improved (good outcome) or they didn't and we addressed it sooner (also better than delayed).

Difficult conversations almost always look better through the 10-month and 10-year lens. The 10-minute discomfort is temporary. The consequences of avoidance are not.

The Pattern

After running 10-10-10 on dozens of decisions, a pattern emerged:

Decisions that feel uncomfortable now but beneficial long-term: Do them. The 10-minute discomfort fades fast.

Decisions that feel great now but questionable long-term: Be cautious. Immediate gratification is a poor guide.

Decisions that look the same across all three horizons: Decide quickly -- it genuinely doesn't matter much.

Decisions where the 10-month and 10-year answers diverge: These are the truly hard ones. They require deeper analysis beyond the 10-10-10 framework.

Combining with Other Frameworks

The 10-10-10 works well as a first-pass filter. It surfaces whether time horizon matters for this decision. For the decisions where it does matter, I'll often go deeper with scenario analysis or a more structured decision-making approach.

For a collection of scenario-based frameworks that complement the 10-10-10 well, I've found the scenarios section on KeepRule useful. It provides structured approaches for the deeper analysis that some decisions require after the 10-10-10 reveals complexity.

Limitations

The 10-10-10 has blind spots:

It assumes you can predict your future feelings. You can't, precisely. But rough directional estimates ("I'll probably regret not trying" vs. "I'll be relieved I avoided the risk") are good enough.

It doesn't account for probability. "How will you feel" doesn't weight by likelihood. For decisions with asymmetric probabilities (small chance of huge upside vs. likely modest downside), you need expected value calculations, not feeling estimates.

It biases toward action. The 10-year view tends to favor bold moves because most actions look brave in retrospect. This isn't always right -- some caution is genuinely warranted.

The Speed Advantage

The biggest practical benefit of 10-10-10 is speed. It takes thirty seconds to run. No spreadsheets, no frameworks, no meetings. Just three questions in your head.

For the 80% of decisions where the three time horizons agree, you've just saved yourself hours of deliberation. For the 20% where they diverge, you know you need to invest more analytical energy.

Either way, you're making progress instead of spinning in indecision.

Try it on the next decision that has you stuck. Ten minutes, ten months, ten years. The answer is usually clearer than you think.

Top comments (0)