Correct for availability and the planning fallacy by using an outside view.
Pick one plan you are working on now. Find two things in it: the risk your team worries about most, and the deadline you have given. For each, work out what it rests on. Either someone counted past cases, or the figure comes from a remembered story or a picture of the work going well.
Where it comes from matters because two common biases bend risk and time estimates in the same direction every time. Both are corrected by a single method, the outside view.
The availability heuristic is the habit of judging how common or probable something is by how quickly examples come to mind. Most of the time it gives a fair answer, because events that happen often are also easy to remember. It goes wrong when an event is memorable for some other reason: it was dramatic, it was in the news, it happened to you or someone close to you, or it was recent, say last week.
Wide coverage of plane crashes can make flying feel more dangerous than driving. One friend's story of a disastrous renovation contractor can make you wary of all contractors. The same thing happens at work. If a large client left after a billing error, billing errors start to feel like the main reason clients leave. Clients who leave quietly over price may well be more common, but nobody retells those stories. Vivid, recent threats seem likelier than frequent, dull ones.
Take Mei, a project lead (an invented example, with invented figures throughout, though the pattern turns up often). A data breach at another company is in the news. Two weeks later, Mei's director tells every project lead to add a security review to their plans. He has never raised the risk that delays most of their projects: clients taking weeks to sign off each stage. The breach is vivid and recent while slow sign-offs are frequent and dull, so the director sees the breach as the likelier threat.
The correction starts when a risk or result feels very likely. Ask whether that feeling comes from a count or from a memory. If you have data, use it. If you don't, get a rough count of past cases, for example a tally of which causes actually delayed past projects, and put the counts in front of the person making the decision. Mei could go through projects from the last two years, count those held up by a security issue and those held up by slow sign-off, and show both figures to the director.
The planning fallacy is the habit of underestimating both the time and the cost of a task, even when you know similar past tasks ran over. Kahneman and Amos Tversky named it, and Kahneman describes falling into it in the book Thinking, Fast and Slow.
Kahneman led a team writing a school curriculum. Everyone on the team, Kahneman included, estimated how long the work would take. Kahneman then asked an experienced colleague how long comparable teams had taken. The colleague's figure was far longer than any of the team's estimates, and the colleague added that a good share of such teams never finished. The team went ahead anyway, and the curriculum took years longer than planned.
Experience does not protect you from this mistake, because the cause lies in how plans are made. Most plans are made from the inside: you picture this particular project, lay out its steps, and imagine each one going roughly as intended. Many small things could go wrong along the way. Each one on its own is unlikely and hard to imagine, but together they make at least some delay very likely. A plan built from the inside, step by step, nearly always assumes a smoother path than the one that actually happens.
Kahneman's remedy is the outside view. Before you examine the details of the current project, find out how long similar projects took. That figure is the base rate, and it is your starting point. You adjust it afterwards, and only for things that are truly different this time.
Later, Mei's team makes an inside estimate of 8 weeks for a records migration. Mei checks the three most recent similar migrations, which took 10, 14 and 12 weeks. Their average is 12 weeks, half as long again as 8 weeks, or 50% longer. Mei starts from 12 weeks and looks for real differences. The client's data is cleaner this time, which makes the job easier and could support a slightly lower figure. The team will also use a new tool nobody on it has used before, which makes the job harder. Mei settles on 11 weeks, gives the client a deadline of 12 weeks as a margin, and writes down the reasons.
The steps, in order:
Before looking closely at the current project, find how long similar past projects took. Use that figure, such as the average of recent similar cases, as your starting point. Look for real differences this time, both the ones that make it easier and the ones that make it harder. Adjust only for differences that truly matter to the timeline, and judge by how much. Settle on an estimate, and add a margin to the deadline you give out. Write down why you chose that estimate.
The outside view feels gloomy, and the usual objection is "this one is different". Almost every project seemed different when it began. What you need to decide is whether a difference matters to the timeline, and by how much.
Getting the base rate is often the hardest step. At work, look in past project records, timesheets and old emails searched for dates, and ask colleagues who did similar work. Three past cases are far better than none.
The same two biases affect personal projects such as renovations, weddings, moving house, and studying for a part-time degree while working. These usually take longer and cost more than planned. For them, the base rate comes from people who did the same thing recently, so ask them. Investing decisions are affected too; the Behavioural Finance course covers that, and the examples here stay with work plans and everyday projects.
There is likely an estimate at work right now that was put together from the inside, step by step. In the activity below, you place it next to the outside view and see how far apart the two are.
Pick a project you are working on now, and note the risk your team fears most and your time estimate. Count how many past projects that risk actually delayed and how long three similar ones took, then revise both.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).