Quality
Triage: When Your Organization Has More Problems Than Resources — and
the Discipline of Deciding What to Fix First, What to Monitor, and What
to Accept Becomes Your Most Critical Quality Skill
The Night Everything Was on
Fire
It was a Tuesday in November when the quality manager at a mid-tier
automotive supplier in central Europe walked into a meeting that would
define the rest of his year. On the conference table sat four open
customer complaints, two pending audit findings, a supplier deviation
request that had been ignored for three weeks, and an internal scrap
rate that had crept from 1.2 percent to 3.8 percent over six months
without anyone triggering a formal response.
His team consisted of three quality engineers, one of whom was on
maternity leave, and a half-time quality technician who split his
attention between inspection and data entry. The plant manager wanted
all four customer complaints closed by Friday. The customer wanted an 8D
report within 48 hours. The auditor wanted evidence of corrective action
within 30 days. And the scrap rate was bleeding approximately €14,000
per week from margins that were already thin enough to read through.
He had twelve problems and resources for three.
This is not an unusual situation. This is the normal condition of
quality management in most manufacturing organizations. And the skill
that separates quality professionals who survive from those who drown is
not their ability to solve problems. It is their ability to decide which
problems to solve.
That skill has a name: quality triage.
Borrowed from the
Battlefield
The concept of triage was born in the blood and chaos of Napoleonic
battlefields. A French military surgeon named Dominique-Jean Larrey
faced an impossible reality: hundreds of wounded soldiers arriving
simultaneously, limited medical staff, and the knowledge that treating
everyone equally meant saving no one effectively. His solution was a
classification system that divided the wounded into three
categories:
Category One: Soldiers who would survive without
immediate treatment. Set them aside. They could wait.
Category Two: Soldiers who would survive if they
received immediate treatment. Focus resources here. This is where effort
saves lives.
Category Three: Soldiers who would not survive
regardless of treatment. Provide comfort, but do not expend scarce
surgical resources. This is the hardest decision, and the most necessary
one.
The genius of this system was not medical. It was rational. It
acknowledged scarcity as a permanent condition and built a decision
framework that maximized outcomes within that constraint.
Quality management faces the same battlefield, the same scarcity, and
the same need for ruthless prioritization. Most organizations just
refuse to admit it.
Why Quality
Triage Is Not Just Prioritization
Prioritization is a ranking. You list your problems from most
important to least important and work your way down the list until you
run out of time, money, or people. Prioritization assumes you will
eventually get to everything. It is optimistic by design.
Triage is a classification. You are not ranking problems. You are
categorizing them based on urgency, impact, and the probability that
your intervention will actually change the outcome. Triage assumes you
will not get to everything. It is realistic by
design.
The difference matters because prioritization without triage leads to
the most common dysfunction in quality organizations: the tyranny of the
squeaky wheel. Whoever complains loudest, whichever customer has the
most political capital, whichever auditor finding makes leadership most
uncomfortable — those problems get attention, regardless of whether they
are the problems most likely to cause real harm.
Quality triage replaces volume with criteria. It replaces political
pressure with systematic assessment. It gives you a defensible answer to
the hardest question in quality management: “Why are you working on
that problem and not this one?”
The Three Categories of
Quality Triage
Adapting Larrey’s framework to the quality domain gives us three
categories that should govern every resource allocation decision in your
quality organization.
Category One: Monitor and
Schedule
These are problems that are real but not urgent. They have not yet
crossed a threshold that demands immediate intervention. They may be
trending in the wrong direction, but the current impact is manageable
and the risk of sudden escalation is low.
Examples include: – A process parameter that is drifting toward a
control limit but remains within specification – A supplier whose
quality scorecard has declined slightly over two consecutive months – An
internal audit finding related to documentation practices that has no
direct product impact – A customer complaint about cosmetic appearance
that does not affect form, fit, or function
The correct action for Category One problems is to document
them, assign an owner, set a review date, and move on. You are
not ignoring them. You are scheduling them for attention when resources
become available or when the monitoring data tells you they have
escalated.
The trap most organizations fall into is treating Category One
problems as Category Two problems because someone important noticed
them. A CEO asking about a documentation finding does not transform that
finding into an urgent quality crisis. It transforms it into a
communication event. Respond with information, not with redirected
engineering resources.
Category Two: Act Immediately
These are problems where your intervention now will
produce a materially different outcome than your intervention
later. The cost of delay is quantifiable and
significant. The probability that your resources can actually resolve
the issue is high.
Examples include: – A customer line stoppage or field failure that
requires containment within hours – A process that has gone out of
statistical control and is producing nonconforming product – A
safety-related defect that could cause harm if it reaches the market – A
critical supplier failure that threatens your ability to ship product
this week
Category Two problems get your best people, your full attention, and
whatever resources they need. This is where quality earns its keep.
Every hour you spend here should produce a measurable reduction in risk
or cost.
The discipline required is not just in acting on Category Two
problems. It is in not acting on Category One or Category Three
problems when Category Two problems exist. This is the moment
where most quality organizations lose their way. A quality engineer
spends Monday on a Category Two customer complaint, Tuesday on a
Category One documentation finding because the plant manager asked about
it, Wednesday on a Category Three legacy issue that has been around for
three years, and by Thursday the customer complaint has escalated
because no one was driving containment.
Triage without discipline is just a fancy word for a list.
Category Three: Accept and
Contain
These are problems where your intervention, regardless of resources,
is unlikely to produce a different outcome. The problem may be too
deeply embedded in your process architecture. The cost of fixing it may
exceed the cost of living with it by an order of magnitude. The
technology to solve it may not exist at a price your organization can
afford.
This is the category that makes people uncomfortable, because it
sounds like giving up. It is not giving up. It is making a calculated
decision that some problems are not solvable within the current
constraints, and the honest thing to do is to acknowledge that, contain
the impact, and plan for a future state where the constraint no longer
exists.
Examples include: – A chronic defect mode in a legacy product line
that is scheduled for phase-out in 18 months – A measurement capability
issue where the gage R&R is marginal but the process tolerance
cannot be opened and a better measurement system costs more than the
defect it would catch – A supplier quality issue where the supplier is
the only source, their performance is unlikely to improve, and switching
suppliers would require recertification that takes longer than your
production commitment – A process variation that is inherent to the
current equipment design and cannot be eliminated without capital
investment that has been approved for next year’s budget
The correct action for Category Three problems is to
implement containment, document the business case for
acceptance, and build the resolution into a longer-term plan.
You are not pretending the problem does not exist. You are acknowledging
that solving it now, with current resources, would cause more harm than
it prevents.
The trap with Category Three is allowing it to become a dumping
ground for problems nobody wants to deal with. Every problem assigned to
Category Three should have a written justification that includes the
cost of the problem, the estimated cost of resolution, and the
conditions under which the categorization would be revisited. If you
cannot articulate why a problem belongs in Category Three, it probably
does not.
The Triage Board:
Making Decisions Visible
One of the most powerful tools for implementing quality triage is a
visual management board that makes the classification transparent to the
entire organization. Not a spreadsheet buried in someone’s laptop. A
physical or digital board that anyone can see, with three columns:
Monitor, Act, and Accept.
Every open quality issue appears on this board, classified into one
of the three categories, with an owner, a review date, and a brief
justification for the classification. The board is reviewed weekly by
the quality leadership team, and reclassification happens in real time
based on new data.
The board serves three critical functions:
First, it makes the triage decision visible. When
the plant manager asks why the quality team is working on Problem A
instead of Problem B, the answer is not a verbal explanation. It is a
gesture toward the board. Problem A is in the Act column because it
meets the criteria. Problem B is in the Monitor column because the data
does not yet support escalation. The board replaces opinion with
evidence.
Second, it prevents the natural migration of all
problems toward the Act column. Without a visible system, the default
behavior in any organization is to treat every problem as urgent.
Urgency is contagious. The triage board creates friction against that
contagion by requiring a justification for every classification.
Third, it creates a feedback loop. When a Category
One problem escalates to Category Two because it was monitored and the
data showed deterioration, that is the system working as designed. When
a Category Two problem resolves and moves to Category One for
monitoring, that is the system working as designed. When a Category
Three problem gets reclassified because the business case for acceptance
has changed, that is the system working as designed.
The board is not static. It is a living instrument that reflects the
current state of your quality reality.
The
Mathematical Foundation: Expected Loss Scoring
For organizations that want to move beyond qualitative triage, there
is a quantitative method that brings rigor to the classification
process. It is based on a concept called expected loss,
and it works like this.
Every quality problem has three attributes that can be estimated:
- Probability of escalation — What is the likelihood
that this problem gets worse if we do nothing? - Impact if it escalates — What is the cost
(financial, reputational, regulatory) if this problem reaches its
worst-case outcome? - Intervention effectiveness — What is the
probability that our available resources can actually resolve this
problem?
The expected loss score is calculated as:
Expected Loss = Probability of Escalation × Impact × (1 –
Intervention Effectiveness)
This score gives you a single number for each problem that captures
not just how bad the problem is, but how much your intervention is
likely to change the outcome. Problems with high expected loss scores
belong in Category Two. Problems with low scores belong in Category One.
Problems where intervention effectiveness is near zero belong in
Category Three regardless of the other factors.
The beauty of this approach is that it naturally surfaces the insight
that triage is trying to teach: the most important problems are not
always the ones you should work on. A catastrophic problem that you
cannot solve is less deserving of your immediate resources than a
moderate problem that you can solve quickly and decisively.
The Human
Element: Why Triage Requires Courage
The hardest part of quality triage is not the framework. It is the
conversations. Telling a plant manager that the problem he is worried
about is classified as “Monitor” requires a different kind of
professional courage than solving the problem itself. Telling a customer
that their complaint, while real, does not meet the threshold for
immediate containment requires a relationship built on trust and
transparency.
Telling your own team that the problem they have been working on for
three months is being reclassified as “Accept” requires an honesty that
most organizations struggle to sustain. It means admitting that the
resources were not sufficient, the approach was not right, or the
problem was more deeply rooted than anyone expected.
These conversations are the real practice of quality triage. The
framework is just the tool that gives you the language to have them.
Back to That Tuesday in
November
The quality manager in our opening story did not try to solve all
twelve problems simultaneously. He did not stay until midnight every
night for a week, burning out his already-depleted team. He did not tell
the plant manager that everything would be fixed by Friday.
Instead, he spent two hours with his two available engineers going
through every open issue and classifying it into one of three
categories. Two of the four customer complaints went into the Act column
— the ones with active containment risk. One customer complaint went to
Monitor — it was a chronic issue that had been occurring intermittently
for six months without escalation. One went to Accept — a cosmetic issue
on a low-volume part where the cost of resolution exceeded the annual
cost of complaints by a factor of four.
The two pending audit findings went to Monitor. The supplier
deviation went to Act because it was affecting incoming material quality
on a critical component. And the scrap rate went to Act because the
trend was accelerating and the weekly cost had crossed a threshold that
made it impossible to defer.
Then he walked into the plant manager’s office, pointed at the triage
board, and said: “Here is what we are working on this week. Here is why.
Here is what we are not working on, and here is the justification. If
you disagree with any classification, I would like to hear your argument
based on these criteria. But I need you to know that if we redirect
resources away from the three items in the Act column, the expected
outcome is measurable and predictable.”
The plant manager looked at the board for a long time. He asked one
question about the cosmetic issue that had been classified as Accept.
The quality manager walked him through the cost analysis. The plant
manager nodded.
They closed the three Act items by the following Tuesday. Not all of
them permanently — one required a longer-term corrective action plan.
But containment was in place, root cause analysis was underway, and no
defect was reaching a customer.
The Monitor items were reviewed the following Monday. One of them —
the chronic customer complaint — had produced a new occurrence over the
weekend. It was reclassified to Act.
The quality manager eventually got his third engineer back from
maternity leave. By that time, the triage board had become a permanent
fixture in the quality department’s weekly review. It was not perfect.
Classifications were sometimes wrong. Problems sometimes escalated
faster than the monitoring caught them. But the organization had a
framework for making decisions under scarcity, and that framework
produced better outcomes than the previous approach, which was to panic
about everything and resolve nothing.
The Triage Discipline
Quality triage is not a one-time exercise. It is a discipline — a
habit of thought that must be practiced every day, with every new piece
of data, every new complaint, every new audit finding. It requires three
things that most manufacturing organizations find difficult:
Honesty about scarcity. You do not have unlimited
resources. Neither does your team. Neither does your budget. Pretending
otherwise does not create more capacity. It just distributes your
existing capacity across too many problems to solve any of them
well.
Willingness to not act. Every quality professional
is wired to respond to every problem. It is the instinct that makes them
good at their job. But the discipline of triage requires the
counterintuitive skill of deliberate inaction — of watching a problem
that you know how to solve because solving it right now would mean not
solving a more important problem.
Transparency about decisions. When you classify a
problem as Monitor or Accept, you are making a decision that some
stakeholders will disagree with. The triage framework gives you the
structure to explain that decision in terms of criteria, not preference.
Use it.
The Bottom Line
Every manufacturing organization has more quality problems than it
has resources to solve them. This is not a failure of the quality
system. It is the permanent condition of manufacturing in a world of
increasing complexity, tightening specifications, and relentless cost
pressure.
The organizations that thrive in this environment are not the ones
that solve every problem. They are the ones that solve the
right problems at the right time with
the right resources — and have the discipline to let
the rest wait until the conditions for resolution actually exist.
Quality triage is the skill that makes this possible. It is not
glamorous. It will not make you popular with every stakeholder. But it
will make you effective, and in the long run, effectiveness is the only
metric that matters.
Peter Stasko is a Quality Architect with over 25 years of
experience in automotive and manufacturing quality management. He
specializes in building practical quality systems that work in the real
world — not just on paper. His approach combines deep technical
knowledge with the leadership skills needed to drive lasting improvement
across organizations of all sizes.
