Quality
and the Art of Problem Framing: When Your Organization Solves the Wrong
Problem Brilliantly — and the Most Expensive Quality Failures Begin With
the Wrong Question
Peter Stasko
The Solution That Wasn’t
In 2019, a Tier 1 automotive supplier in Slovakia faced a crisis.
Their customer, a major German OEM, had issued a formal complaint: the
surface finish on a critical interior trim component was failing visual
inspection at final assembly. Scratches, swirl marks, and
micro-abrasions were appearing on parts that had passed every in-process
check with flying colors.
The supplier responded the way most organizations do — with
overwhelming force. They assembled a cross-functional team. They
commissioned a new automated inspection system with high-resolution
cameras and AI-based defect detection. They retrained every operator on
the line. They tightened their acceptance criteria. They spent €340,000
and three months implementing what their 8D report called a “robust,
sustainable corrective action.”
The defect rate dropped to zero. The customer was satisfied. The team
celebrated.
Six months later, the defects returned — worse than before. Not
because the corrective action had failed, but because the corrective
action had solved the wrong problem. The surface finish defects were
never caused by the manufacturing process. They were caused by the
packaging. The parts were vibrating against each other during
truck transport on the 900-kilometer journey from Slovakia to the German
assembly plant. The new inspection system was catching defects that
hadn’t existed when the parts left the factory — they were being
created in transit.
The supplier had spent €340,000 solving a manufacturing problem when
the real problem was logistical. They had answered the wrong question
with spectacular precision.
This is not a rare story. It is the most common story in quality.
The Frame Is the Fate
Every quality investigation begins with a question. And the question
you ask determines the answer you find — not because the data is wrong,
but because your framing determines which data you look at, which
variables you consider, and which solutions you imagine.
This is the art of problem framing, and it is the single most
underappreciated skill in quality management.
Consider how differently these questions shape an investigation:
-
“Why are our operators making defects?” — This
frame directs you toward human error, retraining, discipline, and work
instructions. It assumes the person is the problem. -
“Why is our process producing defects?” — This
frame directs you toward machine capability, material variation,
environmental factors, and process parameters. It assumes the system is
the problem. -
“Why are defects appearing at the customer but not in our
plant?” — This frame directs you toward the entire value stream
— including storage, transport, handling, and timing. It assumes the
problem may not be where you think it is.
All three questions are reasonable. All three will produce data. All
three will lead to corrective actions. But only one of them was going to
find the packaging vibration issue at that Slovakian supplier. The
others would have led to different solutions — solutions that would have
failed because they were answering a different question than the one
reality was asking.
The frame is not a detail. The frame is the fate.
Why We Frame Poorly
Understanding why organizations consistently frame problems
incorrectly requires understanding three cognitive forces that operate
below the surface of every investigation.
1. Proximity Bias
We frame problems based on what we can see, what is nearby, and what
falls within our departmental boundaries. The quality engineer frames
the problem as a quality issue. The maintenance manager frames it as an
equipment issue. The logistics coordinator frames it as a handling
issue. Each is looking through the lens of their own domain — and each
lens shows a different problem.
This is not ignorance. It is architecture. Most organizations are
structured so that no single person has visibility across the entire
value stream. The quality engineer has never ridden in the truck from
Slovakia to Germany. The logistics coordinator has never stood at the
injection molding machine. The frame is shaped by organizational
boundaries before the investigation even begins.
2. Temporal Compression
We frame problems based on the moment of detection rather than the
moment of causation. A defect discovered at final assembly might have
been caused three weeks earlier, in a different building, by a process
that has since completed its run and been reset for a different
product.
The human brain naturally compresses time. We see the defect now, so
we look for causes now. We look at the process that is running now, the
operator who is on shift now, the machine that is operating now. But the
cause may have come and gone — and with it, the evidence that would have
revealed the true frame.
3. Narrative Gravity
Once an organization starts telling a story about a problem, the
story develops gravitational pull. Evidence that supports the story is
collected eagerly. Evidence that contradicts it is dismissed as outlier,
anomaly, or irrelevant. The narrative hardens into orthodoxy, and the
frame becomes locked.
This is the most dangerous framing failure because it is
self-reinforcing. The more resources you invest in a particular frame,
the harder it becomes to abandon it. The €340,000 inspection system
didn’t just fail to solve the packaging problem — it made it
harder to discover the packaging problem, because admitting the
wrong frame meant admitting the investment was misallocated.
The Anatomy of a Good Frame
A well-framed quality problem has five characteristics:
It
Describes What Is Happening, Not Why It Is Happening
Bad frame: “The operators are scratching the parts during
handling.”
Good frame: “Surface defects are appearing on Component A between
final inspection and customer receipt.”
The first frame embeds a cause (operator handling) and a location
(during handling). The second frame describes the phenomenon without
prejudging either. The second frame leaves open the possibility that the
cause is elsewhere, else-when, and else-how.
It Includes the
Full Temporal and Spatial Scope
Bad frame: “The defect appears at Station 12.”
Good frame: “The defect is first detectable at Station 12. The part
was last confirmed defect-free at Station 8. Between Stations 8 and 12,
the part passes through cooling, storage, and intermediate
handling.”
The first frame locates the problem at Station 12. The second frame
defines a window — a territory where the cause must reside.
That territory may cross departmental boundaries, shift changes, and
even facility walls.
It Is Testable
A good frame generates hypotheses that can be proven false. “The
parts are being damaged during transport” is testable — you can ship
parts with impact sensors, you can simulate the transport route, you can
compare parts shipped by different methods. “The process is unstable” is
testable — you can run capability studies, you can analyze control
charts, you can compare shifts and machines and materials.
“The quality culture is bad” is not testable. It is a judgment
dressed as a frame. It produces feelings, not evidence.
It Avoids Blame
Blame is the enemy of framing. The moment a problem is framed as
“Operator X made an error,” the investigation narrows to that operator,
that action, that moment. The systemic factors that created the
conditions for the error — inadequate training, ambiguous work
instructions, poor process design, impossible tolerances — fade from
view.
This does not mean individuals are never responsible. It means that
framing around blame produces individual solutions (retrain, reassign,
discipline) when the problem almost always requires systemic solutions
(redesign, error-proof, simplify).
It Is Willing to Be Wrong
The best problem framers hold their frames loosely. They treat the
initial frame as a hypothesis, not a conclusion. They actively seek
evidence that would disprove their frame. They build “frame-breaking”
into the investigation process — scheduled moments where the team steps
back and asks, “What if we’re looking at this completely wrong?”
This is uncomfortable. It feels inefficient. It requires admitting
uncertainty in environments that reward confidence. But it is the single
most reliable way to avoid the catastrophic cost of solving the wrong
problem.
Practical Tools for Better
Framing
The art of problem framing can be strengthened with deliberate
practices that counteract our cognitive defaults.
The “Five Whys” of Framing
The classic “Five Whys” technique asks why repeatedly to drill down
to root cause. A framing variant asks the same question at the
boundary level:
- Where exactly did this defect originate? (Not where was it found —
where was it born?) - When exactly did the condition that caused this defect first
exist? - What is the full path this product traveled between defect-free
confirmation and defect detection? - What changed — in the product, the process, the environment, the
people, the materials, or the logistics — in that window? - Who else, outside this department or facility, interacted with this
product during that window?
These questions are designed to expand the frame, not narrow it. They
fight proximity bias by forcing the investigation beyond the immediately
visible.
The Frame Audit
Before investing significant resources in any corrective action,
conduct a formal frame audit. Ask three questions:
- What evidence would prove our current frame wrong?
If you cannot answer this, your frame is not a hypothesis — it is a
belief. - What alternative frames could explain the same
evidence? List at least three. If you cannot generate
alternatives, you are locked into a single narrative. - Who in this organization would be least likely to agree with
our frame? Go find that person and listen to them. Dissent is
not disloyalty — it is the most valuable quality data you have.
The Boundary Walk
Physically walk the entire value stream of the affected product — not
the process as it is documented, but the process as it actually happens.
Follow a part from raw material receipt through every transformation,
storage, transport, and handoff until it reaches the point of defect
detection.
You will discover things no process flow diagram will ever show you:
the shelf where parts sit uncovered for three hours between operations,
the corridor where forklifts create vibration that nobody measured, the
staging area where parts from different batches are mixed. These are the
places where wrong frames hide.
The Cost of the Wrong Frame
Let me return to that Slovakian supplier — not because their story is
unusual, but because the mathematics of wrong framing are universal.
They spent €340,000 on the wrong solution. Then they spent another
€85,000 identifying the real cause (packaging vibration) and
implementing the correct fix (redesigned packaging inserts with
vibration-dampening foam). They lost eight months of defect-free
performance. They absorbed two additional customer complaints before the
real cause was found. They allocated engineering resources to the wrong
project for a quarter of a year — resources that were not available for
other improvement initiatives.
Total estimated cost of the wrong frame: approximately €620,000 in
direct costs, plus unmeasured opportunity costs, strained customer
relationships, and organizational credibility.
The correct investigation — properly framed from the start — would
have cost roughly €15,000 and taken three weeks.
The difference between a €15,000 problem and a €620,000 problem was
not technical capability. Both investigations involved competent
engineers, adequate resources, and appropriate methodologies. The
difference was entirely in the framing. One asked, “How do we stop
producing defects?” The other should have asked, “Where in the entire
value stream are defects being introduced?”
The Frame as a Quality
System Capability
Most quality systems are designed to find causes. Few are designed to
question frames. This is a structural gap.
Consider adding formal framing steps to your existing quality
processes:
In your 8D process, add a mandatory frame review
between D2 (Describe the Problem) and D3 (Interim Containment). Before
you contain anything, ask: Are we sure this is the right problem? Are we
looking in the right place? Are we considering the full scope?
In your FMEA process, explicitly include
out-of-station and out-of-facility failure modes. Most FMEAs assume the
failure occurs within the process boundary being analyzed. But what if
the failure occurs in the gap between processes — during transport,
storage, or handoff?
In your audit programs, audit the boundaries between
processes, not just the processes themselves. The interfaces between
departments, the transitions between operations, the moments of handoff
— these are where framing failures accumulate.
In your management reviews, include a section on
“problems we may be framing incorrectly.” This is not a hypothetical
exercise. It is a structured opportunity to surface dissenting views,
challenge orthodoxies, and identify investigations that may be heading
toward expensive wrong answers.
The Framing Mindset
Ultimately, better problem framing is not a technique — it is a
mindset. It is the willingness to hold your understanding of a problem
as provisional. It is the discipline to look wider when every instinct
tells you to look deeper. It is the courage to ask, “What if we’re wrong
about this?” when the organization is already mobilizing around a
confident answer.
The most effective quality professionals I have worked with share a
common trait: they are suspicious of fast certainty. When everyone in
the room nods at the same frame, they get nervous — not because they
enjoy being contrarian, but because they have seen too many
investigations go spectacularly wrong when nobody questioned the
obvious.
The defect you see is real. But the problem it points to may not be
the problem you think it is. The difference between the defect and the
problem — the gap between what is visible and what is true — is where
framing lives.
Master that gap, and you master the most powerful lever in quality
management. Ignore it, and you will keep solving the wrong problems with
increasing sophistication and decreasing effect.
The question you ask is the answer you get. Ask wisely.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has led quality system implementations
on three continents and believes that the difference between good and
great quality organizations is not their tools — it is the questions
they ask before they start using them.
