Luck & Attribution: Honestly Record Luck's Share of Your Success
Topic: Luck & Attribution·4 Principles
"Success = talent + luck. Great success = a little more talent + a lot of luck." — Daniel Kahneman
This week's thesis: The higher you climb, the easier it is to believe "I got here because I'm good." Not entirely wrong — but self-serving bias is factory default: it systematically inflates your contribution and shrinks the share of luck and timing. This week isn't about false modesty; it's about calibration: success = talent + luck, and whether you can tell those two apart directly determines your next decision's quality, your learning speed, and how much others trust you. Four tools: estimate luck's true share, turn the survivorship-bias mirror on yourself, treat humility as a tool not a virtue, and write luck into every postmortem. Honesty first: luck can't be eliminated — all you can do is stop misfiling it as skill.
PRINCIPLE 01
Success = Talent + Luck: Admit Your Attribution Is Biased
Self-Serving Bias — You Over-Claim by Default
Self-Serving BiasKahnemanCalibration
Principle in One Line
"I did it" is almost always "I did it right + luck helped" fused together. The brain defaults to crediting itself for success and blaming the situation for failure — that's self-serving bias. Not a character flaw, a cognitive default. Its biggest harm: it makes you overestimate how repeatable your success is.
In Their Words
"Success = talent + luck. Great success = a little more talent + a lot of luck."— Daniel Kahneman,《Thinking, Fast and Slow》Ch.19
Scene
Situation: A project you led was a big win, and it's your turn to give the wrap-up at the retro.
✗ Writing luck into the playbook
"This was a win of execution and architecture. The methodology is repeatable — copy it onto the next project." But half the truth is: a competitor imploded that quarter, a key client's budget happened to land, a core engineer happened not to get poached. The next project, without those tailwinds, crashes.
✓ Split two columns before codifying
"We won. First, two columns: what we genuinely did right (codify it), and what was luck — the competitor's mess, the budget window, no attrition. The latter may not recur; keep it out of the playbook. Only the repeatable column is our real capability."
Checklist: Separate Skill From Luck
Was there a factor in this outcome I couldn't control and didn't predict?
Same decision, different timing / market / boss — would it still have won?
When I credit myself, is the subject "I" or "we + timing"?
When I fail, do I flip and blame the environment? Use one consistent standard for both.
If a rival ran the retro on my win, which luck factor would they stress that I left out?
Common Mistakes
Skill when you win, luck when you lose. The team sees this double standard instantly, and your retros lose credibility.
Mixing one-off luck with repeatable skill in one narrative. The org codifies a flawed methodology and walks into the same trap.
Back-inferring decision quality from the result. "We won, so the call was right" — the most expensive misjudgment. See Card 4.
Key References
Elliot Aronson,《The Social Animal》— self-serving bias and the fundamental attribution error. Robert Frank,《Success and Luck》— evidence that luck is systematically underweighted in meritocratic narratives.
PRINCIPLE 02
Turn Survivorship Bias on Yourself
Turn Survivorship Bias on Yourself
Survivorship BiasWaldTaleb
Principle in One Line
Every "success story" you hear comes from someone who survived. The silent failures don't write books, don't give talks, don't sit on your promo panel. The most dangerous survivor isn't someone else — it's you. In parallel universes, many versions of "you" made the same call and lost.
In Their Words
"Mild success can be explainable by skills and labor. Wild success is attributable to variance."— Nassim Taleb,《Fooled by Randomness》
The Classic Case: Wald's Planes
WWII: The military wanted to armor the spots with the densest bullet holes. Statistician Abraham Wald said they had it backwards — they'd only counted the planes that came back. Hits there clearly weren't fatal. Armor the places returning planes had almost no holes (the engines), because the planes hit there never made it home.
Scene
Situation: You read a "10x engineer" growth post, hear a Staff engineer's promo retro, and plan to copy it.
✗ Treat the survivor's path as a recipe
"He did this and got promoted, so I'll do the same." You never saw the hundreds who did the same things and didn't get promoted — and the piece their path was missing is often, precisely, luck.
✓ Actively hunt counter-samples
"Let me talk to a few people who made similar choices but didn't make it — and ask exactly what was missing. If the missing piece was outside their control, that's luck, not a move I can copy."
Checklist: Turn the Mirror Around
The "success case" I'm studying — where's its matching failure sample? Have I looked?
Does this advice only ever come from the mouths of people who already succeeded?
If I did everything right and still lost, which uncontrollable variable would sink me?
When I advise others, am I dressing my luck up as "just work hard"?
Common Mistakes
Treating a survivor's path as a deterministic algorithm. Same moves + no luck = a completely different ending.
Forgetting you're a survivor sample too. A few past wins, then over-betting — variance reverts eventually.
Studying only winners, never dissecting losers. Losers carry higher information density: they tell you where it actually kills you.
PRINCIPLE 03
Humility Is a Tool, Not a Virtue Performance
Humility as Calibration, Not Performance
Practical humility isn't the throwaway "oh, I just got lucky." It's an accurate self-model — knowing where the edge of your competence is. Well-calibrated people decide more steadily, learn faster, earn more trust, and draw less envy. The opposite of humility isn't confidence — it's distortion.
In Their Words
"The real reason... is our inability to distinguish between confidence and competence."— Tomas Chamorro-Premuzic,《Why Do So Many Incompetent Men Become Leaders?》
Scene
Situation: In a review, someone asks "Where's the biggest risk in this plan?"
✗ Inflated confidence
"No real risk, we've thought it through." If it crashes, your credit zeroes out in one shot — and the people in the room who actually know can already tell you're bluffing.
✓ Exposing the edge = calibration
"Three parts I'm confident in, two I'm not — the launch-latency piece I have no experience with, so I want X to look at it with me." Exposing the edge isn't weakness; it lets people believe you when you do say "I'm confident."
✓ Name luck and others specifically when crediting
Not "I drove all of this." Say: "I set the structure, but it shipped because X held the launch together — and we caught a good window."
Checklist: Calibration Self-Check
Can I name a recent judgment I got wrong, and why? (If not = poorly calibrated.)
Asked about risk, do I lead with confidence or with the uncertain parts?
When crediting, do I name luck and specific people, not just a vague "everyone"?
Does my confidence level match my actual past hit rate, or is it always "very sure"?
Common Mistakes + A Note for Women Leaders
Performing humility. "Oh I'm not that good" — false modesty is more grating than arrogance, and it's also a distortion.
Over-humbling into indecision. Calibration isn't refusing to decide; it's deciding with error bars: state your odds, then still make the call.
Female Leader's Note
The "credit luck more, claim less" prescription is written for people who overestimate themselves (often the default-confident type). But research shows women more often attribute success to luck/others and failure to themselves, and observers more readily say a woman's success was "luck or help." If you already underestimate yourself, calibration runs the opposite way: accurately say "this was my competence." Humility = calibration, not self-erasure — claim the credit that is actually yours.
Key References
Tomas Chamorro-Premuzic,《Why Do So Many Incompetent Men Become Leaders?》— the cost of mistaking confidence for competence. Adam Grant,《Think Again》— "confident humility": faith in your ability, openness to being wrong about the current call.
PRINCIPLE 04
Write Luck Into the Postmortem: Separate Decision From Outcome
Write Luck Into the Postmortem — Separate Decision From Outcome
ResultingDecision RetroAnnie Duke
Principle in One Line
The most expensive error is "won, so the call was right; lost, so the call was wrong" — Annie Duke calls it resulting (judging a decision by its outcome). A good outcome can come from a bad decision (luck), a bad outcome from a good decision (bad luck). Postmortems need two axes: decision quality × outcome.
In Their Words
"Resulting: our tendency to equate the quality of a decision with the quality of its outcome."— Annie Duke,《Thinking in Bets》Ch.1
The Decision × Outcome Quadrant
Scene
Situation: A risky tech choice was a big success after launch, and the team wants to "always do it this way."
✗ Good outcome → decision must be right
"It worked! This bet pays off — let's make it the default." You're rewarding a decision that landed in the "dumb luck" quadrant by promoting it into the playbook.
✓ Reward decision quality, not just outcome
"The result is great, but on the information we had this was a high-variance bet. Winning it doesn't make the process right. Next time, same situation — do we still accept this failure probability?" And conversely: when a well-reasoned decision fails on a black swan, don't blame the decider (back to blameless postmortem).
Checklist: Ask the Right Question at the Retro
Am I asking "how did it turn out" or "was the decision reasonable on the information we had then"?
Which quadrant did this land in — earned win or dumb luck?
Did anyone get rewarded for a genuinely bad decision just because the bet paid off?
In a failure retro, did I separately log uncontrollable luck and improvable decisions?
Common Mistakes
Rewarding and punishing purely on outcome. You encourage gambling and punish correct-but-unlucky risks — the team learns "better mediocre-and-right than smart-and-bold."
Blaming all failure on luck (evasion) or all on the decision (over-self-blame). Log the two axes separately to see clearly.
Key References
Annie Duke,《Thinking in Bets》(Ch.1 "Life Is Poker, Not Chess") — resulting and decision journals. Daniel Kahneman,《Thinking, Fast and Slow》(Ch.19 "The Illusion of Understanding") — how hindsight bias distorts retros.
This Week's Exercise · Your Day 30 Action
Do one concrete thing this week — not reflection, not reading:
Pick a recent, clear success of yours and open a two-column doc: left "Skill," right "Luck." Force yourself to write at least 3 items in the Luck column — things you couldn't control and didn't predict (timing, someone else's mistake, a resource window, a key person not leaving).
Then codify only the "Skill" column for your team as repeatable methodology.
Reflection: If you removed one key luck factor from each of your three proudest achievements of the last three years, how many would still stand?
Go Deeper
Does constantly stressing luck kill motivation and slide into fatalism?
No — as long as you separate two things: luck governs the variance of outcomes; effort and decision quality govern where the distribution sits. You can't control one roll of the dice, but you can control how many hands you play and whether each bet is sound — over time, skill still dominates. Acknowledging luck isn't a license to coast; it's a way to put energy where it's truly controllable, while staying gentle with yourself and others on any single result. Fatalism says "it's all luck"; calibration says "I own the luck and I'm accountable for the decision."
In a winner-take-all, outcome-only review system, does talking about luck and decision quality just cost me?
There's a real tension. Reporting up, baldly saying "we got lucky" can read as low confidence or dodging — so externally use a neutral frame like "controllable vs. external factors," casting luck as risk management, not self-deprecation. But your internal, personal retro must be honest, or you'll misfile luck as skill and crash the day the luck runs out. The strategy is layered: do the political translation of attribution externally, and the scientific calibration of attribution internally. The two don't conflict.
Is the skill-to-luck ratio the same across fields?
No — the key variables are variance and feedback cycle length. Low-variance, fast-feedback fields (typing speed, short-cycle engineering delivery) are skill-heavy: practice reliably shows up. High-variance, slow-feedback fields (startups, bet-style tech choices, market timing) are far more luck-loaded; one or two outcomes say almost nothing about ability. To judge how much a field should trust luck, ask "if the same person did this 100 times, how wide is the outcome distribution?" The wider it is, the more you should discount skill in any single result.
As a leader, how do I reward "good decision, bad outcome" without being accused of "excusing failure"?
The key is setting the standard beforehand, not after. At decision time, record: the information known, the options considered, the estimated success probability and failure cost. When the result lands, compare against that record — if the decision was sound on the information at hand, clearly distinguish "right call, bad luck" from a failure that was simply careless. The line for your boss isn't "this failure isn't his fault," but "this was a bet we endorsed in advance, lost to an uncontrollable variable; what we fix is the hedge, not the person who made the call." With a pre-record, that's not excuse-making — it's governance.