Organisations face constant pressure to simplify, streamline, and cut costs. Lean manufacturing and continuous improvement methodologies demand the elimination of waste. But there is a critical difference between eliminating genuine waste and eliminating safeguards you simply do not recognise as safeguards. The first is operational improvement. The second is a latent failure waiting to happen.
I have audited plants where engineers removed inspection steps because they had not found a defect in three years. They did not realise the absence of defects was the direct result of that inspection step functioning correctly. I have watched managers delete process parameters from control plans because nobody could explain why they were there. The engineer who established those parameters had retired, taking the institutional memory with them.
When the institutional memory of why something exists is lost, the process step itself becomes vulnerable. It looks arbitrary, unnecessary, and like a prime candidate for removal. Because the organisation has no mechanism to recover the original engineering rationale, the removal proceeds without objection. This is Chesterton's Fence in action: tearing down a safeguard before understanding why it was built.
Systemic Pressures Behind the Removal
Understanding why organisations repeatedly fall into this trap requires examining the forces driving the behaviour. It is not carelessness. It is a confluence of systemic pressures and cognitive blind spots that make removing the safeguard feel not just reasonable, but necessary for operational efficiency.
Value stream maps drawn in conference rooms rarely capture the tacit knowledge embedded in a process step that an operator has performed for a decade. Continuous improvement philosophies carry an implicit assumption: that the people making changes can correctly distinguish between non-value-added waste and critical compensating controls. When a process step looks like waste but is actually a necessary safeguard, the improvement initiative actively degrades the system.
Modern quality systems compound this problem through metric-driven management. If an activity cannot be measured and linked to a key performance indicator, it gets questioned. But preventive safeguards do not catch defects; they stop them occurring. When a preventive step has worked effectively for years, the data shows nothing: no defects, no escapes, no customer complaints. This absence of evidence is routinely interpreted as evidence of absence.
Anatomy of an Unintentional Safeguard Removal
The pattern repeats across automotive, aerospace, and electronics manufacturing with alarming consistency. Someone notices a process step that seems redundant. It might be a secondary inspection, an additional torque verification, or a redundant cleaning operation. They ask around, but nobody can articulate why the step exists. The documentation is vague, and the operator performing the task simply says they have always done it that way.
The observation escalates into a data-backed proposal. The step is classified as non-value-added. A time study shows it adds forty-five seconds to cycle time. A cost analysis shows it consumes labour that could be redirected elsewhere. The step is removed, the line runs faster, and the metrics improve. The team celebrates a successful optimisation.
Then comes the latent period. For months, or even years, nothing visibly changes. The process continues producing conforming product. The organisation generalises the lesson: if this step could be removed without consequence, perhaps others can be too. But eventually, a supplier changes a raw material formulation, a machine ages past a maintenance threshold, or an environmental condition drifts. The latent variation the removed step was quietly absorbing now has nowhere to go. Defects appear, and root cause analysis traces the failure back to the step removed years prior.
The Breakdown of Institutional Memory
Every process in a manufacturing environment is the product of accumulated knowledge, lessons learned, and responses to specific historical failures. But this knowledge rarely survives personnel turnover, organisational restructuring, or the natural decay of documentation systems. The reasoning behind process steps exists primarily as tacit knowledge in the heads of experienced operators and engineers.
They know a specific temperature range matters because they remember the batch that failed when the oven drifted in 2014. They know a secondary visual inspection catches a defect mode the automated system misses because they personally found three units last quarter. This knowledge is not written down because it feels obvious to the people who hold it. When those people leave, the knowledge gap becomes visible, and the undocumented safeguard becomes the next target for removal.
Quality systems require documentation, but compliance documentation is not engineering analysis. A PFMEA lists a control, but rarely explains the historical reasoning behind it. Work instructions describe what to do, but not why. Experienced engineers and operators are retiring, and the new engineers inheriting these processes are expected to improve them. They cannot improve a system safely if they do not understand the functional purpose of its existing safeguards.
Identifying Genuine Safeguards in Your Process
Not every process step is a safeguard worth preserving. Distinguishing between genuine critical controls and actual waste requires examining the historical context of the step. Specific patterns should trigger heightened scrutiny before any removal is authorised. These patterns indicate a step was likely installed to mitigate a specific, documented failure mode.
Identifying Hidden Safeguards vs. True Waste
Characteristics of hidden safeguards
- Traced back to an 8D, customer complaint, or audit finding
- Redundant checks compensating for primary control failure rates
- No current process owner can articulate the original purpose
- High time/cost relative to the severity of the failure it prevents
Characteristics of true waste
- Created by legacy work practices with no failure mode linkage
- Duplicate data entry where the primary system captures all inputs
- Inspections for features that are no longer functionally required
- Steps where process capability (Cpk) has proven robust over years
If you can trace a process step back to a corrective action request, an internal rejection log, or a customer complaint, it is a safeguard. The fact that it has not caught a defect recently does not mean it is unnecessary. It may mean it is operating exactly as designed, keeping the process within acceptable variation.
Steps with no clear owner are the most dangerous to remove. If nobody in the organisation can explain why a step exists, that is not evidence the step is unnecessary. It is evidence the organisation has failed to document its engineering rationale. The cost of a process step should always be weighed against the cost of the failure it prevents, not against a quarterly budget target.
A Framework for Controlled Removal
Chesterton's principle dictates that the burden of proof must rest on the person proposing removal, not on the person defending the status quo. Before removing any process step, make a genuine effort to recover its rationale. Review historical PFMEA databases, search 8D corrective action logs, and interview experienced operators or retired engineers. The objective is to find the truth behind the control, not simply to justify cutting it.
If the engineering rationale cannot be fully recovered, apply a precautionary risk assessment. Map out the failure modes the step could be mitigating. Assess the severity and likelihood of those failure modes occurring under current process conditions. If you proceed with removal, treat it as a controlled experiment rather than a permanent, immediate line deletion.
The best quality engineers are slow to remove and quick to investigate. They treat every step as a safeguard until proven otherwise.
Process Step Removal Protocol
- 01Recover the rationaleCross-reference PFMEAs, 8D reports, and customer complaint archives for historical triggers.
- 02Apply risk assessmentConduct a formal gap analysis on potential unmitigated failure modes if the step is deleted.
- 03Run controlled trialSuspend the step temporarily while monitoring SPC data, Cpk stability, and near-miss reports.
- 04Document and finaliseUpdate the control plan with the removal justification, or retain the step and document exactly why it must stay.
Run a suspension trial for a defined review period, maintaining the step in the standard work but having operators bypass it under observation. Track process variation, capability indices, and near-miss reports closely. If nothing changes after the defined period, you have the data to support permanent removal. If variation increases, you have an early warning before the damage becomes an irreversible customer escape.
Engineering Discipline and System Humility
Complex manufacturing systems contain interdependencies that are not always visible on the shop floor or in the ERP. Actions have second-order and third-order effects. A parameter that seems arbitrary may be compensating for an upstream variation that is not actively monitored. A step that appears pointless in isolation may be critical for absorbing normal process drift.
Assuming we can look at a mature system, quickly identify what is unnecessary, and remove it without consequence is an assumption of omniscience. It assumes that if we do not understand the function of a process step, it must not have a purpose. Building quality systems that survive personnel turnover requires engineering discipline. It demands that we ask why a step exists before we ask whether we can eliminate it.
In a manufacturing environment where the cost of a single field failure or product recall can dwarf the savings from a hundred successful process optimisations, retaining undocumented safeguards is sound economics. The fence that looks pointless today may be the only structure standing between normal process variation and a catastrophic quality escape. Before you tear it down, ensure you know exactly what it was built to keep out.