What Career Professionals Can Learn from Thinking in Bets
Years into a career, you make dozens of judgment calls a month — which project to prioritize, whether to push back on a client, when to raise your hand for a stretch assignment — usually with less information than you'd like and a boss or client who will remember only how it turned out. The trap is letting that outcome-only grading system train your own instincts, so you start repeating decisions that got lucky and quietly abandoning ones that were actually sound but hit a bad break.
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 review cycle
A project you championed that got cancelled for reasons outside your control isn't proof your judgment was bad, and a project that succeeded despite being under-resourced isn't proof it was well-run.
A professional advocates strongly for a new process that has solid logic behind it. Leadership changes priorities mid-year for unrelated reasons and the process gets shelved before it can prove itself. The professional internalizes this as "my judgment was off" and becomes more hesitant to advocate for good ideas going forward.
When you make a significant recommendation at work, note in writing what you knew and why you recommended it. If it doesn't pan out, reread that note before deciding what lesson to take from it.
State your actual confidence, not just your recommendation
Instead of telling your manager "this approach will work," say how confident you are — and get comfortable with sentences like "I'm about 70% confident, and here's what would change my mind."
An employee tells a manager a new client strategy "will definitely" increase renewals. When renewals dip slightly for reasons unrelated to the strategy, the manager loses trust in the employee's judgment broadly, when a more honest estimate up front would have framed the same result as expected variation.
In your next status update or recommendation, replace a flat statement with a confidence percentage and one sentence on what could move that number.
Find someone who will tell you the case against your plan
Colleagues who already agree with your approach are the easiest people to ask and the least useful. Deliberately find someone with a different vantage point — a different department, a more skeptical peer — and ask them to argue the other side.
A professional finalizes a proposal after running it past two colleagues who already liked the idea. A quieter colleague from an adjacent team, never consulted, later mentions a dependency that would have changed the whole timeline had anyone asked before the proposal went out.
Before submitting a significant proposal or plan, send it to one person likely to disagree and explicitly ask them to poke holes in it, not just review it for typos.
Picture how the next quarter could actually unfold
Before committing to a big project or a career move, imagine a few different ways it might play out — smoothly, with obstacles, or somewhere in between — so you walk in with a plan for more than just the best case.
Asking for honest pushback takes time and can slow down a decision your manager wants made quickly, and stating real confidence levels can read as less decisive than a confident-sounding "yes" — the practical move is to get quick targeted input from one trusted person, then commit clearly once you've done it.
Name one thing, honestly
Think of a professional decision you got praised for — was it actually a strong decision, or did it just 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 submitting a significant proposal or plan, send it to one person likely to disagree and explicitly ask them to poke holes in it, not just review it for typos.