Decision-Making Frameworks

Matching how much deliberation a decision gets to how much it would cost to get wrong.

A decision-making framework is a way of deciding how to decide. The most useful ones do very little clever work and a lot of triage: is this reversible or not, who actually owns it, what would change my mind, and how much deliberation is this worth. That last question is the one most teams skip, and it's where most of the waste is — reversible decisions get committee treatment while irreversible ones get made in a corridor. Frameworks don't produce right answers. They make your reasoning visible enough that someone can disagree with a specific part of it, and they let you tell later whether a bad outcome came from a bad decision or from luck.

Scenarios

You're asked to approve something that could be undone next month at almost no cost. What would you do — give it the same scrutiny as anything else with your name on it, or decide quickly and spend the saved time on the migration nobody has reviewed?

A decision you made last year turned out badly. What would you do — treat it as a mistake to learn from, or first ask whether you'd make the same call again given only what you knew at the time?

Your team has been "gathering more information" on a choice for six weeks. What would you do — keep gathering, or write down what specific piece of information would actually change the answer, and set a date?

Takeaway

Sort by reversibility first. Cheap-to-undo decisions deserve speed, not process.
Write down what would change your mind before you decide. It's the only way to tell later whether you were wrong or just unlucky.
Name the owner. A decision everyone is consulted on and nobody owns gets made by a deadline instead.
Judge past decisions on the reasoning available at the time, out loud, especially when the outcome was bad.
Watch for the framework being tuned to the answer. If the weights moved after you saw the result, you made the decision first.