Quality
and the Planning Fallacy: When Your Organization’s Quality Timelines Are
Always Wrong — and the Optimism Bias That Makes Every Improvement Take
Twice as Long as You Promised
The Timeline That Wasn’t
It was supposed to take six weeks.
The corrective action for the recurring defect in the injection
molding line had a clear plan. Identify root cause (one week), validate
the fix (two weeks), implement across all three shifts (one week), and
confirm effectiveness with 30 days of data (two weeks). The quality
manager presented it to the plant director with confidence. The customer
was waiting. The team nodded.
Twelve weeks later, they were still collecting data.
The root cause turned out to be more complex than anyone assumed. The
validation required tooling modifications that took three weeks to
procure. One shift resisted the new work instructions. And the
effectiveness data showed the defect rate dropping — but not enough to
meet the customer’s threshold, which meant starting the investigation
over with a new hypothesis.
Nobody was incompetent. Nobody was lazy. The timeline was simply
wrong — and it was wrong in exactly the same way the previous five
timelines had been wrong, for exactly the same reason that the next five
timelines would also be wrong.
This is the Planning Fallacy, and it is quietly destroying your
organization’s credibility, one missed deadline at a time.
What the Planning Fallacy
Actually Is
In 1977, psychologists Daniel Kahneman and Amos Tversky documented a
systematic bias in human forecasting: when people estimate how long a
task will take, they consistently underestimate. Not sometimes. Not
occasionally. Systematically. Predictably. Reliably.
The bias has two components. First, people plan in an “inside view” —
they imagine the best-case scenario where everything goes right, where
everyone is available, where materials arrive on time, where the
equipment works, where the customer doesn’t change their mind. Second,
they fail to consult the “outside view” — their own historical data
showing that similar projects consistently took 40% to 100% longer than
originally estimated.
Kahneman later admitted that he and Tversky themselves fell victim to
the same bias while writing the very textbook chapter about it. They
estimated one year. It took eight.
The Planning Fallacy is not about poor estimating skills. It is about
a fundamental cognitive architecture that makes optimism feel like
realism and makes historical evidence feel irrelevant to the current
situation.
Why Quality
Organizations Are Uniquely Vulnerable
Quality departments are especially susceptible to the Planning
Fallacy for several structural reasons.
Quality work depends on other people. A corrective
action isn’t something the quality team can execute alone. It requires
engineering to redesign, maintenance to modify tooling, production to
change procedures, and purchasing to source new materials. Every handoff
is a dependency, and every dependency is a potential delay. But when the
quality manager estimates the timeline, they estimate as if they control
all those resources. They don’t.
Quality improvements have uncertain endpoints.
Unlike building a wall, where you can see progress incrementally,
quality improvements often have binary outcomes. Either the defect rate
drops below the threshold or it doesn’t. You can be 90% of the way
through the timeline and 0% of the way to a solution. This makes
accurate estimation nearly impossible, but it doesn’t stop anyone from
trying.
Customer pressure compresses estimates. When a major
customer issues a corrective action request with a 60-day deadline, the
quality team doesn’t estimate how long the work will actually take. They
estimate how long they can afford to tell the customer it will take.
These are not the same number. The customer then builds their production
schedule around your optimistic timeline, and when you miss it, the
relationship damage compounds.
Past failures are explained away. When the previous
corrective action took twice as long as planned, the team doesn’t update
their estimating methodology. They explain it as exceptional: “The
supplier was late.” “We had a personnel change.” “The customer changed
the specification.” Each explanation is true. But they are always true.
The exceptions are the rule.
The Hidden Costs of Missed
Timelines
The Planning Fallacy isn’t just an inconvenience. It creates
cascading damage throughout the organization.
Destroyed credibility with customers. Every missed
deadline teaches the customer that your word is unreliable. After two or
three missed corrective action timelines, the customer stops believing
your commitments and starts managing you instead — more audits, more
status calls, more oversight. Each of these oversight activities
consumes resources that could have been spent on actual improvement,
creating a death spiral of increasing demands and decreasing
capacity.
Internal trust erosion. When the quality team
consistently misses its own timelines, other departments stop taking
quality commitments seriously. Engineering doesn’t rush to support the
corrective action because “they always extend the deadline anyway.”
Production doesn’t prioritize the new work instruction because “the
effective date always gets pushed back.” The self-fulfilling prophecy
completes the cycle.
Resource misallocation. When you believe a project
will take six weeks, you plan accordingly. You don’t staff for twelve.
You don’t buffer other projects. You don’t prepare contingency
resources. When week eight arrives and the project is still running, it
collides with the next project that was supposed to start in week seven.
Now you have two late projects instead of one.
Burnout and demoralization. The team working the
corrective action knows the timeline is unrealistic. They feel it in
their bones. But they’re held accountable to it anyway. The result is a
quality team that’s perpetually behind, perpetually apologizing, and
perpetually exhausted. This is how you lose your best quality engineers
— not to better pay, but to the feeling that success is structurally
impossible.
The
Reference Class: Your Most Powerful Corrective Tool
The antidote to the Planning Fallacy is deceptively simple: use the
outside view.
Kahneman calls it “reference class forecasting.” Instead of
estimating a project’s duration by imagining the steps involved, you
estimate by looking at how long similar projects actually took in the
past.
Here’s how it works in practice. Before you estimate the timeline for
a new corrective action, pull the records for your last ten corrective
actions. Calculate the actual duration of each one — from initiation to
confirmed effectiveness. Now calculate the ratio of actual time to
planned time. If your average ratio is 1.8, then your new estimate
should be 1.8 times whatever your inside-view estimate tells you.
If the inside view says six weeks, the reference class says
eleven.
This feels wrong. It feels defeatist. It feels like padding. It is
none of those things. It is evidence-based estimating. You are not
predicting failure — you are accounting for the reality that your
process has a predictable pattern of delays, and that pattern will apply
to this project just as it applied to the last ten.
Most organizations resist this. The number feels too high. The
customer won’t accept it. Management won’t approve it. But here is the
paradox: the customer would rather receive an honest twelve-week
estimate that you meet than a dishonest six-week estimate that you miss.
The first builds trust. The second destroys it.
Practical Strategies
for Beating the Bias
Beyond reference class forecasting, several practical approaches can
help quality organizations neutralize the Planning Fallacy.
Decompose ruthlessly. The larger the task, the worse
the estimate. Break every corrective action into its smallest component
activities, estimate each one individually, and then add them up. This
doesn’t eliminate the bias, but it reduces it — because we tend to be
more accurate when estimating small, concrete tasks than large, abstract
projects.
Add explicit buffers for dependencies. Every handoff
to another department should come with a built-in buffer. If engineering
says they can redesign the fixture in five days, plan for eight. This
isn’t distrust — it’s acknowledgment that engineering has their own
priorities, their own interruptions, and their own planning fallacy.
Track and publish your accuracy. Post a chart in the
quality department showing planned versus actual timelines for every
major project. Make the gap visible. Make it undeniable. The data is the
argument you can’t lose. Over time, this transparency creates
organizational pressure to estimate more honestly.
Separate estimation from aspiration. When the plant
director asks how long the corrective action will take, they often
aren’t really asking for an estimate. They’re asking for a commitment
that will satisfy the customer. These are different questions, and they
deserve different answers. “Our best estimate, based on historical data,
is twelve weeks. We will attempt to deliver in eight. I recommend
telling the customer ten.” This three-number approach preserves both
honesty and ambition.
Use pre-mortems. Before finalizing any timeline,
gather the team and ask: “Imagine it is six months from now and this
project is three months late. What went wrong?” The answers will
illuminate the risks that your optimistic inside view filtered out.
Factor those risks into the timeline.
Build portfolio awareness. If your quality team is
working on seven corrective actions simultaneously, the eighth one will
not proceed at the same speed as the first one did when the team had
nothing else on its plate. Capacity is finite. Timeline estimates that
ignore the rest of the portfolio are fiction.
The Leadership Challenge
The hardest part of fighting the Planning Fallacy isn’t the
methodology. It’s the organizational culture.
In many organizations, the person who provides the most aggressive
timeline is rewarded — not because their estimate is better, but because
it sounds more decisive, more confident, more “can-do.” The cautious
estimator who references historical data is seen as negative, as not
being a team player, as not having the right attitude.
This is exactly backwards.
The leader who asks for aggressive timelines and then accepts missed
deadlines is not driving performance. They are institutionalizing
failure. They are teaching the organization that commitments are
performative — that saying “six weeks” is more important than delivering
in six weeks.
The most effective quality leaders I’ve worked with share a common
trait: they would rather disappoint you with an honest timeline upfront
than disappoint you with a missed deadline later. They understand that
credibility is the quality department’s most valuable asset — more
valuable than any tool, any methodology, any certification.
You can lose a corrective action and recover. You can miss a
specification and negotiate. But once your customers and your colleagues
stop believing your timelines, everything becomes harder. Every request
for resources becomes a negotiation. Every commitment becomes
conditional. Every project starts with a deficit of trust that must be
earned back before real work can begin.
The Deeper Pattern
The Planning Fallacy in quality organizations is usually a symptom of
something larger: a culture that rewards optimism over accuracy,
confidence over competence, and speed over sustainability.
It shows up everywhere. In project timelines that are always wrong.
In quality objectives that are always aspirational. In improvement
targets that are always round numbers chosen for their rhetorical appeal
rather than their achievability. In corrective actions that are always
“in progress” because they were never given enough time to reach
“complete.”
The organizations that have broken this pattern share a few
characteristics. They track their estimating accuracy religiously. They
reward honest forecasting over aggressive promising. They treat a missed
deadline as a systemic failure, not an individual one. And they build
their plans around what historically happens, not what they wish would
happen.
This is not pessimism. It is realism. And in quality management,
realism is a competitive advantage.
What I’ve Learned
After twenty-five years of quality transformations across automotive,
aerospace, and pharmaceutical manufacturing, I’ve stopped counting the
number of times a “six-week project” became a six-month ordeal. What
I’ve learned is that the timeline itself is rarely the problem. The
problem is the cognitive bias that makes the six-week estimate feel
reasonable when every data point in your history tells you it isn’t.
The Planning Fallacy doesn’t mean your team is weak or your process
is broken. It means your team is human. Humans are wired for optimistic
forecasting. The question is whether your organization has the
discipline to compensate for that wiring — or whether it will keep
betting on the optimistic timeline and losing, over and over, until the
credibility runs out.
The best quality organizations don’t ban optimism. They contain it.
They let it drive ambition while using evidence to set expectations.
They tell the truth about how long things take, and then they work like
hell to beat their own estimates.
That’s not compromise. That’s mastery.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has led quality system
implementations, coached leadership teams through cultural
transformations, and helped organizations move from reactive
firefighting to proactive quality management. His approach combines deep
technical expertise in quality tools and methodologies with an
understanding of the human and organizational factors that determine
whether quality systems succeed or become expensive bureaucracy.
