The corrective action was supposed to take six weeks. The team had a Gantt chart. Management had a deadline. Twelve weeks later, you were still arguing about the root cause during the 8D investigation.
This is the planning fallacy at work. First identified by psychologists Daniel Kahneman and Amos Tversky, it describes our systematic tendency to underestimate the time, cost, and risks of future actions, even when we have direct experience with similar projects running over budget and past deadline.
In quality management, this cognitive bias is devastating. You have run dozens of CAPA projects. You have watched process validations consume three times the allocated budget. Yet when the next audit finding arrives, the quality engineer looks at the calendar and assumes this specific closure will be simple. It never is.
The Inside View versus the Outside View
The planning fallacy operates through two cognitive traps. The first is inside-the-box thinking. When you plan, you construct a best-case scenario. You assume approvals arrive on time, MSA equipment is available, and production operators are free for training. You do not deliberately ignore risks; your brain simply fails to generate them during the scheduling phase.
The second trap is outside-view blindness. You have access to historical data, yet you treat each new project as unique. You focus on the specifics of updating an FMEA rather than looking at the base rate of all your previous FMEA updates. This distinction between the inside view and the outside view determines timeline accuracy.
In a manufacturing environment, the inside view sounds like this: This FMEA update only covers two failure modes, and the team knows the process well, so we can finish it by Friday. The outside view sounds like this: The last four FMEA updates averaged three weeks each, and every single one was initially scheduled for Friday.
One of these predictions is dramatically more accurate. It is the one your project schedule and customer commitment letters are never built on.
Where Time Estimates Collapse Fastest
Not all quality activities are equally vulnerable. The planning fallacy feeds on novelty, complexity, and interdependence. The more a project depends on cross-functional teams, other departments, or supplier cooperation, the worse the time estimate will be.
CAPA and 8D investigations are prime targets. You start with a straightforward defect and simple containment. Root cause analysis then reveals a systemic failure. The corrective action that was supposed to be a procedure update becomes a capital equipment project, and your six-week timeline becomes six months.
Process validation suffers similarly. IQ, OQ, and PQ protocols look linear on paper. In reality, each phase depends on the previous one's success. A single out-of-specification result during OQ adds weeks while you investigate the deviation, correct it, and repeat the run. You scheduled the best case; validation delivers the real case.
Supplier quality improvement introduces a compounded risk. You are not just managing your own planning fallacy; you are inheriting your supplier's. They promise a corrective action in 30 days. Their internal engineering approval process alone takes 45 days, and they have not started the actual rework.
Anatomy of an Overdue Audit Remediation
A customer audit identifies a gap in your control plan. The finding is legitimate but not catastrophic. Your quality engineer estimates two weeks to close it: update the control plan, revise the work instruction, train the operators, and upload evidence. The customer accepts the commitment.
Week one: The engineer starts updating the control plan and discovers the current revision was never fully implemented. The documented process and the actual production floor process have diverged. You now have two problems: the customer's finding and an internal nonconformance.
Week two: The control plan update requires input from process engineering, who are tied up with a new product launch. The engineer waits three days for a review meeting. The work instruction revision reveals that the specification it references was updated six months ago without triggering a document change.
Weeks three through six: Approvals stall while managers travel. Training schedules slip around shift patterns and absences. The customer finally receives the evidence package and asks for competency verification, not just attendance records. Nobody planned for that.
The Audit Remediation Cascade
- 01DiscoveryDocumented process and actual floor practice have diverged.
- 02Input BottleneckProcess engineering is unavailable due to a product launch.
- 03Specification DriftReferenced standards were updated without document control.
- 04Approval DelayManagement review stalls while key personnel travel.
- 05Evidence RejectionCustomer demands competency verification beyond attendance.
The Reference Class Forecast
The most powerful countermeasure to the planning fallacy is the reference class forecast. Kahneman's method forces you to bypass the inside view and anchor your estimates to historical reality rather than optimistic projections.
First, identify the reference class. What category does this project belong to? Not this specific CAPA, but all CAPA projects executed in the last two years. Second, gather the distribution. Look at the actual duration of projects in this class, not the planned duration. What was the fastest? The slowest? The median?
Third, use the base rate as your starting prediction. If your last ten CAPA projects took between four and fourteen weeks with a median of eight, your starting estimate is eight weeks, regardless of how simple the current failure mode looks. Finally, adjust for specific factors only after anchoring to the base rate.
It feels like sandbagging, but it is not pessimism. It is empiricism. You are replacing your gut feeling with data from your own history.
Several practical techniques help quality teams operationalise this. Three-point estimation uses the PERT formula, combining optimistic, most likely, and pessimistic durations into a weighted average. The buffer rule dictates multiplying initial estimates by 1.5 for multi-department projects and 2.0 for supplier interventions.
Organisational Amplification of the Bias
The planning fallacy is not just an individual cognitive quirk. It has an organisational amplification mechanism that makes it worse in companies than in isolated individuals. When management sets the timeline before the technical team estimates the work, the estimate becomes a negotiation rather than a prediction.
The quality engineer who knows the CAPA will take eight weeks learns to say four, because that is what the vice president wants to hear. The planning fallacy meets executive optimism, and the result is a timeline that bears no resemblance to reality. Once that timeline is committed to a customer, it becomes psychologically sticky.
When the project starts running late, the team does not revise the timeline; they work harder. Overtime increases. Corners get cut. You implement the corrective action faster but less thoroughly, the defect recurs, and you are back at the 8D table. Organisations explain each overrun with project-specific excuses instead of looking at the pattern.
How Organisations Entrench Optimism Bias
- Executive PressureDeadlines dictated before technical teams assess the actual work scope.
- Artificial NegotiationEngineers under-quote timelines to match what leadership wants to hear.
- Commitment StickinessPromised customer dates prevent honest timeline revision when obstacles appear.
- Corner-CuttingTeams compensate by rushing implementation, degrading the corrective action quality.
- Pattern BlindnessOverruns blamed on unique factors rather than systematic estimation failure.
Breaking the Optimism Cycle
If you lead a quality function, breaking this cycle starts with data. Track planned versus actual duration for every quality project, not just the major ones. Build a simple database and review it quarterly. The data is useless if it lives in someone's email; it needs to be on a shared dashboard.
Institute a base rate check in every project planning meeting. Before anyone proposes a timeline, present the historical data for similar projects. Let the actual duration of your last five FMEA updates sit in the room before anyone suggests this one will be different.
Separate estimation from negotiation. The technical team estimates the work based on the reference class. Management prioritises and resources it. These are different conversations. When you combine them, the estimate always bends toward what management wants to hear.
Finally, celebrate accurate estimates over fast ones. If a quality engineer estimates eight weeks and delivers in eight, that is a win. If they estimate four and deliver in six, that is a fifty percent estimation error that your customer had to absorb. The organisations that plan honestly finish faster because they allocate the right resources from the start.