How to Build a Personal Decision-Making Framework That Holds Under Pressure

In 2019 I watched a senior executive I respected make a bad decision in about eleven minutes. It was a hiring decision — a Head of Sales for a 40-person software company. The candidate was charismatic, well-connected, coming off a strong run at a larger competitor. The interview was warm, the references checked out in the way references always do, and the offer went out the same afternoon. Six months later the company had lost two of its three best account executives, missed its number by 34%, and was running an expensive exit process on a leader who had looked, on paper, like the perfect hire.

The problem wasn't the candidate. The problem was the process — or rather, the absence of one. The executive in question, like most operators I've watched at close range, made high-stakes decisions using a mix of gut instinct, reference signals and whatever frame happened to be salient that week. It worked most of the time, because he was experienced and smart. When it didn't work, the failures were expensive.

A personal decision-making framework is a defence against your own pattern matching. It forces you to slow down for the decisions that matter, at the cost of a small friction tax on every decision. Built right, it pays for that tax many times over across a career. Here's how to build one.

First, Stratify Your Decisions

Not every decision deserves the same process. Jeff Bezos, in his 1997 shareholder letter, introduced the distinction that most operators eventually adopt: Type 1 decisions are one-way doors — irreversible, high-consequence, need deliberation. Type 2 are two-way doors — reversible, can be undone in a week, should be made fast. Most decisions are Type 2. Most people treat them all as Type 1.

The first move in any framework is stratification. A quick self-test when a decision arrives:

• Can I undo this in 30 days without significant cost? If yes, it's Type 2. Decide in under an hour and move on.
• Will the consequences compound for 12+ months and is the reverse-course cost material? It's Type 1. Give it real process.
• Is this a recurring decision I've made 50+ times? Build a simple rule and stop re-deciding.

Most wasted cognitive cycles in senior roles come from over-processing Type 2 decisions. The executive who agonises for a week over which vendor to use for a CRM migration is the same one who signs a multi-year, multi-million-pound partnership deal in a 40-minute board meeting because it was "on the agenda." The framework flips that.

The Five-Question Template for Type 1 Decisions

For the decisions that actually matter — hires into critical roles, acquisitions, strategic pivots, firing a senior executive, entering or exiting a market — I use a five-question template, written down, before I sleep on it.

1. What's the decision, stated in one sentence?

This sounds trivial and usually isn't. The act of writing the decision in one sentence often surfaces that you don't actually agree with your team on what's being decided. Is it "whether to hire Maria as Head of Sales" or is it "whether the role should exist in this shape at all and Maria is one candidate"? Those are very different decisions. The framework forces you to pick.

2. What's the default if I do nothing?

Most decisions have a default outcome that no one has made explicit. You don't hire anyone — what happens? You don't buy the company — what happens? The default is your counterfactual. A lot of decisions look worse against a well-specified default than they do in isolation. Writing the default down often reveals that the decision is actually the no-decision — keeping current capabilities rather than adding new ones.

3. What's my base rate for decisions like this?

Daniel Kahneman, in Thinking, Fast and Slow (2011), hammers one lesson more than any other: people ignore base rates and pay for it. If 40% of executive hires fail within two years in companies your size — and that's roughly the number from McKinsey's data — your hiring decision has to acknowledge that. "This specific candidate feels strong" is an inside view. The base rate is the outside view. The honest decision weighs both.

The base-rate question is the single most protective element of the framework. It's the thing that stops you building narratives that hide the probability of failure. Write the number down.

4. What would have to be true for this to work?

Borrowed from Roger Martin's Playing to Win (2013) — the "what would have to be true" question inverts the decision. Instead of asking "will this work?" you ask "what conditions need to hold for this to work?" and then assess the likelihood of those conditions.

For the failed sales hire I mentioned: what would have to be true for that hire to work out? The candidate would need to integrate with the existing top two AEs, build trust with the CEO inside 90 days, not disrupt the existing commission structure, and — this is the one nobody checked — actually enjoy selling into mid-market rather than the enterprise segment she'd come from. Listed that way, at least two of the four were clearly unlikely. The decision looks different.

5. How will I know I was wrong, and by when?

This is the decision journal habit, built into the template. Commit, before making the decision, to the specific evidence that would prove you wrong and the timeframe for seeing it. "If Maria hasn't stabilised the AE team by month four and closed at least one new enterprise account by month six, the hire is failing." Now you have a pre-commitment to examine reality honestly in six months, rather than rationalising as you go.

The research on overconfidence, most of it from Philip Tetlock's work on expert forecasters, shows that experts who pre-commit to falsifiable predictions get measurably better over time. The ones who don't, don't.

The Three-Second Emotional Check

Past the template, there's one more layer worth adding. Before you commit, stop and ask yourself: what am I feeling right now, and is it influencing this?

Am I tired? Decisions made after 16:00 on a Friday are reliably worse than the same decision made Tuesday at 10:00. Am I angry at the alternative? Decisions made to "show" someone something are almost always wrong. Am I excited about the upside in a way that's making me discount the downside? Kahneman again — we're loss-averse for losses we can see, but blind to losses from decisions not made.

This isn't about becoming Vulcan. It's about noticing when your emotional state is driving the decision and giving yourself permission to defer for 24 hours when the answer is yes. Almost no Type 1 decision genuinely needs to be made in the next four hours. The ones that do, by their nature, have already failed the framework.

The Two Traps to Avoid

First trap: building a framework so elaborate you stop using it. I've seen executives with 20-page decision protocols that sit in Notion and never get opened because opening them is more expensive than just deciding. The goal is a process tight enough that you actually use it on the five or six major decisions a year that deserve it. Five questions is roughly the ceiling. Anything more is theatre.

Second trap: using the framework to rationalise what you were going to do anyway. You work through the five questions, discover they point against your initial instinct, and then reverse-engineer answers until they point toward it. The discipline here is intellectual honesty — and it's easier said than done. A partial fix: make someone else in your life (a peer, a coach, a spouse who'll push back) read your answers before you commit. It's much harder to lie to yourself when someone is watching.

The Last Thing

Decision frameworks don't guarantee good outcomes. They guarantee good processes. The difference matters because, as Annie Duke has pointed out repeatedly in Thinking in Bets (2018), judging decisions by outcomes in a world full of randomness leads you to reward luck and punish skill. Your framework gets you to a defensible decision given what you knew at the time. If the outcome goes badly anyway — and sometimes it will — you still know you made a good decision. That's what allows you to keep making hard calls without losing your nerve.

The executive I mentioned at the start eventually built a version of this. Two years later, his hire rate on senior roles was measurably higher, and — more importantly — he could explain, before the hire started, exactly what he was betting on. The bets still didn't always work. But the ones that didn't, didn't surprise him.