Cited from real sources 6 min read Updated August 2026

A decision framework by Annie Duke

Annie Duke's Thinking in Bets: How to Judge a Decision Without Its Outcome

Thinking in Bets is Annie Duke's reframe that every decision is a bet placed under uncertainty, so its quality lives in the process, not the result. Duke, a former professional poker player and now a special partner at First Round Capital, argues that judging a call by how it turned out teaches you almost nothing, because luck and hidden information sit between the choice and the outcome. The fix is to write the bet down before you know.

Why one result proves nothing

"poker is much noisier than you think because when I win a hand I have no idea why"

The hand you won and the hand you played well are two separate facts. Business is noisier than poker, and that gap is where most learning quietly dies.

Annie Duke on Lenny's Podcast This will make you a better decision maker Watch at 47:46

The framework

A good result is not evidence of a good decision

Two things determine how anything turns out: the quality of your decisions and luck. You control exactly one of them. Duke's framework starts by refusing to let the second one grade the first. She calls the error resulting, and it is the habit of reading backward from an outcome to a verdict on the choice that produced it.

It survives because resulting feels like evidence. You shipped, the number moved, so the call was right. But two things sit between the decision and the result that you could not see at the time. One is luck. The other is information that only arrives after you have committed.

Her sharpest illustration is an investor who was early into Uber. Everyone now treats that as proof of judgment. Duke points out that nobody, including the investor, knows which it was: a read on a real pain point in a developing market, or a friend who happened to start the company.

we don't actually know what the decision quality was, right, like all we know is that you had a good result
Duke on the investor who was early into Uber Watch at 53:21

This is not academic. If you cannot separate luck from skill, every fortunate win hardens a process that will eventually fail you, and every unlucky loss talks you out of one that works. Betting language fixes that, because a bet forces you to say how sure you are before the cards turn over.

How to apply it

How do you actually think in bets?

Seven moves, drawn from Duke's framework and from how she rebuilt decision records at a venture fund.

  1. 1

    State the decision as a bet, not a conclusion.

    You are wagering money, headcount, or a quarter on one future out of several. Name what you are risking and what has to be true for it to pay off.

  2. 2

    Express confidence as a percentage.

    Not "I'm sure" but "I'm 72 percent". A number can be moved by new evidence. A certainty can only be defended, which is why people defend it.

  3. 3

    Record the forecast before the result exists.

    A prediction reconstructed after the fact is worthless, because hindsight rewrites it. Write it where someone else can read it back to you.

  4. 4

    Shorten the feedback loop on purpose.

    Duke's position: the loop is as long as you choose it to be. Ask what is correlated with the outcome you care about and track that, instead of waiting years for a verdict.

  5. 5

    Field the outcome before you change anything.

    Place each result somewhere on the luck-to-skill spectrum first. Most sit in the middle. Extracting a lesson from the luck portion is how teams end up with superstitions.

  6. 6

    Run the "wanna bet" test on anything that feels certain.

    If being asked to wager on a belief makes you suddenly less sure, you were holding it at a confidence the evidence never earned.

  7. 7

    Match the effort to the stakes.

    Duke's happiness test: if the outcome will not meaningfully affect you in a week, a month, or a year, decide fast and move on. Reserve the full process for bets that can actually hurt.

What this looks like at a venture fund

Duke has spent five years inside First Round Capital doing exactly this. When she arrived, the partnership recorded the vote and little else: who said yes, who said no. She had them agree on shared definitions of what they were judging, rate components like market and team on a scale of one to seven so the opinions carried spread, and forecast one thing: the probability the company funds at Series A.

Hundreds of companies later, the fund can ask a question it previously could not. Is a given partner better than random at that forecast? The answer goes back to the partner, which is the only mechanism by which calibration improves.

let's make it explicit because you're doing it implicitly anyway
Duke on why the forecast already exists Watch at 58:52

Note what actually changed. Not the judgment. The record of it.

Boundary conditions

When it works, when it fails

Works best when

  • The decision type repeats often enough that a base rate can form
  • You can name a leading signal correlated with the outcome you actually care about
  • The forecast is written down before the result, where someone can check it
  • The room rewards being accurate over sounding confident

Fails when

  • Nobody ever scores the forecasts, so the numbers are theater and calibration never moves
  • The percentage is attached to something genuinely unknowable, which buys false precision
  • The prediction gets reconstructed after the outcome, where hindsight bias rewrites it
  • Being wrong in the room costs status, so people quietly stop making the call explicit

The last one is the real constraint, and it is psychological rather than technical. A long feedback loop is comfortable. If you were early into a company that worked, you are already credited for judgment, and finding out whether you deserve it can only cost you. Tightening the loop means volunteering to be wrong sooner.

it's very very difficult for human beings to deal with feeling wrong in the moment even if it helps them in the long run
Duke on why nobody volunteers for a tighter loop Watch at 54:04

Where operators disagree

Duke's rule is to put a number on your confidence. Douglas Hubbard pushes it further: anything that matters is observable and therefore measurable, and calibrated probability estimation makes even intangibles quantifiable. Nassim Taleb draws the opposite line. We systematically overestimate our ability to predict in complex domains, and a precise-looking model there is more dangerous than admitted ignorance because it manufactures false confidence.

The reconciliation both camps accept: calibrate where outcomes are bounded and repeat often enough to be scored; where they are not, stop forecasting and build for robustness. Duke's own practice sits in the first case. She picked Series A funding to forecast precisely because hundreds of instances exist to score it against.

Thinking in bets is the judging half of Duke's work. The acting half is her kill criteria, which convert the bet into a pre-committed exit condition, so you are not relying on clear judgment at the moment you have none. The decision-making framework guide puts both moves in sequence alongside operators who attack the other failure modes.

The sources

Where Duke discusses this

Useful? Send it to whoever on your team is about to be graded on an outcome they did not control.

Want the full playbook?

Get 457 strategic thinking frameworks.

89 frameworks 125 rules 235 heuristics & principles 11 operators

From Richard Rumelt, Annie Duke, Charlie Munger, and 8 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

Related frameworks