The Timeline That Was
Never Realistic
Every quality initiative begins the same way: a room full of
managers, a whiteboard full of ambitions, and a Gantt chart that defies
the laws of physics. The corrective action will take two weeks. The new
inspection system will be running by month’s end. The cultural
transformation toward zero defects will be complete by Q3. Everyone
nods. The timeline gets printed, laminated, and pinned to the wall where
it will die a quiet death over the next six months while everyone
pretends it never existed.
This is the Planning Fallacy at work, and it is arguably the most
expensive cognitive bias in manufacturing quality management. First
identified by psychologists Daniel Kahneman and Amos Tversky in 1979,
the Planning Fallacy describes our tendency to underestimate the time,
cost, and risks of future actions while overestimating their benefits —
even when we have direct experience with similar past projects that went
over time, over budget, and underdelivered.
In a manufacturing environment, this isn’t an academic curiosity.
It’s the reason your corrective actions close late, your capital
improvement projects consume double their allocated budgets, and your
organization keeps launching quality initiatives with the same naive
enthusiasm it had the last time — and the time before that — despite a
track record that should have taught everyone to be far more
cautious.
Why We Keep Getting It Wrong
The Planning Fallacy persists because of a fundamental tension in how
human beings think about the future. When we plan, we focus on the
unique features of the specific task ahead. We think about what makes
this corrective action different, what makes this implementation
special, what makes this timeline achievable. We construct a best-case
scenario in our minds and then treat it as the most likely outcome.
Meanwhile, we ignore or minimize the statistical evidence from our
own history. The last three CAPA implementations each took four months
instead of the planned six weeks. The last equipment validation ran
three months over schedule. The last process change required twice as
many trials as anticipated. This information exists — it’s in project
records, in post-mortem documents, in the collective memory of everyone
who was there — but it doesn’t meaningfully influence the next plan.
Kahneman called this the difference between the “inside view” and the
“outside view.” The inside view focuses on the specifics of the current
project. The outside view asks: “How long do projects like this
typically take?” The inside view is vivid, detailed, and optimistic. The
outside view is statistical, boring, and almost always more accurate.
And in quality management, we almost never take the outside view.
The Anatomy of
an Unrealistic Quality Timeline
Consider a typical scenario. A customer audit finds a significant
nonconformance in your welding process. Your corrective action response
commits to: root cause analysis within one week, countermeasure
implementation within three weeks, and effectiveness verification within
six weeks. The customer accepts the plan. Your quality engineer begins
work with genuine confidence.
Here’s what actually happens. The root cause analysis reveals that
the problem isn’t just the welding parameters — it’s the fixture, the
material certification process, and the training of second-shift
operators. Each of these dimensions requires a separate investigation,
each involving different departments, each with its own scheduling
constraints. The one-week analysis takes four weeks because you can’t
get the metallurgy lab to prioritize your samples, the production
manager won’t release operators for interviews during peak season, and
the fixture designer is already committed to two other projects.
The countermeasure implementation timeline assumed that once you knew
the fix, you’d simply implement it. But the new fixture requires design
review, procurement lead time for modified components, a trial run that
reveals the need for further adjustment, and then another trial run that
conflicts with a production commitment. The three-week window stretches
to eight.
Effectiveness verification was supposed to confirm that the fix
worked. But the sample size you planned turns out to be inadequate for
statistical significance. The production schedule doesn’t allow enough
consecutive runs to accumulate the data. And just when you’re about to
declare success, a different defect mode appears — not the original
problem, but one that your fix inadvertently created.
The six-week CAPA takes five months. Nobody is surprised except the
people who wrote the plan.
The Hidden Costs of
Systematic Optimism
The Planning Fallacy doesn’t just create missed deadlines. It
generates a cascade of secondary problems that are often more damaging
than the delay itself.
Resource starvation. When one project runs over
timeline, it consumes resources that were allocated to other
initiatives. Your quality engineer spending five months on a CAPA that
was supposed to take six weeks means five months of delayed work on the
preventive maintenance optimization project, the supplier audit program,
and the SPC implementation on Line 3. One unrealistic timeline doesn’t
just delay one project — it creates a ripple effect across the entire
quality improvement portfolio.
Credibility erosion. Every missed deadline chips
away at the quality function’s credibility with operations, with
management, and with customers. After the third or fourth time a quality
initiative fails to deliver on schedule, the organization stops taking
quality timelines seriously. “Quality said it would be done by March”
becomes code for “maybe by June, maybe never.” Once this credibility is
lost, rebuilding it takes years — and in the meantime, quality’s ability
to drive organizational change is severely compromised.
Premature declarations of victory. One of the most
dangerous responses to timeline pressure is declaring success before the
evidence actually supports it. The effectiveness verification that
should have required 30 data points gets done with 12. The process
validation that needed three consecutive successful runs gets declared
complete after two. The corrective action that addresses the immediate
symptom gets closed without confirming that the root cause is truly
eliminated. The Planning Fallacy doesn’t just make us late — it makes us
dishonest about whether we’ve actually accomplished what we
promised.
Short-term fixes masquerading as solutions. Under
timeline pressure, organizations gravitate toward quick wins that look
impressive in progress reports but don’t address underlying causes. You
committed to a systematic process redesign, but the timeline is
slipping, so you implement a tighter inspection checkpoint instead. It
catches more defects — temporarily — but the root cause remains. Three
months later, the defect rate is back where it started, and the
inspection checkpoint has become a permanent bottleneck that everyone
resents.
Why Experience Doesn’t Help
One of the most puzzling aspects of the Planning Fallacy is that
experience doesn’t seem to cure it. Your quality manager has been
through a dozen CAPA implementations, and every single one ran over the
planned timeline. Yet when asked to estimate the next one, they produce
a timeline that assumes nothing will go wrong.
This happens because experience, counterintuitively, can make the
Planning Fallacy worse. Experienced planners have more detailed mental
models of how a project should unfold. These detailed models feel like
expertise, but they’re actually elaborate best-case scenarios. The more
detailed the plan, the more confident the planner feels — and the more
blindsided they are when reality deviates from the script.
There’s also a motivated reasoning component. Quality managers know
that realistic timelines are often unwelcome. The customer wants the
CAPA closed quickly. The plant manager wants the new system running
before the next audit. The VP wants to report progress at the quarterly
review. Producing a realistic timeline that says “this will take six
months” requires professional courage that not every quality
professional possesses, especially when they know the response will be
“make it faster.”
The Reference
Class: Your Most Powerful Tool
The single most effective antidote to the Planning Fallacy is the
reference class forecast — a concept that Kahneman championed and that
most quality organizations never use. The idea is simple: instead of
building a timeline from scratch for each new initiative, look at how
long similar initiatives actually took in the past, and use that
distribution as your starting point.
If your last five corrective actions for welding defects each took
between three and five months from initiation to verified closure, then
your base estimate for the next one should be three to five months — not
six weeks. If your last three equipment qualification projects each
required two to three rounds of testing, plan for two to three rounds.
If every SPC implementation you’ve ever done took between nine and
twelve months to reach sustainable maturity, don’t write a plan that
promises full deployment in six.
This sounds obvious. It is obvious. And almost no one does it,
because the reference class forecast is almost always less optimistic
than the plan that leadership wants to hear. Taking the outside view
requires you to start from a place that feels pessimistic, even though
it’s actually realistic. It requires you to tell the customer that their
corrective action will take four months, not six weeks. It requires you
to tell the plant manager that the new quality system won’t be running
before the next audit. These are uncomfortable conversations, and most
organizations structure their planning processes to avoid them.
Building
a Planning Fallacy-Resistant Quality Organization
Creating an organization that can plan realistically requires
structural changes, not just individual awareness. Here’s what that
looks like in practice.
Maintain a project duration database. Track the
planned versus actual duration of every quality initiative — corrective
actions, improvement projects, system implementations, audit responses,
equipment qualifications. Build a simple database that allows you to
look up: “For CAPA projects involving process changes, what is the
typical range of actual durations?” This becomes your reference class,
and it should be the starting point for every new plan.
Decouple planning from promising. In most
organizations, the planning process is conflated with the commitment
process. You write a plan and it immediately becomes a promise to a
customer, to management, or to an auditor. Separate these functions.
Plan first using reference class forecasting and realistic assumptions.
Then negotiate commitments based on the plan — with appropriate buffers
built in for the unknown unknowns that every project contains.
Build in explicit buffers — and protect them. The
difference between an experienced planner and a naive one is that the
experienced planner knows that unexpected problems will arise but
doesn’t know which specific problems they’ll be. Buffers aren’t padding
— they’re an honest acknowledgment of uncertainty. A quality
organization that builds 30-40% buffer into its timelines and then uses
that buffer for the inevitable complications will deliver on schedule
far more often than one that plans to the day and misses every
deadline.
Conduct pre-mortems. Before finalizing any quality
initiative timeline, gather the team and ask: “Imagine it’s six months
from now and this project has failed to meet its deadline. What went
wrong?” This exercise forces people to identify specific risks that
optimistic planning tends to overlook. The production manager will
mention the upcoming peak season. The engineer will mention the lead
time for that critical component. The quality manager will mention the
three other projects competing for the same resources. These aren’t
pessimism — they’re data, and they belong in the plan.
Track planning accuracy as a metric. If your quality
organization doesn’t measure how accurately it plans, it will never
improve at planning. Add a simple metric: the ratio of actual duration
to planned duration for completed projects. If that ratio is
consistently above 1.0 — and in most quality organizations, it’s between
1.5 and 3.0 — then your planning process is systematically biased, and
your timelines should be adjusted accordingly.
The Cultural Dimension
The Planning Fallacy thrives in organizational cultures that punish
realism and reward optimism. If the quality engineer who says “this will
realistically take four months” gets overruled while the one who says
“we can do it in six weeks” gets praised for their can-do attitude, then
every timeline will be a work of optimistic fiction.
Changing this requires leadership that values accuracy over
enthusiasm. It requires management that thanks the engineer who delivers
an uncomfortable but realistic estimate rather than rewarding the one
who tells them what they want to hear. It requires a culture where
saying “I don’t know yet, but based on past experience it could take X
to Y months” is seen as a sign of professional maturity, not a lack of
commitment.
This is hard. Most manufacturing cultures are biased toward action,
toward confidence, toward the appearance of control. Acknowledging
uncertainty feels like weakness. Admitting that a project might take
longer than hoped feels like failure. But the actual failure is not the
realistic estimate — it’s the unrealistic one that sets the organization
up for disappointment, erodes credibility, and ultimately delays the
quality improvements that everyone genuinely wants to achieve.
The Customer Conversation
Nowhere is the Planning Fallacy more damaging than in customer-facing
quality situations. When a customer requests a corrective action, they
want a fast response. The natural instinct is to promise a fast
response. But a promise you can’t keep is worse than an honest answer
the customer doesn’t want to hear.
A CAPA closed late is worse than a CAPA with a realistic timeline
from the start. Late closure suggests that your organization can’t
execute. A realistic timeline suggests that your organization plans
carefully and executes reliably. Customers — especially sophisticated
automotive and aerospace customers — understand this distinction better
than most quality professionals give them credit for.
The next time you’re tempted to promise a six-week corrective action,
ask yourself: in the entire history of this organization, has any
corrective action of comparable complexity ever been completed in six
weeks? If the honest answer is no, then the promised timeline isn’t a
plan — it’s a lie you’re telling yourself and your customer, and the
eventual correction will be far more painful than the honest estimate
would have been.
The Uncomfortable Truth
The Planning Fallacy isn’t really about planning. It’s about the
stories we tell ourselves about control, competence, and the future. We
believe that this time will be different because we want it to be
different. We believe that our detailed plans prove our competence when
they actually prove our optimism. And we keep making the same mistake
not because we’re stupid, but because the alternative — honest,
realistic planning that acknowledges uncertainty and history — requires
a kind of organizational courage that most quality cultures haven’t
built.
Your timelines aren’t too aggressive because you’re bad at
estimating. They’re too aggressive because your planning process is
designed to produce optimistic estimates rather than accurate ones. Fix
the process, not the people. Build the reference class database. Conduct
the pre-mortems. Track planning accuracy. Protect the buffers. And
slowly, project by project, your quality organization will learn to plan
in a way that actually reflects reality — which is the only planning
that can actually drive improvement.
The question isn’t whether you’ll fall prey to the Planning Fallacy.
You will. The question is whether you’ll build the systems to catch
yourself — or keep laminating timelines that were doomed before they
were printed.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality management, process
improvement, and organizational transformation. He has helped
organizations across automotive, aerospace, and industrial manufacturing
build quality systems that work in practice — not just on paper. His
writing focuses on the human and organizational factors that determine
whether quality tools deliver their promised value or become expensive
exercises in compliance theater.
