A project manager who consistently finishes projects 2× over schedule decides to add a 25% time buffer to all future estimates. Based on the planning fallacy, what will most likely happen?
AProjects will now finish on time, because the buffer compensates for the systematic underestimation
BProjects will still run over, because the buffer itself was sized using the inside view rather than anchored to actual base rates
CThe buffer will cause projects to finish early, creating slack time
DThe bias will be corrected once the manager gains more experience with the buffered estimates
Adding a buffer does not fix the planning fallacy if the buffer is also estimated using the inside view — optimistic reasoning about the specific plan. If your typical ratio of actual-to-estimated time is 2×, a 25% buffer still leaves you systematically short. The correct fix is reference class forecasting: look at the base rate of similar projects (how long did comparable projects actually take?), anchor your estimate there, then adjust for genuinely unique factors. The buffer must come from outside the plan, not from inside it.
Question 2 Multiple Choice
Why does the planning fallacy persist even in experienced professionals who have repeatedly seen their estimates fail?
ABecause experience degrades memory for past failures, making people increasingly optimistic over time
BBecause the inside view — focusing on the specific details of the current plan — continues to dominate over outside-view base rates even when past experience contradicts it
CBecause professionals are overconfident in their domain expertise and refuse to update on evidence
DBecause the fallacy only affects time estimates, and experienced professionals make errors in different dimensions
The planning fallacy is not a knowledge problem — people know their past projects went over. It is a view-selection problem: when planning, the mind naturally focuses on the specific scenario ('this time we have X, Y, and Z advantages'), generating inside-view estimates that ignore base rates. Experience with overruns does not automatically trigger outside-view reasoning. Kahneman and Tversky identified this view dominance as the structural root cause: the fix requires deliberately switching to the outside view, not just accumulating more experience.
Question 3 True / False
A person who has finished every past project at least 80% over their initial time estimate can still, in good faith, underestimate their next project's duration.
TTrue
FFalse
Answer: True
Yes — this is the essence of the planning fallacy. It is not a matter of dishonesty or incompetence. The inside view generates genuinely felt optimism about the current plan's specific features. Even people with clear track records of overruns continue to underestimate because the mental process of planning attends to the plan's details rather than the reference class of similar past outcomes. This is why passive experience is insufficient; deliberate use of reference class forecasting is required.
Question 4 True / False
The planning fallacy is primarily a problem of laziness: if planners simply worked harder to identify risks and dependencies, they would produce accurate estimates.
TTrue
FFalse
Answer: False
This is false. The planning fallacy is not caused by insufficient effort — it is a systematic cognitive bias in which the inside view (focusing on how this particular plan will unfold) crowds out outside-view base rates. More detailed planning often makes the fallacy worse, because elaborating the plan's steps makes success feel more vivid and concrete. Kahneman and Buehler's research shows the bias affects experts and careful planners just as much as novices. The corrective is not more inside-view analysis but a deliberate switch to outside-view reference class data.
Question 5 Short Answer
Why is adding a buffer to an estimate insufficient to correct the planning fallacy, and what approach actually works?
Think about your answer, then reveal below.
Model answer: A buffer is insufficient if it is sized using the inside view — reasoning about what could go wrong in this specific plan. Such buffers inherit the same optimism bias as the original estimate. The approach that actually works is reference class forecasting: identify a class of similar past projects, find the actual distribution of outcomes (especially the typical overrun ratio), and anchor the estimate to that base rate. Only after anchoring to outside-view data should you adjust for features that genuinely make this project different. Tracking your own planning ratio (actual / estimated) over time gives you a personalized correction factor.
The key distinction is inside view vs. outside view. The inside view produces estimates by imagining the specific plan unfolding — which feels accurate but is systematically optimistic. The outside view asks: 'What happened to projects like this one?' Buehler's research showed that asking people 'how long did similar tasks take you in the past?' produced dramatically more accurate estimates than asking 'how long will this task take?' The buffer must be derived from outside the plan, not generated by elaborating the plan further.