Kahneman: fast and slow thinking in projects
The steering committee is pushing you for a delivery date. You feel the answer coming instantly: "mid-October". It feels certain, almost obvious. But where did that number come from? Probably not from a calculation – but from your intuition. And intuition, no matter how experienced you are, has predictable blind spots.
The psychologist Daniel Kahneman received the Sveriges Riksbank Prize in Economic Sciences in Memory of Alfred Nobel in 2002 for his research on human decision-making, much of it together with Amos Tversky. In his 2011 book Thinking, Fast and Slow he summarised a life's work – and gave us the language to understand our own misjudgements.
What does the research say?
Kahneman describes thinking as two systems. System 1 is fast, automatic and effortless – it reads facial expressions, completes sentences and delivers gut feelings. System 2 is slow, effortful and deliberate – it calculates, compares options and scrutinises assumptions. We need both: without System 1 we couldn't get through an ordinary day. The problem is that System 1 is systematically biased, and that System 2 is lazy – it happily accepts the quick answer, especially under time pressure, stress or fatigue.
Research has mapped a series of recurring thinking errors. The anchoring effect: the first number mentioned pulls all later judgements towards it, even when it is arbitrary. Availability bias: what comes to mind easily – the most recent, the most dramatic – feels more likely than it actually is. And the one that hits project managers hardest: the planning fallacy, Kahneman and Tversky's term for our stubborn tendency to underestimate the time and cost of our own projects, even though we know that similar projects usually overrun.
Kahneman's conclusion is not that intuition is worthless – in environments you have trained in for a long time, with fast feedback, it becomes accurate. The conclusion is that you need to know when it is not enough: in new situations, under pressure and when a lot is at stake, System 2 needs to be engaged deliberately.
What does this mean for you as a project manager?
Never give estimates in real time under pressure. The spontaneous answer in the meeting comes from System 1 and is almost always too optimistic. Practise the phrase: "I want to run the numbers on that – you'll have it tomorrow morning." Buying yourself a few hours is how you engage System 2.
Counter the planning fallacy with the outside view: don't just ask "how long will this take us?" but "how long have similar projects actually taken?". Base your estimate on that track record first, then adjust – not the other way around. The track record knows things your optimism doesn't want to know.
And in charged conversations: notice when you react on autopilot. An attack in a meeting triggers an immediate defence from System 1. A deliberate pause – breathing, summarising what the other person said – gives System 2 time to choose a response instead of firing one off.
How to practise this
Recognising your autopilot requires situations where it actually kicks in. Project-simulator's high-pressure scenarios are built for exactly that: the other party demands answers, anchors numbers and raises the tempo – and in the debrief afterwards you see, in your own words, where you responded reflexively and where you slowed down. Try it free for a week at project-simulator.com.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days