Quality
and the Planning Fallacy: When Your Organization’s Project Timelines
Become Works of Fiction — and the Deadlines Everyone Agreed To Became
the Compromise Nobody Questioned
The Timeline That Was
Never Realistic
In 2017, a Tier 1 automotive supplier in Slovakia committed to
deploying a new quality management system across three plants in nine
months. The board approved the timeline. The quality director signed
off. The project charter looked impeccable — detailed Gantt charts,
milestones mapped to the week, resource allocations that appeared
reasonable on paper. The team even built in a “buffer” of three weeks
for unexpected issues.
Twenty-three months later, the system was still not fully
operational. Two of the three plants had gone live with partial
implementations. The third was still running parallel systems. The cost
overruns had consumed the contingency budget and then doubled it. The
quality director had been replaced. The new director inherited a project
that everyone had agreed was “on track” just six months earlier.
This is not an unusual story. It is, in fact, the norm.
The planning fallacy — first identified by psychologists Daniel
Kahneman and Amos Tversky in 1979 — describes the systematic tendency of
individuals and organizations to underestimate the time, cost, and risks
of future actions while overestimating their benefits. It is not
optimism, although optimism fuels it. It is not incompetence, although
incompetence amplifies it. It is a cognitive architecture — a built-in
feature of how human minds construct predictions about the future.
And in quality management, where project timelines determine
inspection schedules, supplier qualifications, process validations, and
regulatory submissions, the planning fallacy does not merely create
inconvenience. It creates the conditions under which defects thrive,
compliance fails, and organizations learn the wrong lessons from their
own failures.
Inside the
Fallacy: Two Systems, One Prediction
Kahneman’s dual-process theory provides the neurological foundation
for understanding why the planning fallacy persists even in
organizations full of experienced professionals.
System 1 — the fast, intuitive, automatic processor — generates the
initial estimate. It does this by constructing a best-case scenario. Not
the average case. Not the worst case. The best case. It
imagines everything going right: no supplier delays, no key personnel
resignations, no regulatory surprises, no equipment failures, no scope
creep, no competing priorities pulling resources away.
System 2 — the slow, analytical, deliberate processor — is supposed
to review and correct this estimate. But System 2 is lazy. It requires
effort and energy that the brain conserves by default. So when the
project manager presents a nine-month timeline that feels “about right,”
System 2 nods along, makes minor adjustments at the margins, and
approves.
The result is not a prediction. It is a wish dressed in professional
clothing.
In quality organizations, this plays out with remarkable
consistency:
- Process validation timelines that assume every run
produces acceptable data on the first attempt - FMEA completion schedules that allocate two days
for what requires two weeks of genuine cross-functional analysis - Corrective action implementation plans that treat
root cause investigation as a linear exercise rather than an iterative
one - Supplier audit calendars that schedule five audits
per week because “that’s what we did last year” - Software validation projects that budget zero time
for the interface issues nobody anticipated
Each of these plans shares the same structural flaw: they describe
what happens when nothing goes wrong, in a domain where something always
goes wrong.
The Reference Class Neglect
One of the most damaging features of the planning fallacy is what
Kahneman calls “reference class neglect” — the failure to look at
similar past projects and use their actual outcomes as a basis for
prediction.
When a quality team plans a new PPAP submission timeline, they almost
never start by asking: “How long did our last twelve PPAP submissions
actually take, from start to final approval?” They start by imagining
the steps, estimating each one in isolation, and adding them up. This
inside-view approach systematically excludes the reality of delays,
revisions, failed tests, customer rejections, and the organizational
friction that turns three-week tasks into three-month ordeals.
The data is usually available. PPAP logs exist. Project management
tools track actual versus planned dates. Calendar applications record
how many meetings were required. But the data is never consulted during
planning, because the planning mind prefers its own narrative
construction over the messy, discouraging evidence of history.
A pharmaceutical company I worked with discovered this the hard way.
Their average CAPA closure time over three years was 127 days. Their
target for new CAPAs was 45 days. When I asked how they arrived at 45,
the quality manager said, “That’s what the standard recommends.” The
standard recommended 45 days as a best practice — not as a realistic
target for an organization that had never closed a complex CAPA in less
than 90 days. The gap between aspiration and capability was not a
motivational tool. It was a systematic distortion that drove people to
close CAPAs superficially — checking boxes without addressing root
causes — just to hit a number that was never achievable.
The Social Mechanics
of Unrealistic Plans
The planning fallacy does not persist solely because of cognitive
architecture. It persists because of organizational dynamics that reward
optimism and punish realism.
Consider the typical planning meeting. A quality director presents a
project timeline. The VP of Operations asks if it can be compressed. The
quality director, who knows the timeline is already optimistic, faces a
choice: defend the estimate and be seen as obstructionist, or agree to
compression and be seen as collaborative. The political incentives favor
compression. The facts favor defense. Politics wins.
This dynamic creates what I call “aspirational scheduling” —
timelines that everyone knows are unrealistic but that nobody is willing
to challenge because challenging them carries social costs. The project
manager who points out that similar projects consistently take twice as
long is labeled negative. The engineer who asks for more testing time is
called risk-averse. The quality lead who requests additional resources
is told to “work smarter.”
The result is a conspiracy of optimism. Not a conscious conspiracy —
no one sits in a room and decides to deceive — but a shared willingness
to proceed with plans that experience has repeatedly disproven, because
the social cost of acknowledgment exceeds the financial cost of
delay.
I witnessed this at a medical device manufacturer where the
leadership team approved a 12-month timeline for IATF 16949
certification. The consultant they hired told them 18 months was
realistic. The internal quality team privately estimated 24 months. The
leadership team chose 12 months because “the customer requires it by
Q4.” The certification was achieved in 22 months, after two failed
audits, one consultant replacement, and a near-complete turnover of the
quality department staff who burned out trying to hit an impossible
target.
Where the Fallacy
Strikes Hardest in Quality
The planning fallacy affects every aspect of quality management, but
certain areas are disproportionately vulnerable:
Process Validation
Validation protocols assume that processes behave predictably from
run one. They do not. First runs reveal problems. Second runs reveal
different problems. By the third run, you understand the process well
enough to design a proper validation. But the plan allocates three
consecutive successful runs in two weeks, and when run one fails, the
entire schedule collapses.
Root Cause Investigation
Organizations plan root cause analysis as a discrete event — a
two-day workshop that produces a definitive answer. In practice, genuine
root cause investigation is iterative. You form a hypothesis, test it,
discover it is wrong, form a new hypothesis, test again, discover the
problem is more complex than expected, expand the scope, involve new
people, and gradually converge on the truth. This process takes weeks or
months, not days. But the CAPA form has a field for “Root Cause
Identified Date” that is expected to be filled in within 72 hours of the
initial complaint.
Culture Change Initiatives
Quality transformation projects — implementing a new QMS, shifting
from detection to prevention, building a quality culture — are routinely
planned with the same tools used for construction projects. Gantt
charts, critical paths, resource histograms. But culture does not follow
a Gantt chart. People do not change their beliefs about quality because
a project charter says they should change by Q3. The planning fallacy in
culture change is particularly insidious because the metrics of
“success” are vague enough that organizations can declare victory while
nothing has actually changed.
Supplier Development
When a supplier quality engineer plans a supplier improvement
project, the plan typically includes the supplier’s commitment to
implement changes within the agreed timeline. What it does not include
is the supplier’s competing priorities, their internal resistance to
change, their resource constraints, their financial limitations, and the
fact that they promised the same improvements to three other customers.
The plan assumes the supplier is a reliable execution partner.
Experience shows they rarely are.
The
Solution That Almost Works: Reference Class Forecasting
Kahneman’s proposed remedy for the planning fallacy is reference
class forecasting — the practice of basing predictions on the actual
outcomes of similar past projects rather than on the specific details of
the current one.
The technique is straightforward:
-
Identify the reference class. What category of
project are you planning? Process validation? CAPA closure? Supplier
audit? QMS implementation? -
Gather historical data. How long did the last
ten projects in this category actually take? Not the planned duration —
the actual duration. Not the optimistic estimate — the real
number. -
Compute the base rate. What is the average,
median, and range of actual durations? What percentage came in on time?
What percentage exceeded the estimate, and by how much? -
Adjust for specific factors. Is this project
simpler or more complex than average? Are the resources more or less
available? Is the team more or less experienced? Make directional
adjustments, not wholesale revisions. -
Build the plan from the adjusted base rate. The
historical data becomes your starting point, not your ceiling.
A Tier 1 automotive supplier I advised implemented this approach for
their APQP timelines. Their historical data showed that new product
launches had a median duration of 14 months from kick-off to PPAP
approval, with a range of 11 to 23 months. Their standard planning
template had assumed 9 months. When they recalibrated to the historical
base rate and communicated the realistic timeline to their customer,
three things happened:
First, the customer pushed back — hard. They had built their own
production schedule around the 9-month assumption. But when the supplier
presented the data — not opinions, not estimates, but 47 completed
launches with actual timelines — the negotiation shifted from “why can’t
you do it faster” to “what would it take to accelerate, and what are the
risks.”
Second, the project team experienced a measurable reduction in stress
and overtime. They were no longer working against a clock that had been
set to an impossible pace. Morale improved, and paradoxically,
productivity improved with it.
Third, the actual launch came in at 13 months — one month under the
base rate. The first time in the supplier’s history that a major launch
came in ahead of a realistic schedule, because the realistic schedule
gave them the space to plan properly, execute carefully, and address
problems when they were small instead of when they were crises.
The Pre-Mortem:
Imagining Failure to Prevent It
Gary Klein’s pre-mortem technique provides a complementary defense
against the planning fallacy. Before the project begins, gather the team
and ask: “It is twelve months from now. This project has failed. What
went wrong?”
This question activates a different cognitive pathway. Instead of
constructing a best-case narrative (System 1), the team is asked to
construct a failure narrative. This engages the analytical, skeptical
functions that remain dormant during normal planning. People who sat
quietly during the optimistic planning session suddenly have a list of
risks they were reluctant to mention.
In quality projects, pre-mortems consistently surface the same
categories of risk:
- Key personnel will be pulled onto other priorities mid-project
- The customer will change requirements after work has begun
- The IT system will not be ready when needed
- The training will be rushed and ineffective
- The pilot will reveal problems that were not anticipated
- Management attention will shift to the next crisis
These risks are not surprises. They are the normal operating
conditions of quality projects. The pre-mortem simply creates permission
to acknowledge them before they become emergencies.
Building a Realistic
Planning Culture
Overcoming the planning fallacy requires more than individual
awareness. It requires organizational systems that reward accuracy over
optimism.
Track and publish actual versus planned data. Make
the gap visible. When every project in the organization has a
retrospective that compares the original plan to the actual outcome, and
when those comparisons are stored in a searchable database, the
reference class data builds itself.
Separate aspiration from prediction. It is perfectly
valid to aspire to close CAPAs in 45 days. It is dishonest to plan as
though 45 days is the expected outcome when the historical average is
127. State the aspiration. State the prediction. Track both. Let the gap
between them drive improvement, not deception.
Reward the messenger. The engineer who says “this
will take six months, not three” is not being negative. They are being
accurate. Organizations that punish accuracy and reward optimism create
the conditions for the planning fallacy to flourish. The fix is
cultural: when someone provides a realistic estimate that is higher than
leadership wants to hear, the response should be gratitude for honesty,
not pressure to compress.
Build planning buffers that match historical
variance. If historical data shows that process validations
typically take 40% longer than planned, build a 40% buffer into the next
plan. This is not padding — it is calibration. A buffer that matches
historical variance is a realistic plan. A plan without such a buffer is
a fiction.
Use range estimates instead of point estimates.
Instead of saying “the QMS implementation will take 12 months,” say “the
QMS implementation will take 12 to 18 months, depending on resource
availability and the complexity of legacy system migration.” Range
estimates are more honest, more useful, and more defensible when
leadership inevitably asks for compression.
The Deeper Lesson
The planning fallacy persists because it serves a psychological
function. Optimistic plans feel good. They signal confidence, ambition,
and capability. They tell stakeholders what they want to hear. They
allow organizations to commit to targets that look impressive in
presentations and quarterly reports.
But in quality management, the cost of unrealistic planning is not
merely delayed projects and blown budgets. It is compromised quality.
When timelines compress, the first thing sacrificed is thoroughness.
Inspections get rushed. Training gets abbreviated. Validation runs get
fewer iterations. Root causes get superficial treatment. The process
that was supposed to be validated in three runs gets validated in one
“successful” run that nobody had time to question.
The planning fallacy does not just create late projects. It creates
defective products, failed audits, customer complaints, and the slow
erosion of quality culture as people learn that the plans are
performative — that the real plan is “do whatever it takes to hit the
date, and hope nothing goes wrong.”
The antidote is not pessimism. It is realism. And realism begins with
a simple question that most organizations never ask: “The last time we
did this, how long did it actually take?”
The answer to that question is the only honest starting point for the
next plan.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He specializes in building quality
systems that work in the real world — not just on paper — and has helped
dozens of companies close the gap between what they plan and what they
actually deliver.
