Business

What Is Your Quality Failure Costing You, and Can Finance Produce the Number?

Quality sits in operations and its cost sits nowhere. Until finance can produce the number, prevention will always lose the argument to correction.

Kevin Jogin · 28 Aug 2026 · 11 min read

Ask your chief financial officer what poor quality cost the enterprise last year. If the answer takes more than a week to assemble, you have found the reason prevention keeps losing to correction.

Most large organisations can tell you their warranty provision, their scrap rate and their on-time-in-full performance. Very few can tell you what quality failure cost them in total, and almost none can tell you what it cost by cause. The number is not hidden. It is distributed — sitting in a dozen accounts that were designed to answer other questions, under headings like rework, expedited freight, customer credits, engineering change, inspection labour and, most expensively, the revenue that never arrived because a customer quietly reduced their forecast.

This is not an accounting curiosity. It is the mechanism by which quality investment loses every budget round it enters. A prevention proposal arrives with a cost that is visible, specific and attributable to a cost centre. The failures it would avoid are invisible, diffuse and attributable to nobody. The proposal is competing against an alternative whose cost has been made structurally unmeasurable, and it loses on the evidence — not because the evidence is against it, but because there is none.

The Strategic Context

Quality is unusual among operational disciplines in that its economics run backwards from managerial intuition. In most activities, doing more costs more. In quality, the cost curve is dominated by what happens when you do less: the expense of a defect rises steeply the further it travels from the point at which it was created.

A specification error caught in design costs an engineer's afternoon. The same error caught at first article costs a tooling change. Caught in production it costs scrap, rework and schedule. Caught at the customer it costs replacement, freight, investigation, credit, and a conversation about whether the relationship continues. Caught in the field, in a regulated or safety-critical context, it costs all of that plus a recall, a regulator, and a permanent change in how the organisation is perceived by people who will never read the technical explanation.

Each boundary the defect crosses adds a new class of cost, and the later classes are the ones the ledger is least equipped to attribute to a cause.

Philip B. Crosby made the argument that quality is free — that prevention pays for itself out of the failures it avoids, and that the apparent cost of quality is really the cost of not having it [SOURCE DETAILS REQUIRED]. The argument has been available for decades and adopted far less widely than its acceptance would suggest. The reason is structural rather than intellectual: the saving is real but unbooked, and organisations act on booked numbers.

What Leaders Commonly Misread

Quality is treated as a department rather than a distributed obligation. Where an organisation has a quality function, the rest of it infers that quality is that function's problem. Inspection then becomes the control — the weakest one available, since it detects defects only after the resources to create them have been consumed, and detects them imperfectly.

Prevention is scored as cost and failure as noise. Prevention spending appears in a budget line where it can be cut; failure cost appears across many lines where it cannot be seen. The asymmetry is not a judgement about priorities but an artefact of the chart of accounts, and it biases the enterprise toward correction.

Quality is confused with grade. An expensive product that fails to do what the customer required is a quality failure. A modest product that does exactly what was required, reliably, is a quality success. Conflating quality with cost, finish or specification level leads organisations to invest in features while the conformance problem — the gap between what was promised and what was delivered — goes unaddressed.

Method names substitute for method. This is the hardest misreading to detect from outside. Executives repeat the vocabulary of quality improvement without the substance, and the vocabulary is frequently wrong.

Reframing the Issue

The useful reframe is this: the cost of poor quality is not an operational metric. It is a capital-allocation number that the enterprise has chosen not to compute.

That changes who owns the problem. As an operational metric, quality performance belongs to operations and competes for attention with throughput and schedule. As a capital-allocation number, it belongs to the board, because it is the return available on a class of investment nobody is currently able to size. Prevention spending is then not an operational preference but an investment whose return the enterprise has declined to measure.

The Vocabulary Problem, Stated Plainly

Three errors recur often enough to be worth correcting directly, because acting on any of them will make a quality programme worse.

Six Sigma is not "more checkpoints". It is a disciplined method for reducing variation in a process toward a very low defect rate, structured around a defined improvement cycle and resting on statistical analysis of process capability [FACT CHECK REQUIRED]. Adding inspection points is close to the opposite of what it prescribes: inspection detects variation that the method exists to eliminate at source. An organisation that installs more gates and calls it Six Sigma has bought the cost of the gates and none of the benefit.

Error-proofing is not an alarm. Shigeo Shingo's contribution — commonly known by its Japanese name — includes two distinct classes of device [SOURCE DETAILS REQUIRED]. A warning device tells the operator that something is wrong. A control device makes the wrong action physically impossible: the connector only fits one way, the fixture will not close unless the part is seated, the next step will not initiate until the previous one is confirmed. The control class is the more powerful and the one most often omitted when the concept is summarised for management. An organisation that has implemented warnings has implemented the weaker half.

Total productive maintenance, total quality management, statistical variation reduction and error-proofing are not four interchangeable tools. They operate at different levels. One is a management philosophy about where quality responsibility sits. One is an equipment-effectiveness system. One is a variation-reduction methodology with its own analytical apparatus. One is a device-level design technique. Presenting them as a menu of evaluation options — pick two — produces programmes that are busy and incoherent.

Precision here is not pedantry. A quality initiative described in wrong terms will be resourced in wrong proportions.

Why the Number Cannot Be Produced

Cost accounting systems are built to answer two questions: what did we spend, and against which budget. They are not built to answer: what did this defect cost us across every account it touched. A single field failure typically generates a replacement unit, a freight charge, an investigation, a credit note, rework of a batch, an expediting cost and occasionally a legal provision — across seven ledger accounts. Each entry is correctly booked. None carries a code linking it to the others.

The enterprise therefore knows its total spending in each category and can decompose none of it by cause. It observes that expedited freight rose; it cannot say what share of that was one supplier's dimensional variation.

This is solvable, and solving it is a governance decision rather than a systems project: give a defect an identifier at the point of detection, and require every downstream cost to carry it. Most enterprise systems can support this and most do not, because nobody has asked — and nobody has asked because the request must come from finance on behalf of an argument operations has never been able to make with numbers. [Related article: Do You Know Your Suppliers' Costs, or Only What They Charge You?] describes the same structural blindness one level further out in the chain.

Where the Cost Actually Sits

Four categories, in ascending order of both magnitude and difficulty of measurement:

Prevention — design review, capability studies, supplier development, training, error-proofing devices. Fully visible. Usually the smallest number and always the easiest to cut.

Appraisal — inspection, test, audit, gauge calibration. Visible, and frequently the category that expands when prevention is cut, because a poorly controlled process needs more checking.

Internal failure — scrap, rework, retest, downgrade, schedule disruption. Partially visible. Systematically understated, because rework absorbed within a shift's normal hours often leaves no trace.

External failure — warranty, credits, replacement, investigation, recall, and the two costs nobody books: the revenue lost when a customer reduces share of wallet without complaint, and the management attention consumed by the incident. This is almost always the largest category and almost always the least measured.

The ratio between these four is more informative than any of them individually.

Suppliers, and the Cost of Not Refusing

Where a defect enters through a supplier, the enterprise carries the downstream cost and the supplier does not. This asymmetry is the single largest driver of tolerated poor quality in multi-tier operations, and it persists because refusing a delivery has an immediate, visible cost — a line stops — while accepting it has a distributed, invisible one.

The correction is not primarily contractual. It is the decision to refuse, consistently, from a position where the enterprise can afford to — which requires a supplier quality standard specific enough to enforce without argument, and enough qualified alternative supply that refusal is credible.

Where an organisation has neither, its stated quality standard is aspirational, and its suppliers know it. [Related article: Is Your Make-or-Buy a Cost Decision or a Capability Decision?] deals with when the enterprise should hold the activity itself, and a chronic inability to enforce a quality standard externally is a legitimate input to that decision.

Decision Framework

Establish the number before designing the programme. Commission a bounded exercise — one product family, one quarter — that traces every cost generated by defects in that scope, across all accounts, to an identified cause. Do not attempt the whole enterprise. The purpose is to establish the shape of the cost, not a comprehensive figure.

Test the ratio. Express the result across the four categories. Where appraisal exceeds prevention by a wide margin, the organisation is paying to find defects it is not paying to avoid.

Apply the escalation test to each significant defect class. For each, ask: at which point in the process could this have been detected, and at which point could it have been made impossible? The gap between the two is the prevention opportunity, and the cost difference between those points is what it is worth.

Choose control over warning wherever the geometry allows. For every recurring human-error defect, ask whether the process can be designed so the error cannot occur, before asking whether the operator can be alerted or retrained. Training decays; geometry does not.

Set a single accountable owner for the total number. Not for quality — for the cost of quality. Where the number has no owner it will not be produced.

From Strategy to Execution

Immediately. Ask the finance function for the cost of poor quality for one product family for one quarter, decomposed by cause. Treat the difficulty of the answer as the finding.

Over the medium term. Introduce defect identifiers that persist across systems so downstream costs can be attributed to originating causes. Build supplier quality standards that are specific enough to enforce, and qualify enough alternative supply that enforcement is credible. Shift a defined proportion of appraisal spending to prevention and measure what happens to internal failure over two cycles.

Over the longer term. Move quality from a functional responsibility to a design property. The most durable improvements come from decisions taken in design — tolerances, part geometry, capability requirements — a stage at which the quality function frequently has no authority. Changing that is an operating-model decision, not a quality initiative.

Signals to Monitor

  • Appraisal cost rising while volume is flat. Process control is deteriorating and inspection is absorbing the difference.
  • Rework absorbed within normal hours rather than reported. This is the clearest sign the true internal failure cost is understated.
  • Customers reducing volume without complaining. The most expensive external failure category and the one with no ledger entry.
  • A rising proportion of engineering change originating from production rather than from product improvement.
  • Supplier non-conformances accepted under concession more than occasionally. Each concession is a decision that the enterprise will carry the cost.
  • Quality performance reported as a rate rather than a cost in board papers. Rates make the trend visible and the consequence invisible.

Questions for the Leadership Team

  1. What did poor quality cost this enterprise last year, in total, and how long would it take our finance function to produce that number?
  2. What is our ratio of prevention to appraisal spending, and what does it say about where we believe quality comes from?
  3. For our three most frequent defect classes, at what point could each have been made physically impossible rather than merely detectable?
  4. When did we last refuse a supplier delivery on quality grounds — and if the answer is "rarely", is that because our suppliers are excellent or because refusal is not credible?
  5. Who owns the cost-of-quality number in this organisation, and does that person have the authority to act on it?
  6. How much of what we describe as a quality programme would survive an examination of whether we are using the methods we name correctly?

Closing Perspective

Quality failure is expensive in a way that is designed to be invisible: distributed across accounts built to answer other questions, at magnitudes that dwarf the prevention spending it displaces. This is why exhortation does not work. The organisation behaves rationally on the information it has, and that information is incomplete in a direction which consistently favours doing nothing.

The intervention that changes this is not a campaign. It is a number, owned by someone, produced regularly enough that prevention arguments can be made on the same evidentiary footing as the proposals they compete with. Everything else — the methods, the culture, the training, the supplier standards — follows the number or fails without it. The same asymmetry between visible cost and invisible consequence appears wherever an enterprise automates a decision it used to make by hand, and it is examined there in [Related article: Why One Machine Failure Costs More Than a Thousand Human Ones].

Until finance can answer the question, quality is an opinion competing against a budget line. After it can, it is a return on capital.


About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.