The planning fallacy fundamentals

• A. A tendency to overestimate how much time, cost, or risk a future task will involve, while underestimating how long it will actually take
• B. A tendency to underestimate how much time, cost, or risk a future task will involve, while overestimating how much progress we will make ✓
• C. A belief that people who plan carefully always finish projects on schedule
• D. A bias in which people refuse to create any plan at all because they fear failure

Why: The planning fallacy, identified by Daniel Kahneman and Amos Tversky, describes the systematic tendency to underestimate the time, costs, and risks of future actions while overestimating the benefits, so people routinely expect projects to finish sooner than they do.

• A. B. F. Skinner
• B. Sigmund Freud
• C. Daniel Kahneman and Amos Tversky ✓
• D. Ivan Pavlov

Why: Daniel Kahneman and Amos Tversky introduced the planning fallacy in 1979 as part of their broader work on judgment and decision-making under uncertainty.

• A. The sunk cost fallacy
• B. The planning fallacy ✓
• C. Confirmation bias
• D. The availability heuristic

Why: Underestimating how long a task will take despite past experience with similar tasks is a classic example of the planning fallacy.

• A. They focus on the specific details of the upcoming task rather than on how similar tasks have gone in the past ✓
• B. They always use historical data to make their forecasts
• C. They deliberately pad their estimates to avoid blame
• D. They assume that unexpected problems will never occur

Why: People tend to take an 'inside view,' imagining the specific steps of a task in a best-case scenario, rather than an 'outside view' based on how comparable projects actually turned out.

• A. Ignoring past projects so you can focus on the present
• B. Using reference class forecasting, which bases estimates on the actual outcomes of similar past projects ✓
• C. Setting the deadline as early as possible to motivate faster work
• D. Trusting your gut feeling about how long something will take

Why: Reference class forecasting counters the planning fallacy by anchoring estimates in real historical data from comparable tasks, rather than in optimistic mental simulations of the current task.

• A. The tendency to overestimate the accuracy of weather forecasts
• B. The tendency to underestimate how long tasks will take and how much they will cost ✓
• C. The tendency to plan projects only after deadlines have passed
• D. The tendency to avoid planning altogether to reduce stress

Why: The planning fallacy, identified by Daniel Kahneman and Amos Tversky, describes the consistent tendency for people to underestimate the time, costs, and risks of future tasks, even when they have experience with similar tasks running late before.

• A. They deliberately lie to their managers about timelines
• B. They focus on the best-case scenario and ignore interruptions and setbacks ✓
• C. They always finish tasks faster than they expect
• D. They lack any information about the task at all

Why: People often imagine a smooth, ideal sequence of steps and fail to account for delays, unexpected problems, and interruptions that typically occur in real projects.

• A. Ignoring past project data so you stay optimistic
• B. Using reference class forecasting by looking at how long similar past projects actually took ✓
• C. Adding a fixed buffer of exactly one day to every task regardless of size
• D. Asking only the most optimistic team member for an estimate

Why: Reference class forecasting grounds estimates in actual outcomes of comparable past projects, which corrects for the inside-view optimism that drives the planning fallacy.

• A. A team finishes a software release two days early because they worked hard
• B. A student who has written three late essays predicts their next essay will be done a week early ✓
• C. A contractor accurately estimates the cost of materials using supplier price lists
• D. A person checks the weather before planning an outdoor event

Why: The student ignores their own history of late essays and makes an overly optimistic prediction, which is the core pattern of the planning fallacy.

• A. Experienced professionals are unaware that past projects ran late
• B. Planning is primarily based on memory of how things went, which tends to forget delays ✓
• C. Experienced professionals never use estimates at all
• D. Estimates made by experts are always randomly generated

Why: Memory tends to be selective, so people often remember the intended plan rather than the delays that actually happened, and the optimistic inside view remains strong even among experienced workers.

• A. Outside-view thinking, based on reference class data from similar projects
• B. Inside-view thinking, based on a detailed mental simulation of this specific project ✓
• C. Base-rate thinking, based on the historical frequency of project delays
• D. Reference-class forecasting, based on the average duration of comparable projects

Why: Inside-view thinking focuses on the specific details of the case at hand and imagines how it will unfold. The team's step-by-step mental picture of their own project is a classic inside view, which tends to overlook unexpected obstacles and underweight how similar projects have actually gone.

• A. To gather more detailed information about the project's specific tasks
• B. To anchor the estimate on how long comparable projects have historically taken ✓
• C. To make the team feel more confident about meeting its deadline
• D. To identify which team members are most likely to cause delays

Why: The outside view anchors a forecast on the track record of a reference class of similar projects rather than on the particulars of the current one. This counteracts the optimism that the inside view tends to produce, because past outcomes reveal how often projects overrun.

• A. People deliberately ignore past data to appear more ambitious to managers
• B. People tend to believe their own project is different and will avoid the problems that affected others ✓
• C. Historical data is usually unavailable for most types of projects
• D. Estimation tools are too complex for most people to use correctly

Why: A common reason the planning fallacy persists is the belief that 'this time is different.' People focus on the unique features of their own project and assume they will avoid the setbacks that affected similar efforts, so the inside view wins out despite contrary evidence.

• A. How do you imagine the next few weeks will go for your thesis?
• B. What tasks remain, and how long does each one take you?
• C. How long did it take students in past years to finish theses like yours? ✓
• D. How confident are you that you can meet your planned deadline?

Why: Asking how long comparable students actually took shifts attention to a reference class of similar cases, which is the defining feature of an outside view. The other options all keep the focus on the individual student's own plans and feelings, which invites inside-view optimism.

• A. Trust your gut feeling about how smoothly the project will proceed
• B. Identify a reference class of similar past projects and adjust your estimate toward their typical outcomes ✓
• C. Break the project into the smallest possible tasks and estimate each one optimistically
• D. Assume the project will take exactly as long as the client requested

Why: Outside-view forecasting involves choosing a relevant reference class of comparable past projects, looking at their actual durations or outcomes, and adjusting your forecast toward that base rate. Relying on gut feeling or optimistic task-level estimates reflects the inside view that produces the planning fallacy.

• A. The tendency to underestimate the time, cost, and risks of future actions while overestimating their benefits ✓
• B. The tendency to overestimate the time, cost, and risks of future actions while underestimating their benefits
• C. The tendency to plan only for the most likely outcome and ignore rare events
• D. The tendency to repeat past plans exactly without adjusting for new information

Why: The planning fallacy, identified by Kahneman and Tversky, describes how people systematically underestimate how long tasks will take and how much they will cost, while overestimating the benefits and underestimating the risks.

• A. Confirmation bias
• B. Anchoring bias
• C. Optimism bias ✓
• D. Availability heuristic

Why: Optimism bias, the tendency to expect better outcomes than warranted, is a root cause of the planning fallacy because it leads people to assume that things will go smoothly and according to plan.

• A. Choosing a restaurant based on recent reviews
• B. Believing a home renovation will finish in two months when similar projects typically take six ✓
• C. Remembering a vacation more fondly after returning home
• D. Agreeing with a group's decision to avoid conflict

Why: Expecting a renovation to finish quickly despite evidence that similar projects run long is a classic planning fallacy, as the estimate ignores the typical duration of comparable tasks.

• A. Relying only on your own gut feeling about how long a task will take
• B. Using reference class forecasting, which bases estimates on the outcomes of similar past projects ✓
• C. Setting deadlines as early as possible to create pressure
• D. Avoiding any written plans so that expectations stay flexible

Why: Reference class forecasting counters the planning fallacy by anchoring estimates to actual historical outcomes of similar projects rather than to the optimistic details of the current plan.

• A. Because they are unable to remember past experiences
• B. Because they tend to imagine the steps of success in detail while giving little attention to delays and obstacles ✓
• C. Because planning requires them to ignore all negative information
• D. Because best-case scenarios are always the most statistically likely

Why: People often construct vivid, detailed mental pictures of how a plan will unfold successfully, which makes success feel more probable and leaves unexpected problems underrepresented in their estimates.

• A. Estimating the time by carefully modeling every task in the specific project plan
• B. Basing the estimate on the actual outcomes of similar past projects, rather than on the details of the current plan ✓
• C. Asking the project team to give their most optimistic completion date
• D. Averaging the estimates made by all stakeholders involved in the project

Why: Reference class forecasting uses the distribution of outcomes from a relevant set of comparable past projects as the basis for prediction. This sidesteps the inside view, which tends to be overly optimistic because it focuses on the unique features of the current plan.

• A. Planners deliberately inflate estimates to win approval for their projects
• B. Planners focus on the specific steps they can foresee and underweight unexpected delays, interruptions, and problems that historically occur ✓
• C. Project plans are typically written by people with no experience in the field
• D. Estimates are always based on completed tasks rather than remaining work

Why: The inside view builds a story of how the project will go step by step, which tends to ignore the many unforeseen obstacles that appear in practice. Planners often assume things will go smoothly, which produces systematic underestimation rather than deliberate deception.

• A. Identify a reference class of similar past projects with known outcomes ✓
• B. Break the current project into the smallest possible tasks
• C. Ask the lead engineer to estimate the most likely completion date
• D. Add a fixed contingency buffer of 20 percent to the initial plan

Why: The first step is choosing an appropriate reference class: a set of past projects comparable in type, scale, and context. Only after this can you look up the distribution of their outcomes and adjust for any differences from the current project.

• A. Ignore the historical data because this project is unique
• B. Assume the project will come in exactly on budget since the team is experienced
• C. Use the historical distribution to set a budget that accounts for typical overruns, and adjust only for clearly justified differences ✓
• D. Reduce the planned budget to force the team to work more efficiently

Why: Reference class forecasting says to anchor on the base rate from comparable cases. You can then adjust for specific factors that genuinely differ, but the historical overrun pattern should drive the forecast rather than being dismissed as irrelevant.

• A. A broader class always gives more accurate predictions than a narrow one
• B. A class that is too narrow may contain too few cases, while one that is too broad may include projects that are not truly comparable, so the choice affects the forecast ✓
• C. The reference class should always consist of the single most similar project
• D. The choice of reference class does not affect the forecast once the data is collected

Why: Selecting the reference class involves a trade-off: narrow classes are more relevant but may have too little data, while broad classes have more data but may mix in dissimilar cases. Both extremes can distort the forecast, so the choice matters.

• A. The tendency to underestimate the time, costs, and risks of future tasks despite knowledge of past similar experiences ✓
• B. The tendency to overestimate the time, costs, and risks of future tasks despite knowledge of past similar experiences
• C. The belief that planning is unnecessary for experienced professionals
• D. The habit of creating detailed schedules that are never followed

Why: The planning fallacy, identified by Kahneman and Tversky, describes the consistent tendency to underestimate how long tasks will take and what they will cost, even when people have repeatedly experienced overruns on similar past tasks.

• A. To give team members extra free time to rest between tasks
• B. To absorb unexpected delays so that they do not cascade into missed deadlines ✓
• C. To increase the official project budget for management approval
• D. To delay the start date so that the project appears more realistic

Why: A buffer is protected time added to a schedule to absorb the inevitable delays and surprises. It prevents small setbacks from cascading into missed deadlines and counteracts the optimistic bias the planning fallacy produces.

• A. Asking team members to simply work faster to meet the original estimate
• B. Using reference class forecasting by basing estimates on outcomes of similar past projects ✓
• C. Removing all deadlines so that work can proceed without pressure
• D. Estimating only the tasks that are easiest to predict

Why: Reference class forecasting shifts attention from the unique details of the current project to the actual results of comparable past projects. This outside view corrects the inside-view optimism that causes the planning fallacy.

• A. The estimate is accurate because the team is confident
• B. The planning fallacy, since the estimate ignores historical evidence of longer durations ✓
• C. Scope creep, since the feature grew over time
• D. Parkinson's law, since work expands to fill available time

Why: The team is anchoring on an optimistic inside-view estimate and ignoring the base rate from comparable past work. This is the classic signature of the planning fallacy.

• A. Hidden inside individual task estimates so that no one knows it exists
• B. Only at the very beginning of the project before any work starts
• C. As a visible, explicit allowance at the project or milestone level, separate from task estimates ✓
• D. Nowhere, because buffers encourage people to slack off

Why: Keeping buffers explicit and separate from task estimates makes them visible for management decisions and prevents padding within tasks. Hidden padding tends to be consumed by Parkinson's law, while explicit project-level buffers protect the overall deadline.

• A. The tendency to overestimate the accuracy of weather forecasts
• B. The tendency to underestimate the time, costs, and risks of future tasks despite knowing past projects ran over ✓
• C. The tendency to plan projects in too much detail before starting
• D. The tendency to avoid planning altogether to reduce anxiety

Why: The planning fallacy, described by Kahneman and Tversky, is the systematic underestimation of how long tasks will take and what they will cost, even when people have direct evidence that similar past tasks took longer.

• A. Adding a fixed 10% buffer to every estimate regardless of the task
• B. Asking team members to estimate faster so the schedule feels more ambitious
• C. Using reference class forecasting by comparing the project to similar completed projects and their actual outcomes ✓
• D. Focusing only on the best-case scenario to keep morale high

Why: Reference class forecasting bases the estimate on the actual historical outcomes of comparable projects rather than on the specifics of the plan, which pulls the forecast toward realistic results instead of optimistic inside-view reasoning.

• A. They lack any information about the project
• B. They focus on the specific plan and imagine smooth execution, neglecting interruptions and unexpected problems ✓
• C. They intentionally deceive stakeholders about timelines
• D. They always underestimate the importance of the project

Why: People tend to take an 'inside view,' concentrating on the steps they have planned and assuming things go as intended, while underweighting the many delays, dependencies, and surprises that typically occur.

• A. Trust the team's expertise and proceed with the two-week plan
• B. Ignore the past data because this update is different
• C. Adjust the forecast using the historical data and break the work into smaller tasks to identify hidden steps ✓
• D. Tell the team to work faster to meet the two-week target

Why: Using historical evidence to adjust the estimate and decomposing the work to reveal overlooked steps are practical ways to correct for optimism. Ignoring data or simply pressuring the team does not address the underlying bias.

• A. Too much time spent on quality review
• B. Overlooked dependencies, integration work, and testing that are not included in the initial plan ✓
• C. Having too many stakeholders reviewing progress
• D. Using detailed project management software

Why: Plans often omit dependencies, integration effort, testing, and rework, so the estimate covers only the visible core tasks. Recognizing these hidden components helps produce more realistic schedules.