What Leaders and Managers Can Learn from Thinking in Bets
Managing people means constantly deciding things with partial information — who to promote, whether to greenlight a project, how to handle a conflict between two team members — and then watching your team judge you entirely on how it turned out. That habit trains everyone, including you, to repeat decisions that got lucky and abandon ones that were actually well-reasoned but hit a bad break. Treating decisions as bets made under uncertainty, rather than verdicts to be graded only in hindsight, makes you a fairer and sharper manager.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Judge the call, not the year-end number
A project that missed its target might still have been the right bet given what your team knew at launch, and a project that hit its number might have gotten there by luck rather than a plan worth repeating.
A manager green-lights a reasonable pilot program based on solid early signals. A key client unrelated to the pilot churns for unrelated reasons, the quarter looks bad, and in the review the manager tells the team the pilot decision was wrong — teaching everyone that caution beats sound, well-supported bets, when actually the pilot's logic had been fine.
When reviewing a project after the fact, write down the decision and the information available at the time before looking at the final result, then evaluate the two separately.
Ask for a number, not a nod
When a direct report says a project "will be done on time," ask them to put a percentage on it. The number surfaces doubts that a confident tone hides, and it gives you something honest to plan around.
A manager asks the team lead if the migration will be ready for the deadline and gets an enthusiastic "yes." Two days before the deadline, it turns out the lead had real doubts the whole time but didn't want to sound negative — doubts that would have shown up immediately if asked to state a percentage instead of a yes or no.
In status updates, ask each owner to give a confidence percentage alongside their timeline, and normalize percentages under 100% as useful information, not as a red flag.
Build in someone whose job is to disagree with you
As a leader, people default to telling you what you want to hear. Deliberately invite a colleague or report who isn't invested in your preferred outcome to argue the other side before you decide.
A manager wants to restructure a team and runs the idea past two people already known to support it. Both agree, the restructuring goes through, and it's only afterward that a quieter team member reveals they'd seen a staffing gap the plan created — a gap that would have surfaced immediately if anyone had been asked to argue against the plan.
Before finalizing a decision that affects the team, name one person specifically and ask them to make the strongest case against your plan, in a private conversation where disagreeing costs them nothing.
Walk through how each option could unfold before you choose
Before committing to a reorg, a hire, or a new process, spend ten minutes imagining several different ways it could play out — smoothly, painfully, or somewhere in between — so you've already thought through your response instead of reacting in the moment.
Asking for confidence percentages can feel like it slows a team down when a decision needs to move fast, and seeking disagreement can feel like second-guessing a plan you need people to commit to — the balance is to timebox the pushback, then commit fully once it's heard.
Name one thing, honestly
Think of a team decision you've praised as "a great call" — was it a good decision, or just a decision that happened to work out?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before finalizing a decision that affects the team, name one person specifically and ask them to make the strongest case against your plan, in a private conversation where disagreeing costs them nothing.