“What makes a decision great is not that it has a great outcome. A great decision is the result of a good process.”
Annie Duke, Thinking in Bets: Making Smarter Decisions When You Don’t Have All the Facts (2018) (Source)
🏆🎲🔍
A bad decision can be rewarded. A good decision can fail.
Annie Duke learned to separate decisions from results in a setting designed to confuse them. During her career as a professional poker player, she could make a sound choice based on the probabilities and information available, then still lose the hand. She could also play recklessly and be rescued by the next card. Poker made visible what ordinary life often conceals: an outcome reflects the decision, but also uncertainty, hidden information, other people, and luck.
Duke uses the poker term “resulting” for the habit of judging a decision by how it turned out. Her point is not that outcomes are irrelevant. Outcomes matter enormously. The problem begins when one result becomes the entire explanation. If we want success to teach us anything reliable, we have to ask a harder question than “Did it work?” We have to ask what, exactly, the result allows us to conclude.
The Shortcut That Looked Like Skill
A team is behind schedule. To preserve the launch date, testing is reduced, two warnings are set aside, and several people work through the weekend. The project launches on time and nothing visibly breaks. The compressed schedule enters the success story as proof of decisive leadership. The strain that made it possible disappears from the account.
From the outside, the lesson appears obvious: the shortcut worked.
But what did the outcome actually prove? It proved that the project arrived on time and avoided an immediately visible failure. It did not prove that the omitted testing was unnecessary, the workload was sustainable, or the same gamble would survive a second attempt. A risk that did not materialize has not ceased to be a risk. It has merely passed through one trial without becoming visible.
This is why success can be a more dangerous teacher than failure. Failure interrupts the story. It forces attention toward the broken assumption, the missed signal, or the method that could not bear reality. Success can close the inquiry before it begins. It rewards us emotionally and socially, then offers a flattering explanation: we succeeded because we were talented, brave, disciplined, intuitive, or right.
Sometimes that explanation is partly true. Effort, preparation, skill, and courage can all matter. The distortion lies in turning one contribution into the complete cause. Most meaningful outcomes emerge from several forces at once: judgment, labor, timing, access, assistance, prior advantage, the actions of other people, and events no one controlled. Wisdom does not require us to deny our contribution. It asks us to stop claiming more explanatory territory than the evidence supports.
A single favorable outcome is especially weak evidence. If someone drives too fast and arrives safely, the arrival does not establish that the speed was prudent. If an exhausted person pushes through one more week and meets the deadline, the accomplishment does not prove exhaustion is an effective operating system.
The first task after success, then, is not celebration or criticism. It is separation. Name the result. Then name the method. Do not let the glow of the first become proof of the second.
What the Success Story Leaves Out
Culture rarely presents success as a crowded event. It prefers a protagonist. The founder saw what others could not. The athlete wanted it more. The leader trusted instinct. The family prospered because it made better choices. These stories are memorable because they compress complexity into character. They are also incomplete.
The people most available to explain success are the people whose methods ended in visible success. Those who used similar methods and failed may have disappeared from the sample. Their companies closed, their projects were cancelled, their bodies could not sustain the pace, or their stories were never invited onto the stage. When we study only survivors, a risky practice can look like a proven formula because the evidence against it is no longer standing where we can see it.
Success stories also edit out infrastructure. A person may have worked exceptionally hard while also benefiting from stable housing, inherited knowledge, forgiving institutions, financial reserves, good health, unpaid care, strong networks, or a fortunate opening in the market. Naming those conditions does not insult the work. It makes the account more accurate. Effort and advantage can coexist. Skill and luck can cooperate. A mature explanation does not have to choose only one.
There is another omission that matters even more. Sometimes the cost of success is not absent. It has simply been moved to someone else. The project met its target, but the team lost weekends. The organization grew, but the environmental damage remained outside its accounting. The household functioned, but one person quietly carried the planning, worry, and repair. The leader looked calm because other people were not permitted to show strain.
An outcome can therefore be successful inside a narrow frame and damaging inside a wider one. “We achieved the goal” is not the same claim as “we achieved it responsibly.” Designed Systems and Leverage asks us to inspect the rules, incentives, and feedback loops that decide what gets counted. If a system rewards speed but does not measure preventable rework, speed will look wiser than it is. If it rewards revenue but ignores depletion, extraction can masquerade as performance. If it celebrates the visible individual while hiding collective support, recognition will drift away from causation.
This does not mean every achievement needs to be dismantled until no one may feel proud. Celebration and examination can coexist. Gratitude becomes more credible when it can name assistance. Confidence becomes more useful when it can name uncertainty. Pride becomes less fragile when it does not depend on pretending that one person controlled the whole field.
The better success story is not smaller. It is more populated. It includes the people, conditions, costs, near misses, and alternative outcomes that made the visible result possible.
Judge the Method, Not Just the Result
To learn responsibly from success, return to the moment before the outcome was known. What information was available? Which risks were recognized? Which warnings were dismissed? What alternatives were considered? Who participated in the decision, and who would have carried the harm if the gamble failed? A process should be judged first by what could reasonably have been known and done at the time, not by the relief that arrived afterward.
This protects us from two opposite errors. A good decision can produce a bad outcome because uncertainty is real. A bad decision can produce a good outcome for the same reason. Separating process from result allows accountability without pretending that anyone controls the future. It also prevents a fortunate escape from becoming a repeatable method.
Repeatability requires more than asking whether the same action could work again. Ask whether it would remain responsible under less favorable conditions. Would the method survive without heroic overtime, unusual access, a forgiving customer, an unnoticed defect, or one person absorbing the burden? What happens when the next attempt meets ordinary friction? A process that depends on favorable weather should not be taught as if it built the shelter.
The most useful review holds four forms of evidence together. The result tells you what happened. The method tells you what you chose. The conditions tell you what assisted or constrained the choice. The costs tell you what the result required from you and from others. Only then can you decide what deserves repetition.
This is also where success becomes a question of transmission. Every celebrated result teaches beyond the people who produced it. Rewards turn actions into signals. Promotions turn behavior into precedent. Founder stories become management advice. Family stories become expectations for the next generation. When we praise the outcome without examining the method, we may transmit the luckiest part of the story as though it were wisdom.
A responsible lesson sounds less impressive but travels better. This worked under these conditions. This part reflected skill; another part depended on help or timing. The cost was higher than we first admitted, and the risk did not materialize. Here is what we would change before trying again.
Success deserves celebration. It does not deserve immunity from inquiry. The goal is not to explain achievement away. It is to keep a favorable result from granting authority to an unsound method. Once we learn to examine how success becomes credibility, another question appears: whose favorable outcomes are treated as proof of wisdom, and whose expertise must keep proving itself?
🏆🎲🔍
Practice: Complete a Success Reality Check
Choose one success that still influences how you make decisions. It can be personal, relational, creative, financial, or professional. Select something specific enough to examine without exposing another person’s private information. Then work through six fields:
Result: What happened? Describe the favorable outcome without interpreting it.
Method: What choices, habits, and actions contributed to the result?
Luck and conditions: What timing, access, support, advantage, or uncertainty also shaped what happened?
Cost: What did the result require from you, other people, or the surrounding system? Which costs were delayed or hidden?
Repeat: Which parts of the method would remain responsible under different or less favorable conditions?
Change: What would you preserve, stop, strengthen, or redesign before attempting something similar again?
Finish with one sentence: “This success taught me less about ______ than I first believed, and more about ______ than I initially noticed.”
The purpose is not to drain satisfaction from the achievement. It is to recover the information that celebration alone cannot provide. If the success involved unsafe conditions, exploitation, significant financial exposure, or health concerns, reflection is not a substitute for appropriate professional guidance or structural change.
Scientific Context and Summary
Outcome bias appears when a result changes how we judge the decision that produced it. A choice can look wise after success and foolish after failure, even when the information and reasoning available beforehand were identical. In a foundational series of experiments, Jonathan Baron and John Hershey found that people rated the same decision processes differently after learning whether the outcomes were favorable or unfavorable. A later preregistered study by Aiyer and colleagues replicated the central finding. It also examined how perceptions of responsibility and social norms may shape these judgments.
Field research suggests that the distortion is not limited to hypothetical decisions. Lars Lefgren, Brennan Platt, and Joseph Price studied strategy changes by professional basketball coaches. Coaches were more likely to revise their strategy after narrow losses than after narrow wins, even though those close results revealed little about the strategy’s underlying quality. The outcome influenced whether the prior choice was repeated.
Survivorship bias creates a related problem in organizations and cultural stories. Jerker Denrell showed that observers learn from a distorted sample when failures disappear and only surviving organizations remain visible. Risky or unreliable practices can then appear superior among the survivors even when they do not produce better results across the full population. Copying the habits of winners may therefore produce confident management folklore rather than dependable knowledge.
Attribution adds a personal layer. A meta-analysis by Amy Mezulis and colleagues found a widespread tendency to explain positive events in more self-favoring ways than negative ones. The size and form of that pattern varied across age, culture, and psychological context. Annie Duke’s account of “resulting” translates the problem into practical language: we can credit skill when we win, invoke luck when we lose, and miss useful evidence in both directions.
Repeated successful outcomes can also change how risk is interpreted. Diane Vaughan’s study of the Challenger launch decision described how anomalies within a complex organization could gradually become treated as acceptable when they recurred without catastrophe. This is not evidence that every shortcut leads toward disaster, nor should the history be casually mapped onto ordinary mistakes. It demonstrates a narrower structural danger: the absence of a bad outcome can become evidence that a departure from safer practice is normal.
These findings describe tendencies, not diagnoses, and none offers a perfect formula for separating skill from luck in a single event. Outcomes remain essential evidence. Repeated results, comparison groups, documented decision criteria, near-miss reporting, and attention to hidden costs can make that evidence more informative. The most defensible lesson is not to ignore success, but to widen the inquiry around it. Evaluate what happened, what was chosen, what else contributed, who carried the cost, and what the method would predict under changed conditions.
Wisdom begins when a favorable result becomes a question rather than a verdict.
References
Aiyer, S., Kam, H. C., Ng, K. Y., Young, N. A., Shi, J., & Feldman, G. (2023). Outcomes affect evaluations of decision quality: Replication and extensions of Baron and Hershey’s (1988) outcome bias experiment 1. International Review of Social Psychology, 36(1), Article 12. https://doi.org/10.5334/irsp.751
Baron, J., & Hershey, J. C. (1988). Outcome bias in decision evaluation. Journal of Personality and Social Psychology, 54(4), 569–579. https://doi.org/10.1037/0022-3514.54.4.569
Denrell, J. (2003). Vicarious learning, undersampling of failure, and the myths of management. Organization Science, 14(3), 227–243. https://doi.org/10.1287/orsc.14.2.227.15164
Duke, A. (2018). Thinking in bets: Making smarter decisions when you don’t have all the facts. Portfolio. Author’s book page
Lefgren, L., Platt, B., & Price, J. (2015). Sticking with what (barely) worked: A test of outcome bias. Management Science, 61(5), 1121–1136. https://doi.org/10.1287/mnsc.2014.1966
Mezulis, A. H., Abramson, L. Y., Hyde, J. S., & Hankin, B. L. (2004). Is there a universal positivity bias in attributions? A meta-analytic review of individual, developmental, and cultural differences in the self-serving attributional bias. Psychological Bulletin, 130(5), 711–747. https://doi.org/10.1037/0033-2909.130.5.711
Vaughan, D. (2016). The Challenger launch decision: Risky technology, culture, and deviance at NASA (Enlarged ed.). University of Chicago Press. (Original work published 1996). Publisher’s book page
Legal Disclaimer: The content published on Lucivara is provided for informational, educational, and reflective purposes only and is not intended to constitute medical, psychological, legal, or professional advice. Lucivara does not diagnose conditions, prescribe treatments, or provide therapeutic or professional services. Readers are encouraged to consult qualified professionals regarding any personal, medical, psychological, or legal concerns. Use of this content is at the reader’s own discretion and risk. Copyright Notice: © 2026 Lucivara. All rights reserved. This content is protected by copyright laws and is intended for individual, personal, and non-commercial use only. No part of this publication may be reproduced, distributed, transmitted, displayed, published, or broadcast in any form or by any means without prior written permission from Lucivara. Acceptable Use: The content published on Lucivara is intended for individual, personal, and non-commercial use only. Readers may access, read, and engage with the content for their own reflective, educational, or informational purposes. Except for such ordinary human use, no portion of this content may be copied, reproduced, redistributed, republished, transmitted, stored, scraped, extracted, indexed, modified, translated, summarized, adapted, or incorporated into derivative works without prior written permission from Lucivara. This restriction expressly includes, without limitation, the use of Lucivara content for training, fine-tuning, prompting, testing, benchmarking, or operating artificial intelligence systems, machine learning models, automated agents, bots, or any other computational or data-driven systems, whether commercial or non-commercial. By accessing or using this site, readers acknowledge and agree to Lucivara’s Terms and Conditions.
