I have stood in a war room at eleven at night, customer containment taped to the wall, three shifts' worth of suspect parts on quarantine pallets, a phone ringing every forty minutes. I have also stood in front of an executive committee with nothing to report. Only one of those meetings produced a budget increase.

Every few months a retrospective on Lululemon's see-through pants recall does the rounds, and the takeaway is always some version of the fix nobody applauded. That is the entire economics of quality in four words. Escapes generate headlines, war rooms, task forces and money. Prevention generates absence – and absence, in a budget review, looks identical to waste. The containment gets funded; the prevention gets cut, usually the year after it works. The same news cycle carries Stellantis insisting, again, that it is addressing its quality woes, and a revised ISO 9001 that promises an even stronger prevention orientation. Standards can mandate the discipline. Nothing in them forces anyone to pay for it.

The quarter nothing happened

At SNOP I ran quality, health and safety at a greenfield plant of more than 900 people and built the QA/QC function from a bare floor upwards, with PFMEAs written before the first serial part ran. The strongest quarter of my tenure produced one specific, verifiable result: zero critical customer escalations.

Not one 8D request. No sorting mission at a customer, no Sunday call about a pallet that left us wrong.

How does that read upstairs? As an empty inbox. Nobody applauds the phone call that doesn't come. The customer quality manager who used to ring weekly simply stopped ringing, and within a month the silence was read as spare capacity – as if the department that produced it no longer needed what it had. A quiet customer is not a compliment in a budget cycle. It is a vacuum, and finance fills a vacuum with a headcount.

What a non-event costs and saves

The same work shows up twice in a career: once as silence, once as a number that has to fight for itself. At Witte Automotive the number was the point. QRQC on the shop floor within the hour of detection. A3 for the systemic causes. A Q-Wall so a solved problem stayed solved. Scrap, rework, sorting, premium freight, customer debits – the failure-cost line came down substantially, and it came down as a lower line on the P&L, never as a headline above it. At SNOP the maths was starker: a 70% cut in defect costs at a plant that had started with nothing.

Here is the accounting problem. A contained escape gets costed precisely because it leaves a paper trail: sorter hours, freight bills, debits. A prevented escape leaves nothing. Its saving arrives as the absence of a cost that never appears, and the P&L quietly re-baselines it away. My 70% was real euros, but a finance director could argue volume, or mix, or new tooling – prevention has no receipt with which to defend itself. Containment walks into the budget meeting with documents. Prevention walks in with a counterfactual.

Containment is a story. Prevention is a silence. Organisations fund stories.

Making quiet work legible

This is not a communications problem, and I distrust anyone who solves it with a newsletter. It is a leadership discipline with mechanics:

  • Baseline the escapes that didn't happen. Last year's escape rate, this year's volume, fully loaded cost per escape – sorting, freight, containment labour, the debit – published with its assumptions visible, so finance attacks the number in the open instead of the corridor. A number that survives an argument survives a budget round.
  • Close prevention like an 8D. A prevented failure is not finished until the barrier has an owner, a due date, verified effectiveness and a signed closure. If you would not close a customer escape without verifying effect, do not close a countermeasure without it. An open register of non-events, run with 8D discipline, is the only artefact absence can produce.
  • Put the recall you didn't have on one slide, in euros. Three numbers: counterfactual cost, cost of the prevention system, delta. If the delta is not clearly positive, your prevention is theatre – better to learn that from your own slide than from an escape.

Nobody knows your name

The reward for good quality is that nobody knows your name. No customer remembers the plant that never shipped them rubbish; no board remembers the quarter without an escalation. The Lululemon piece gets shared precisely because somebody, a decade on, bothered to reconstruct what the fix cost and what it prevented – the legibility work nobody did at the time. That is rare enough to count as news.

So the goal cannot be applause. Applause is for containments, and containments are the invoice for prevention nobody funded. The goal is that the budget knows your name – through baselined counterfactuals, closed non-events and one honest slide of euros – so the silence you engineered gets renewed for another year instead of cut because nothing appeared to be happening.

Key takeaways

  • Prevention is invisible on the P&L by construction: prevented failures carry no invoice, so their savings register as baseline drift rather than results.
  • Publish a counterfactual early – last year's escape rate, this year's volume, fully loaded cost per escape – with assumptions exposed, before finance writes its own version.
  • Run non-events with 8D discipline: owners, dates, verified effectiveness, signed closure. Absence needs artefacts.
  • Report prevention as one slide in euros – counterfactual cost, system cost, delta – and treat a negative delta as a finding about your own system, not a reason to hide the slide.

Escapes are visible; that is their entire business model. They photograph well, they escalate fast, and they fill a room with people who can find money in an afternoon. Prevention has no such advantages. Its only currency is legibility, and legibility is built in baselines, closures and euros months before the budget round, never during it. The failure will always be visible. Leadership's job is to make the prevention visible too, in the only language a budget understands.