Rational Thinking and Bias
Kahneman and Tversky's biases give a name to the specific way a decision went wrong, so a team can build a check against that bias rather than just trying to think more carefully next time.
Trace the path from spotting a specific bias in a past decision to a standing rule that catches it next time.
Reach for this when…
- A decision failed and everyone agrees, in hindsight, the warning signs were obvious.
- The same type of project keeps running late by roughly the same margin.
- A leader keeps backing their first instinct even when new evidence arrives.
How to run it
- Introduce the core biases: confirmation bias, availability, anchoring, framing, loss aversion, planning fallacy.
- Have people name a real recent decision likely shaped by one of them.
- Apply a debiasing technique: pre-mortem, reference class forecasting, or actively seeking disconfirming evidence.
- Turn the debiasing technique into a standing check in your decision process.
A worked example
Situation. Abdulla Al-Kuwari ran product at a mobile payments startup in Doha, Qatar, where every launch date estimate had missed by roughly the same margin for three years.
Applied. The team named it as the planning fallacy and ran reference class forecasting on the next launch, pulling actual delivery times from their last six comparable releases instead of estimating from scratch.
Result. The reference-class estimate came in six weeks later than the team's gut number. They shipped on the reference-class date, on time, for the first time in the company's history.
The catch
Naming a bias after the fact is easy and can become its own bias, blaming psychology for what was actually a resourcing problem. The debiasing techniques also take real discipline to run under deadline pressure, which is exactly when people skip them.
If you can name the bias but keep making the same estimate anyway, you added vocabulary, not a check.
Origin: Daniel Kahneman & Amos Tversky