Thinking, Fast and Slow: better business decisions

Who should use it, and when not to

Use it before decisions that are hard to undo: a hire, a price change, an investment, a launch date. It helps most when a forecast feels confident but rests on one story, or when a meeting agreed fast and nobody argued.

It's not needed for small, reversible choices. Deciding quickly there is usually right. To sort which decisions deserve the slow treatment, see the door check skill.

The core ideas

System 1 and System 2. System 1 recognizes faces and finishes "bread and…" without effort. System 2 does long division. System 2 is lazy: it often endorses System 1's answer, especially when we're tired or busy.

What you see is all there is. Kahneman's phrase for building a confident story from the information at hand, without asking what's missing.

Anchoring. A number mentioned first pulls later estimates toward it, even when it is irrelevant.

The planning fallacy and the outside view. Plans are built from the inside, from the details of our own project, so they are too optimistic. The outside view starts from a reference class of similar projects and adjusts from there.

Loss aversion and framing. Losses weigh more than equal gains, so the same choice framed as a loss or a gain can get different answers. This comes from prospect theory, Kahneman's work with Amos Tversky.

The pre-mortem. A technique from Gary Klein that the book recommends: assume the plan failed and explain why. It gives doubters a safe way to speak.

A worked mini example

This is an illustration. A café owner plans a second café. The manager says fit-out will take 6 weeks because the first one did, and expects 900 euros of daily sales by month two, close to the first café's 1,100 today. The contractor's last two jobs ran about 4 weeks late. The landlord says the rent is 20% below market.

A pre-mortem adds a risk nobody raised: a late opening that misses the spring season, with a 10-year lease locking in losses.

How to review a decision

1. Write the decision and the intuitive answer, with the one-sentence reason people give.
2. Trace each key number to its source, and flag anchors and single vivid cases.
3. List what's missing: the information that would matter but isn't in front of you.
4. Reframe the choice as a gain and as a loss, and see whether the preference changes.
5. Take the outside view: name a reference class and its typical outcome.
6. Run a pre-mortem: three to five reasons it failed, each with an early warning sign.
7. Decide, and write what evidence would change the call.

The decision bias review skill runs these steps on your decision and marks numbers without a source.

Common mistakes

• Listing every bias. Name only the ones your facts show.
• Inventing base rates. A made-up reference class is just another anchor.
• Using the review to block decisions. The aim is a better estimate, not a veto.
• Quoting every study as settled. Some priming studies in the book failed to replicate, and Kahneman acknowledged it. The decision tools don't depend on them.

Where it comes from

Daniel Kahneman, a psychologist, received the 2002 Nobel Memorial Prize in Economic Sciences for work on judgment and decision-making under uncertainty, much of it with Amos Tversky. Thinking, Fast and Slow, published in 2011 by Farrar, Straus and Giroux, brings that research together for general readers. Kahneman died in 2024.

This page is an independent summary in our own words. It is not affiliated with or endorsed by the author's estate or publishers. The book's title is used only to name it. More explainers are in the business books index.

Questions

What are System 1 and System 2?

Kahneman's labels for two modes of thinking. System 1 is fast, automatic and intuitive. System 2 is slow, effortful and deliberate. Many errors happen when System 2 accepts System 1's quick answer without checking it.

What is the planning fallacy?

The tendency to plan from the best case of your own project, so estimates of time and cost come out too optimistic. The book's fix is the outside view: start from how similar projects turned out.

What is a pre-mortem?

Before a decision is final, the team imagines it is a year later and the decision has failed, then writes down why. Kahneman recommends the technique, which comes from the psychologist Gary Klein.