Insights · Learn
Decision quality is not decision outcome.
A good decision under uncertainty can still produce a bad outcome, and a bad decision can still produce a good one. Confusing the two is a common failure mode in investment governance.
Decision quality and decision outcome are different measures. Quality asks whether a call was well reasoned given what was known at the time; outcome asks whether it worked. Because investment decisions are probabilistic, a strong decision can still produce a weak result, and a weak one can still get lucky. Evaluating teams by outcome alone rewards luck and punishes discipline. The fix is a record of what the team knew at approval, kept separate from the position's later performance.
Why decision quality and outcome diverge
Investment decisions are probabilistic. A 70% expected case can still land on the 30% outcome, and a 30% expected case can still land on the 70% one. Over hundreds of decisions, the law of large numbers separates skill from luck. Over the relatively small number of decisions a typical investment committee reviews in a year, the gap between decision quality and decision outcome can dominate the signal entirely.
When an IC revisits a position 18 months in, the natural question is 'was this a good deal?' That is a question about outcome. The question that preserves discipline is 'was this a good decision, based on what we knew at the time?' The two questions have different answers, and firms need a different kind of record to answer each one.
Punishing a good decision for a bad outcome trains the next analyst to underwrite to lower confidence. Rewarding a bad decision for a good outcome trains the next analyst to skip the diligence that would have caught it.
A matrix each IC should make explicit
Cross decision quality (good or bad) with decision outcome (good or bad) and four cells emerge. Each one calls for a different institutional response, and each carries a different risk if the committee responds the wrong way.
Preserve the team's mandate to make similar calls.
Risk · Punishing it trains the next analyst to underwrite to lower confidence.
Study what made it well-reasoned; codify the pattern.
Risk · The win breeds over-confidence and the discipline slips.
The lesson is clear — fix the process.
Risk · Learning “not this deal” instead of “not this process.”
Do not let the good outcome ratify the bad process.
Risk · Rewarded sloppiness gets replicated on the next deal.
How to evaluate a decision when the outcome isn't visible yet
Most positions get reviewed mid-cycle, 12 to 30 months in, before the outcome has locked. The temptation is to project the current trajectory and pre-judge the result. The discipline is to evaluate the decision against what was known at approval, not against what is known now.
- Did the team identify the right structural risks at IC, or miss a material category of risk?
- Did the team explicitly test downside scenarios, or rely on a best-case projection?
- Did the team document the decision basis in a way that survives team turnover and outside review?
- Did the team commit to forward indicators that would invalidate the thesis, or only to backward indicators that confirm what already happened?
- Did the team name, in writing at approval, what would change their mind?
These are quality questions a committee can answer mid-cycle without waiting for the outcome. The answers may look unfavorable even on a position that is currently performing well, and may look reasonable even on one that is currently struggling.
Evaluating a decision after outcome lock
Once the outcome is known, the natural pull is to backfit a narrative that makes it look inevitable. Hindsight bias, the tendency to overestimate how predictable an outcome was, is among the most documented biases in the decision literature.
The discipline at post-outcome review is to ignore the outcome on the first pass and judge the decision against the evidence available at the time. Then layer the outcome back in and ask which of the factors that materialized were knowable at decision time, which were not, and which were knowable but left uninvestigated. The third group is where decision-quality lessons live; the second is where luck-versus-skill lessons live.
What top-quartile committees do differently
Bain's Global Private Equity Report and McKinsey's research on private equity both document a discipline gap between top-quartile and bottom-quartile firms. A handful of patterns show up repeatedly in the top-quartile group.
Decisions are typed
Monitor, stabilize, intervene, hold or exit is recorded at IC, not just the approval itself.
Downside is named
What specifically breaks the case, and at what threshold, is explicit and written down, not implicit in a model.
Forward indicators are committed
Not 'we will watch the financials' but a named metric and threshold that would reopen the thesis.
Post-mortems separate quality from outcome
Teams that made good decisions with bad outcomes are protected, not blamed.
Institutional memory survives turnover
The decision basis is written down well enough that it does not leave the firm when the analyst does.
The infrastructure that makes this possible
- Memo sections for the financials, the risks and the terms are assembled from the sourced spread, so the basis for the decision is traceable, not reconstructed from memory.
- Risk signals are graded against the firm's own policy thresholds at approval, so the record shows what the team flagged, not just what it concluded.
- Open conditions stay on the deal record alongside the covenant obligations, so what the committee asked for is not left in an approval email.
- The memo exports as DOCX or XLSX carrying a deterministic evidence fingerprint, so a later reviewer can see what the team knew without rebuilding the file.

A decision-quality record does not need to predict the outcome. It needs to preserve what the team knew, so the committee can tell the difference between a good decision and a good outcome later.
Sources cited
- Annie Duke, Thinking in Bets (Portfolio, 2018). The 'resulting' framework naming the conflation of decision quality and outcome.
- Michael J. Mauboussin, The Success Equation (Harvard Business Review Press, 2012). The luck-skill continuum.
- Daniel Kahneman, Olivier Sibony and Cass R. Sunstein, Noise: A Flaw in Human Judgment (Little, Brown Spark, 2021). Institutional decision discipline.
- Daniel Kahneman, Thinking, Fast and Slow (Farrar, Straus and Giroux, 2011). Hindsight bias and System 1/System 2 thinking.
- Philip E. Tetlock and Dan Gardner, Superforecasting (Crown, 2015). Calibration discipline in forecasting.
- Dan Lovallo and Olivier Sibony, 'Are You Solving the Right Problem?', Harvard Business Review (Jan-Feb 2017), and 'The Case for Behavioral Strategy', McKinsey Quarterly (March 2010).
- Atul Gawande, The Checklist Manifesto (Metropolitan Books, 2009). Structural decision discipline as a primitive.
- Bain Global Private Equity Report (annual). Top-quartile versus bottom-quartile discipline pattern data.
Questions
What is the difference between decision quality and decision outcome?
Decision quality measures whether a call was well reasoned given what was known at the time it was made. Decision outcome measures whether it worked. The two can disagree because investment decisions are made under uncertainty.
Why does evaluating by outcome alone cause problems?
Over the small number of decisions a typical committee reviews each year, luck dominates the signal more than it would over hundreds of trials. Rewarding lucky outcomes and punishing unlucky ones trains teams toward sloppier process and lower-confidence underwriting.
What is hindsight bias and why does it matter here?
Hindsight bias is the tendency to overestimate how predictable an outcome was once it is known. It makes reasonable assumptions look obviously flawed in retrospect, which is why post-outcome review should judge the decision against the evidence available at the time, before layering in what actually happened.
How should a committee evaluate a position before the outcome is known?
By asking whether the team identified the right risks, tested explicit downside scenarios, documented the decision basis, and committed to forward indicators that could invalidate the thesis, rather than projecting the current trajectory.
What do top-quartile investment committees do differently?
They type decisions at approval, name downside scenarios explicitly, commit to forward indicators in writing, separate decision quality from outcome in post-mortems, and keep institutional memory that survives team turnover.