You have seen it happen in every organization you have ever worked
with. The quality improvement project that was supposed to take three
months is now entering its ninth month with no end in sight. The CAPA
that was marked “urgent” sits open for 472 days. The validation protocol
that everyone agreed would be straightforward turns out to require three
times the number of runs anyone anticipated. The new inspection system
that was budgeted at $200,000 has already consumed $600,000 and still is
not operational.
And every single time, the same thing happens in the post-mortem
meeting. People sit around the table, shake their heads, and say: “We
should have known.” But they never do. The next project gets the same
optimistic treatment. The next timeline gets the same aggressive
compression. The next budget gets the same wishful rounding down. And
the cycle repeats, not because people are stupid or incompetent, but
because the Planning Fallacy is one of the most deeply embedded
cognitive biases in organizational life — and in quality management, it
does not just cost time and money. It costs quality itself.
What Is the Planning Fallacy?
The Planning Fallacy was formally described by psychologists Daniel
Kahneman and Amos Tversky in 1979. It refers to the systematic tendency
of individuals and organizations to underestimate the time, costs, and
risks of future actions while simultaneously overestimating their
benefits. This is not simple optimism, although optimism plays a role.
It is a structural cognitive error that persists even when people have
direct, personal experience with similar tasks that went over budget,
past deadline, and under performance.
Kahneman himself admitted that he and Tversky fell victim to it while
writing the very book chapter that described the phenomenon. Their
original estimate for completing the chapter was one to two years. It
took eight. The team had access to data from other teams who had taken
similarly long on comparable projects, and they still believed they
would be different. That is the insidious power of the Planning Fallacy:
it does not yield to evidence.
In quality management, the Planning Fallacy manifests in a specific
and particularly damaging way. Quality professionals consistently
underestimate the complexity of improving quality systems, implementing
corrective actions, validating processes, and achieving certification.
They treat best-case scenarios as base-case scenarios. They plan as if
nothing will go wrong, even though everything always goes wrong. They
build schedules that assume perfect conditions, uninterrupted focus,
instant approvals, and cooperative suppliers — none of which exist in
reality.
The Anatomy of an
Underestimate
To understand why the Planning Fallacy is so persistent in quality
organizations, you need to understand how it is constructed. It is not a
single bad estimate. It is a cascade of compounding underestimates, each
one small enough to seem reasonable in isolation but devastating in
aggregate.
First, there is the scope underestimate. The team looks at the
problem — say, reducing defect rates in a welding operation — and
identifies what they believe are the key variables. They plan to
investigate five parameters. The actual number of variables affecting
weld quality turns out to be fourteen. The scope just grew by nearly 200
percent, but the timeline did not.
Second, there is the dependency underestimate. The quality
improvement project requires input from the materials lab, but the
materials lab is backlogged with customer complaints. It requires a
change to the work instruction, but the work instruction change requires
a review by three departments that have not met in two months. It
requires new measurement equipment, but the procurement process takes 90
days. Each dependency is a potential delay, and there are always more
dependencies than anyone anticipated.
Third, there is the rework underestimate. The team assumes that their
first approach will work. It does not. The gauge R&R fails, and the
measurement system has to be redesigned. The process capability study
shows the process is not capable, and the team has to go back to the
drawing board. The corrective action does not hold, and the defect
returns. Every iteration adds time that was never in the plan.
Fourth, there is the organizational friction underestimate. Approvals
take longer than expected. People are unavailable when needed.
Priorities shift. Budgets get reallocated. The project champion leaves
the company. These are not exceptional events — they are the normal
operating conditions of every organization — yet they are systematically
excluded from project plans.
Why Quality Is Especially
Vulnerable
Every discipline deals with the Planning Fallacy, but quality
management is uniquely susceptible for several reasons.
Quality work is inherently cross-functional. A CAPA might originate
in a customer complaint, but its root cause might lie in engineering,
its corrective action in manufacturing, its verification in the quality
lab, and its effectiveness check in field performance. Each handoff is a
potential delay, and the number of handoffs is almost always
underestimated.
Quality work deals with variability. When you plan a production run,
you have years of data on cycle times, downtime, and yields. When you
plan a quality investigation, you are dealing with an anomaly —
something that has not happened before or has not been adequately
characterized. The uncertainty is fundamentally higher, and the Planning
Fallacy exploits uncertainty by allowing planners to fill gaps with
optimistic assumptions.
Quality work is subject to regulatory scrutiny. A validation protocol
that would be straightforward in an unregulated environment becomes a
months-long ordeal when every deviation must be documented, every change
must be justified, and every conclusion must be defensible to an
auditor. Quality professionals who have lived through audits still
underestimate how much time regulatory compliance adds to a project.
Quality work is often perceived as overhead. In organizations where
quality is seen as a cost center rather than a value driver, quality
projects compete for resources with production, engineering, and
commercial priorities. When resources are scarce, quality projects get
delayed, and the delays are never factored into the original
timeline.
The Real
Cost: What Happens When Timelines Collapse
The direct costs of the Planning Fallacy in quality management are
obvious: projects run late, budgets overrun, and people get frustrated.
But the indirect costs are far more damaging.
When a quality improvement project runs over schedule, the
organization faces a choice: extend the timeline or compress the work.
Most organizations choose compression. They cut corners. They reduce the
number of validation runs. They skip the edge cases in the
investigation. They close the CAPA before the effectiveness check is
complete. They accept “good enough” evidence when they should demand
thorough evidence. And every one of those shortcuts is a seed that will
germinate into a future quality failure.
The Planning Fallacy also erodes organizational trust. When quality
teams consistently miss deadlines, leadership stops believing their
estimates. The natural response is to impose more aggressive timelines,
which only makes the problem worse. The quality team knows the timeline
is unrealistic but has stopped fighting because fighting never works.
They nod, commit to the impossible schedule, and then silently
prioritize what they can actually accomplish while hoping nobody notices
what gets dropped. This is how organizations develop a shadow quality
system — the one that exists on paper versus the one that actually
operates on the floor.
There is also a profound human cost. Quality professionals who are
perpetually working against unrealistic deadlines burn out. They stop
caring about excellence because excellence takes time they do not have.
They become checkbox tickers, going through the motions of quality
without the substance. The organization loses not just their
productivity but their expertise, their judgment, and their
engagement.
The
Reference Class: A Remedy Hiding in Plain Sight
Kahneman proposed a specific antidote to the Planning Fallacy, and it
is stunningly simple: use reference class forecasting. Instead of
planning a project from the inside out — building up a timeline task by
task, each with its own optimistic estimate — plan it from the outside
in. Look at similar projects that have been completed and use their
actual duration, cost, and outcomes as the baseline for your new
estimate.
In quality management, this means maintaining a database of past
projects with their original estimates and actual results. How long did
the last five CAPAs take to close? How much did the last three equipment
validations cost? How many runs did the last process qualification
actually require before achieving the desired capability? This data
exists somewhere in every quality organization, but it is almost never
used for planning. It is used for reporting, for compliance, for audit
readiness — but not for the one thing that could prevent the next
unrealistic timeline.
When a quality team says the new CAPA will take 30 days, the
reference class says the last 20 CAPAs of similar complexity took an
average of 90 days. The gap between 30 and 90 is not a difference of
opinion. It is the difference between the inside view and the outside
view. The inside view says: “This one is different. We have learned from
the past. The root cause is obvious.” The outside view says: “They said
that last time too.”
Implementing reference class forecasting in a quality organization
requires discipline. It means tracking not just whether a CAPA was
closed but how long it took, how many iterations were required, how many
resources were consumed, and what the obstacles were. It means creating
categories of quality projects — simple CAPAs, complex CAPAs, process
validations, system implementations — and maintaining actual performance
data for each category. And it means having the courage to present the
outside-view estimate to leadership, even when it is not the number they
want to hear.
Structural
Defenses Against the Planning Fallacy
Beyond reference class forecasting, there are structural changes that
quality organizations can make to reduce the impact of the Planning
Fallacy.
Add explicit buffers. This sounds obvious, but it is
remarkably rare in quality project plans. Every quality project should
include a buffer of 25 to 50 percent of the estimated duration,
allocated specifically for the unknowns that the Planning Fallacy will
inevitably reveal. The buffer is not padding — it is an honest
acknowledgment of uncertainty.
Require pre-mortems. Before a quality project
begins, gather the team and ask: “Imagine it is six months from now and
this project has failed spectacularly. What went wrong?” This exercise
forces the team to confront the risks they have been ignoring and builds
them into the plan.
Separate estimates from targets. An estimate is what
you believe will happen. A target is what you want to happen. In most
quality organizations, these are treated as the same number. They are
not. The estimate should be derived from the reference class. The target
can be more aggressive, but only if the organization is willing to
invest the additional resources and accept the additional risk required
to hit it.
Track estimate accuracy over time. If your quality
team’s estimates are consistently 40 percent low, add 40 percent to the
next estimate. This is not pessimism — it is calibration. A quality
organization that knows its estimation bias can correct for it. A
quality organization that ignores its estimation bias will repeat the
same mistakes indefinitely.
Make the cost of shortcuts visible. When a project
runs late and the organization considers compressing the work, quantify
the risk. What is the probability that skipping the additional
validation runs will result in a field failure? What is the cost of that
failure? Making these trade-offs explicit does not guarantee better
decisions, but it prevents the organization from making them
blindly.
A Personal Observation
After 25 years in quality, I can tell you that the Planning Fallacy
is not just an academic concept. It is the single most common source of
quality system failure I have encountered, and I do not mean missed
deadlines. I mean quality failures — defects that escaped, recalls that
happened, customers that were lost — because the timeline was
unrealistic, and the team responded by cutting the quality work to fit
the schedule.
I have seen organizations spend millions on quality management
systems that were implemented so hastily that they produced garbage
data. I have seen validation protocols so rushed that they validated
nothing. I have seen CAPAs closed on paper while the root cause
continued to generate defects on the floor. And in virtually every case,
the root cause of the shortcut was a timeline that was never realistic
to begin with.
The organizations that get quality right are not the ones with the
most sophisticated tools or the most experienced people. They are the
ones that plan honestly. They build timelines that account for reality.
They budget for the friction that every project encounters. They do not
confuse ambition with feasibility. And when the estimate comes in higher
than leadership wants to hear, they have the data and the courage to
defend it.
The Planning Fallacy will always be with us. It is wired into how
humans think. But in quality management, where the consequences of
underestimation are measured in defects, recalls, and sometimes human
safety, the obligation to resist it is not optional. It is
professional.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing excellence, process optimization,
and quality systems design. He writes about the intersection of human
psychology and operational performance because he believes that the best
quality systems are the ones that account for how people actually think,
decide, and behave — not how they should.
