Quality and the Einstellung Effect: When Your Organization’s Expertise Becomes Its Blind Spot — and the Solutions That Worked Yesterday Prevent You From Seeing the Solutions That Would Work Tomorrow

Uncategorized

Quality
and the Einstellung Effect: When Your Organization’s Expertise Becomes
Its Blind Spot — and the Solutions That Worked Yesterday Prevent You
From Seeing the Solutions That Would Work Tomorrow

The Expert Who Couldn’t
See the Obvious

In 1942, a psychologist named Abraham Luchins published a study that
would haunt every quality manager who has ever stared at a recurring
defect and thought, “I’ve seen this before.” He gave people a series of
water jar problems — puzzles where you had to measure exact amounts
using three jars of different sizes. The first few problems all required
the same solution pattern: fill Jar B, pour from B into A, then pour
from B into C. Fill, transfer, transfer. Every time.

Then Luchins slipped in a problem that could be solved in one step —
just fill Jar A directly. No transfers. No complexity. A child could see
it.

But the experts — the people who had already solved five problems
using the fill-transfer-transfer method — couldn’t see the simple
solution. They kept applying the complex formula even when it was
unnecessary. They had developed what Luchins called
Einstellung: a mental set. The German word means “attitude” or
“setting,” but in psychology, it refers to something far more dangerous
— the tendency to approach new problems with solutions that worked on
old ones, even when better solutions are staring you in the face.

The Einstellung Effect is not about stupidity. It is the exact
opposite. It is what happens when expertise becomes a cage. And if you
have spent any time in quality management, you have watched it happen —
in your team, in your leadership, and if you are honest, in
yourself.

Why Your Best People
Are Your Biggest Risk

In quality, we worship experience. We want engineers who have seen a
thousand defects, managers who have navigated a hundred audits,
operators who can feel when a machine is drifting out of spec before the
SPC chart catches it. And we should want those people. Their pattern
recognition is invaluable. Their instinct for where things go wrong has
saved organizations millions.

But pattern recognition has a dark side. The brain does not store
solutions and problems separately. It stores them as paired units. When
you encounter something that looks like a problem you have
solved before, your brain does not say, “Let me evaluate this fresh.” It
says, “I know this one,” and reaches for the familiar solution before
you have even finished defining the problem.

This is not a character flaw. It is neurology. The basal ganglia —
the part of your brain that handles habits and automatic behaviors — is
faster than the prefrontal cortex, which handles deliberate reasoning.
By the time your conscious mind engages, your habitual response has
already been selected. The expert’s brain is a well-oiled machine for
producing familiar answers. That is its strength. That is also its
vulnerability.

In a manufacturing environment, the Einstellung Effect shows up
everywhere:

The recurring defect that gets the same root cause every
time.
Your team has investigated this weld defect six times.
Every investigation concludes “operator technique.” The corrective
action is always “retraining.” The defect comes back. Nobody questions
whether the root cause was ever actually operator technique — because
the pattern matches, the brain stops searching.

The audit finding that gets the same response every
time.
The auditor flags the same nonconformity three years
running. Your team writes the same corrective action — update the
procedure, train the people. It satisfies the auditor. It does not fix
the problem. But the organization has a mental set: audit finding equals
procedure update. It cannot see that the real issue is the process
itself.

The new product that gets the old failure mode
analysis.
Your FMEA team is populated with veterans of the
previous product line. They bring their failure mode list from the old
program. They rate risks based on what went wrong last time. They miss
an entirely new category of risk because their mental set is calibrated
to the old product, and the new one has a different physics, a different
supply chain, a different customer expectation.

The Water Jar on Your Shop
Floor

Let me make this concrete with a story from a real plant — an
automotive supplier making precision-machined housings for transmission
systems. They had a chronic problem with bore diameter variation on a
critical center bore. The tolerance was tight — 18 microns — and they
were running at a Cpk of 0.89. Not terrible, but not capable. The
customer was pushing back.

This plant had excellent engineers. People with 15, 20 years of
experience. And they had attacked this problem repeatedly. Every time,
they came at it from the same angle: tooling. They adjusted the cutting
tool geometry. They changed the tool material. They tightened the tool
change intervals. They installed a tool presetter with tighter
calibration. Each intervention produced a small improvement. None of
them got the Cpk above 1.0.

I asked a simple question: “Have you looked at the coolant?”

The room went quiet. Not because it was a brilliant insight. Because
it was obvious — and nobody had thought of it. The coolant system was
original equipment from 12 years ago. The flow rate had never been
verified. The coolant concentration was checked weekly, but the
filtration system had not been maintained. Chips were recirculating.
Thermal variation from inconsistent coolant flow was causing the bore to
expand and contract during the cut, producing variation that no tooling
change could ever fix.

They fixed the coolant system in three days. Cpk went to 1.45.

Why had a team of experienced engineers spent two years optimizing
tooling and never once looked at the coolant? Because they had solved
bore diameter problems before — and it was always tooling. Their mental
set said “bore variation equals tooling issue.” The Einstellung Effect
had turned their expertise into a blind spot.

This is not an isolated incident. It is the default mode of
experienced organizations. And it is arguably the most expensive hidden
cost in quality management.

The Three Traps of Expert
Thinking

The Einstellung Effect in quality organizations typically manifests
through three interlocking traps:

Trap 1: The Familiar Solution
Trap

When you have a hammer, everything looks like a nail. When your
quality team has successfully used Six Sigma DMAIC to reduce variation,
every variation problem gets the DMAIC treatment — even the ones that
are really design problems, or supplier problems, or cultural problems
that no statistical analysis will solve.

I watched an organization spend six months running a DMAIC project on
a defect that was ultimately traced to a supplier quietly changing their
raw material specification. The data was beautiful. The analysis was
rigorous. The solution was irrelevant — because the problem was not a
process variation issue. It was a supply chain integrity issue. But the
team’s mental set was “we do DMAIC here,” so they DMAIC’d a problem that
needed a supplier audit, not a control chart.

Trap 2: The Competence Trap

This one is perverse: the better you are at solving a particular type
of problem, the less likely you are to recognize when you are facing a
different type of problem. Research by Bilalić, McLeod, and Gobet in
2008 demonstrated this with chess grandmasters. When shown a board
position that resembled a famous pattern they knew, the grandmasters
would immediately see the familiar solution — and completely miss a
faster, more elegant solution that was also available. Their expertise
literally blinded them to the better move.

In quality, this shows up as the team that has gotten so good at
firefighting that they never invest in fire prevention. They are
spectacular at containing defects, sorting product, running containment
actions, and managing customer notifications. Their firefighting skills
are world-class. And because they are so good at it, they never stop to
ask whether the fire should be happening in the first place. The
Einstellung Effect says: “I know how to handle this.” It does not say:
“Should I have to?”

Trap 3: The Framework Trap

Quality professionals love frameworks. ISO 9001, IATF 16949, AS9100,
Six Sigma, Lean, TPS, TQM, Baldrige, EFQM — we have more frameworks than
problems, or so it sometimes feels. And frameworks are genuinely useful.
They provide structure, ensure completeness, and create a shared
language for improvement.

But frameworks also create mental sets. When every problem gets
filtered through your chosen framework, you start seeing the framework’s
categories instead of the problem’s reality. The ISO auditor who
evaluates every process against clause 8.5.1 may miss a cultural issue
that does not fit neatly into any clause. The Lean practitioner who sees
every delay as waste may overlook a delay that is actually a deliberate
quality checkpoint that the previous regime installed for good
reason.

The framework becomes the lens, and the lens determines what you can
see. The Einstellung Effect ensures that you see what the framework
predicts — and nothing else.

How to Break the Mental Set

The Einstellung Effect cannot be eliminated — it is a feature of how
human cognition works. But it can be managed. Here are five practical
strategies that I have seen work in quality organizations:

1. Rotate the Problem Solvers

The same team investigating the same problem will produce the same
solution. This is almost a physical law of quality management. Rotate
people into investigations who have no history with the problem — and
ideally, no history with that type of problem. Bring in the maintenance
engineer for a quality investigation. Bring in the quality engineer for
a maintenance investigation. Bring in someone from a completely
different product line.

Fresh eyes do not have a mental set. That is their only advantage —
and it is enormous.

2. Require the “Stupid
Question” Round

Before any investigation closes, before any corrective action is
approved, hold a formal session where someone — preferably someone
junior or external — is required to ask: “What if everything we assumed
about this problem is wrong?” This is not a symbolic exercise. It needs
to be a genuine permission structure for challenging the team’s
framing.

At one automotive plant, I instituted a rule that every 8D
investigation had to include a section called “Alternative Hypotheses
Considered and Rejected.” Not just the hypothesis the team pursued — but
the ones they dismissed, and why. This forced teams to articulate their
assumptions, and in roughly 20% of cases, it led them to reconsider a
hypothesis they had initially rejected.

3. Use the “What Would
a Beginner Do?” Prompt

Before finalizing a corrective action plan, ask the team: “If someone
with no experience in this process walked in and saw this problem for
the first time, what would they try?” This is not about disrespecting
expertise — it is about temporarily suspending it. The beginner’s
perspective is free from the Einstellung Effect because the beginner has
no mental set to overcome.

I have seen this prompt produce breakthroughs. A new hire asked why a
particular inspection was being done manually when a $200 camera could
do it automatically. The veteran team had never questioned the manual
inspection because it had always been done that way. The beginner had no
investment in the status quo, and so could see what the experts could
not.

4. Separate
Problem Definition From Solution Design

Most quality investigations conflate these two phases. The team
defines the problem and immediately starts designing a solution, often
within the same meeting. This is the Einstellung Effect’s favorite
environment — the faster you move from problem to solution, the more
likely you are to apply the familiar solution.

Force a gap. Define the problem in one session. Sit with it. Let it
marinate. Then design the solution in a separate session, ideally on a
different day. This temporal separation gives the prefrontal cortex time
to engage and evaluate whether the familiar solution is actually the
right one.

5. Track Solution Diversity

Most quality organizations track how many problems they solve. Almost
none track how many different types of solutions they apply. If
your last ten corrective actions were all “retrain the operator,” you do
not have a training problem — you have an Einstellung problem. Your team
has a single-tool mental set.

Start measuring solution diversity as a quality metric. How many
distinct categories of corrective action has your team applied in the
last quarter? If the answer is fewer than five, your team is in a mental
set. They are applying the same solution to every problem because it is
the solution they know, not because it is the solution the problem
needs.

The Paradox of Expertise

Here is the uncomfortable truth: you cannot build a high-performing
quality organization without experienced people, and you cannot protect
that organization from the Einstellung Effect without actively working
against the very expertise that makes those people valuable. The answer
is not to replace experts with beginners. The answer is to build systems
that harness expertise while protecting against its blind spots.

The best quality organizations I have worked with share a common
trait: they treat expertise with deep respect and healthy suspicion.
They value the veteran engineer’s instinct, and they require that
instinct to be tested against fresh evidence. They celebrate pattern
recognition, and they create structures that ensure patterns do not
become prisons.

Abraham Luchins showed us in 1942 that the mind prefers the known
solution over the optimal one. Eighty-four years later, his insight is
still the most underappreciated risk factor in quality management. Your
organization’s expertise is its greatest asset. Do not let it become its
most dangerous liability.

The next time your team confidently proposes a corrective action that
looks exactly like the last five corrective actions — stop. Ask the
stupid question. Bring in the beginner. Check the coolant.

The solution you cannot see is almost always more valuable than the
one you reach for automatically.


Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He specializes in building quality
systems that work with human psychology rather than against it — because
the most sophisticated process in your plant is the one between your
team’s ears.

Scroll top