How to Think in Probabilities (Without Being Insufferable)

A poker pro's framework for making better decisions. Outcome quality isn't decision quality. Ranges beat point estimates. Skip the base rate and you're broken.

How to Think in Probabilities (Without Being Insufferable)

In the 2003 World Series of Poker, the eventual winner was an amateur accountant named Chris Moneymaker, who had qualified through a $40 online satellite.

He won by making decisions that often looked wrong but were almost always right.

That distinction — looking wrong while being right — is the entire game of probabilistic thinking. And once you see it, you can't unsee it.

Outcome quality is not decision quality

You make a decision with 70% odds. The other 30% comes in. Were you wrong?

No. You were unlucky.

The poker player Annie Duke coined a term for the mistake everyone else makes here: "resulting." It's the habit of judging the quality of a decision by the quality of its outcome.

Resulting feels intuitive because most decisions in life resolve in one shot. We get one outcome and we treat it as proof. But a single outcome is almost no evidence about decision quality — especially when the decision was probabilistic to begin with.

Drop the point estimate. Use a range.

The fastest upgrade you can make to your thinking is to stop giving point estimates.

"What will the S&P do this year?" Wrong question. Better question: "What's the 90% range?"

If you say "the S&P will be at 6,200 by year-end," you have given a number that is almost certainly going to be wrong. If you say "I think there's a 90% chance the S&P closes between 5,400 and 6,600," you've said something useful, falsifiable, and honest about your uncertainty.

Ranges force you to confront how much you don't know. Point estimates hide it.

Always start with the base rate

"Will this startup succeed?" Don't reason from the founder, the product, the market. Start with the base rate.

Roughly 75% of venture-backed startups fail. So the prior probability that this one fails is ~75%. From there, you can adjust based on what's different about this specific startup. Strong team? Move to 65%. Already at $1M ARR? Move to 50%.

The classic mistake is to skip the base rate and start with the specifics. You read a great founder profile, get excited, and assume 80% success probability. The base rate says you're 25 points too optimistic before you've even done analysis.

Base rates are boring. They are also where almost all the signal lives.

Calibration is a learnable skill

A well-calibrated forecaster, when they say "70% confident," is right 70% of the time. When they say "90%," they're right 90% of the time.

Most people are badly calibrated. They say "90% confident" and they're right about 65% of the time. The gap between expressed confidence and actual accuracy is overconfidence, and it costs you money in markets and friendships in life.

You can fix this. Make 20 forecasts with explicit probabilities. Wait until they resolve. Check your accuracy at each probability bucket. You'll discover you're overconfident in one direction. Adjust. Make 20 more.

This is exactly what Tetlock's superforecasters did. It's the cheapest, highest-impact mental upgrade in the entire decision-making literature.

The Bayesian update, without the math

When new information arrives, update your forecast in the direction the information points. But not too far.

The hardest part is the second half. Most people either ignore new information ("the model said X, I'm sticking with X") or overreact to it ("one bad jobs print, recession is inevitable!").

The discipline is to ask: how much does this information actually change the base rate? A surprise inflation number that's 0.3% above forecast might shift your "Fed cuts in September" odds from 60% to 50%. It does not justify going from 60% to 10%.

Small updates, frequent updates. That's the rhythm.

The danger of crisp answers

Confident, specific predictions feel impressive. They are also almost always wrong.

When a guru tells you "Bitcoin will hit $150,000 by Q3," they have given you a number that gives them no escape route. If Bitcoin hits $148,000, they were "essentially right." If it hits $90,000, they go quiet and recycle a different prediction next quarter.

Probabilistic thinkers don't do this. They say "I think there's a 35% chance Bitcoin closes above $150,000 by year-end, a 40% chance between $80,000 and $150,000, and a 25% chance below." That's not weakness. It's honesty wearing a different costume.

What this looks like in practice

Reading the news: notice every "X will happen" claim and silently translate it to "this person assigns more than 50% probability to X." Then ask yourself if that probability seems right.

Making decisions: before you commit, write down what you think the probability of success is. After the outcome, check whether you were calibrated, not whether you were "right."

Talking to other people: replace "I think" with "I'm 70% sure." It will make you sound weird at first. It will also make you much, much better at being right.

What Juno lets you do with this

Prediction markets are calibration training in disguise. You back your probability with money. You see if you're right or wrong. The price moves in real time, forcing you to confront how the crowd disagrees with you.

After a few hundred trades, your sense of "70% confident" actually means 70%. That's a skill almost no one in finance has, and it's free to learn — you just need a market.

The Moneymaker lesson

Chris Moneymaker won the 2003 WSOP because he could make calls that looked terrible 30% of the time. Each of those losses was unlucky, not wrong. Each of those wins was earned, not lucky.

His opponents thought he was reckless. He was actually just calibrated.

That's the trick. Look reckless. Be calibrated. Win the long game.