The decision-making framework operators actually use

The short answer

The framework, in five steps

Run this on any decision that is worth more than ten minutes of thought.

1. 1

   Match the effort to the stakes

   Most decisions are low-stakes and reversible. Annie Duke's test: if the outcome will not affect your happiness in a week, a month, or a year, decide quickly and move on.

2. 2

   Define the problem, not the symptom

   Name what you actually want and the obstacle in the way. Solving the presenting symptom is the most common way a good process produces a useless answer.

3. 3

   Force at least three futures

   Ask compared with what, and then what, and at the expense of what. One option is never a decision.

4. 4

   Set the criteria before you look at the data

   Deciding what would change your mind after you see the numbers is how motivated reasoning gets in.

5. 5

   Write the exit condition

   Name the specific signal that means stop or pivot, and the action attached to it, while you still have no stake in the answer.

The cited playbook

The cited decision moves

Each move is how an operator who makes hard calls for a living actually decides, linked to the source.

1. 1

   Sort the decision by stakes and reversibility first

   Annie Duke's filter is that most agonising decisions are not high-stakes, they only feel that way. If either option would make you happy as your only option, the decision is low-stakes; if the outcome will not meaningfully change your life in a week, a month, or a year, it is a sheep in wolf's clothing. Spending a week on those is how the genuinely irreversible calls end up getting ten minutes.

   Annie Duke · Annie Duke, How to Decide
2. 2

   Define the problem before you explore any solution

   Shane Parrish's five-step process starts by separating what you want from the obstacle in the way, and insists on the root cause rather than the symptom. The step most people skip is the cheapest one: a decision framed around the wrong problem produces a confident answer to a question nobody asked.

   Shane Parrish · Shane Parrish, Clear Thinking
3. 3

   Invert: ask how you would guarantee failure

   Rather than asking how to succeed, ask what would reliably cause this to fail, then eliminate those conditions. Parrish's argument for inversion is practical, not philosophical: failure modes are far easier to name accurately than success factors, so you can raise your odds without knowing exactly what winning requires.

   Shane Parrish · Shane Parrish, Clear Thinking
4. 4

   Set kill criteria before you commit

   Decide in advance what signal means stop or pivot, and attach an action to each one. Annie Duke's point is that once you launch, sunk cost and identity make you far slower to quit than you predict, so the exit condition has to be written while you still have no stake in the answer.

   Annie Duke · Annie Duke on Lenny's Podcast
5. 5

   Judge the decision by the process, not the outcome

   Duke calls the opposite habit resulting: grading a call by how it happened to turn out. A good decision can lose and a reckless one can win, so if you only review outcomes you learn the wrong lesson twice. Separate the quality of the reasoning from the quality of the result, then review the reasoning.

   Annie Duke · Annie Duke, Thinking in Bets

Where experts disagree

Where operators disagree: fix the person, or fix the room?

They are not really opposed, they are different layers. Duke's moves work on a decision you own; Dalio's work on decisions a group owns. The failure mode is running Duke's process alone on a call that needed three dissenting voices, or building Dalio's machinery for a decision one person could have made in ten minutes.

What founders say

What founders actually say

Verbatim user quotes from public forums, sourced, not paraphrased.

FAQ

Decision-making framework questions, answered

Related guides

Keep exploring