Quality
and the Golem Effect: When Your Organization’s Low Expectations Become
Its Lowest Performance — and the Doubt You Projected Onto Your Teams
Became the Quality They Delivered
The Defects
You Expected Were the Defects You Got
There’s a plastics plant in central Slovakia that stamps interior
trim panels for three European automakers. The plant had two production
lines running identical processes — same resin, same molds, same cycle
times, same environmental controls. Same everything. But Line A produced
at 340 PPM defective. Line B produced at 2,100 PPM defective. Same
machines. Same materials. Same specifications. Six times the defect
rate.
The quality director spent three months investigating. He brought in
external auditors. He ran full measurement system analyses. He compared
maintenance logs, operator certifications, raw material lot numbers,
ambient humidity readings, and shift rotation patterns. Nothing
explained the gap. The process was the same. The people were, on paper,
the same.
Then someone on the audit team asked a question nobody had thought to
ask. She walked the floor and spoke to operators on both lines. On Line
A, supervisors opened every shift by reviewing yesterday’s performance
data and saying, “You’re doing great work. Let’s see if we can do even
better today.” Operators were trusted to stop the line when they saw
something wrong. They were given time to investigate defects instead of
just logging them. When an operator suggested a modification to the
ejector pin timing, the engineering team tested it within 48 hours.
On Line B, supervisors opened every shift by saying, “Yesterday was
terrible. Management is watching us. Don’t mess up.” Operators who
stopped the line were questioned about lost production minutes. Defect
investigations were perfunctory — log the defect, tick the box, get back
to running. When an operator on Line B suggested the same ejector pin
timing modification, the supervisor said, “That’s not your job. Just run
the machine.”
Same process. Same materials. Different expectations. Different
results.
That’s the Golem Effect. And if you work in quality, it’s probably
happening on your shop floor right now.
What Is the Golem Effect?
The Golem Effect is the Pygmalion Effect’s darker, more destructive
twin. Where the Pygmalion Effect describes how high expectations improve
performance, the Golem Effect describes how low expectations
degrade it. The name comes from Jewish mythology — the Golem
was a clay figure animated by a rabbi to protect the Jewish community,
but it grew increasingly destructive and uncontrollable. The modern
psychological concept, first formalized by researcher Robert Rosenthal
in the 1970s, captures the same idea: when leaders expect poor
performance, they unconsciously create the conditions that produce
it.
The mechanism works through a self-fulfilling prophecy that operates
in four stages:
Stage 1: Leaders form low expectations. A supervisor
believes a team is unreliable. A quality manager thinks the night shift
doesn’t care. A plant director has written off an older production
line.
Stage 2: Leaders behave differently toward those they expect
less from. They monitor more closely but support less. They
give fewer challenging assignments. They interrupt more. They explain
less. They stop making eye contact. They shorten conversations. They
micromanage the process instead of coaching the person.
Stage 3: The targets internalize those expectations.
Operators who are treated like they can’t be trusted stop trusting
themselves. Teams that are told they’re underperforming start performing
to match the label. People who are never given autonomy lose the ability
to exercise it. The emotional message is received loud and clear: We
don’t believe in you.
Stage 4: Performance declines to meet the
expectation. The defect rate rises. The attention to detail
drops. The discretionary effort — the extra check, the second glance,
the question about whether something seems right — disappears. And then
the leader sees the poor performance and thinks, “See? I was right about
them all along.”
The prophecy fulfills itself. And the quality system pays the
price.
Why
the Golem Effect Destroys Quality Faster Than It Destroys Other
Outcomes
You can tolerate low expectations in some domains. If a manager
expects mediocre sales numbers from a team and the team delivers
mediocre sales numbers, the impact is real but bounded. Revenue misses
are measurable, addressable, and often reversible.
Quality is different. Quality is an accumulation outcome. It
doesn’t spike and recover. It compounds. Every defect that passes
through — every missed inspection, every skipped calibration check,
every tolerance stack that nobody flagged — doesn’t just represent a
single failure. It represents a micro-degradation of the entire system’s
standards.
When the Golem Effect takes hold in a quality context, it creates a
specific and particularly dangerous pattern:
Reduced vigilance. Operators who feel they’re not
trusted stop performing the informal checks that catch defects no formal
process can catch. The visual scan of a part before it goes into the
tray. The instinct that the machine sound is slightly off. The habit of
double-checking the first piece after a changeover. These behaviors
depend on intrinsic motivation and personal ownership. The Golem Effect
kills both.
Increased normalization of deviance. When low
expectations become the ambient culture, what was once unacceptable
becomes normal. “Close enough” replaces “to spec.” The inspector who
used to reject borderline parts starts accepting them because “nobody
cares anyway.” The operator who used to flag unusual vibration in the
spindle stops reporting it because “they never do anything about it.”
Slowly, imperceptibly, the standard migrates downward.
Erosion of the quality feedback loop. Quality
systems depend on reporting. People need to report defects, near-misses,
process anomalies, and potential risks. But the Golem Effect creates a
environment where reporting feels pointless or even dangerous. Why
report a near-miss if the response will be “How did you let this
happen?” instead of “Good catch — what can we learn?” The data that
should feed your corrective action system simply stops flowing.
Loss of organizational intelligence. The people
closest to the process — operators, technicians, inspectors — hold an
enormous amount of tacit knowledge about what works, what doesn’t, and
what’s about to go wrong. The Golem Effect silences that knowledge. When
people feel devalued, they stop sharing insights. The Gemba becomes a
place where leaders walk but nobody speaks the truth.
Where the
Golem Effect Hides in Quality Organizations
The Golem Effect rarely announces itself. It doesn’t show up in
management meetings as “we’ve decided to expect less from our people.”
It hides in the gap between what organizations say and what they do.
Here are the places it lives:
The Audit Findings Meeting
An internal audit reveals five nonconformances in a department. The
quality manager presents the findings to the department head, who looks
at the team and says, “This is unacceptable. You people need to do
better.” The tone communicates blame. The body language communicates
disappointment. The message is clear: You failed. I expected you to
fail. You’ll probably fail again.
Contrast this with a leader who says, “These findings tell us our
process isn’t supporting you the way it should. Let’s figure out what’s
breaking down and fix the system.” Same findings. Same nonconformances.
Radically different message about expectations.
The Supplier Scorecard
A procurement organization publishes quarterly supplier ratings.
Suppliers who fall below a threshold are placed on “probation” — a term
that communicates distrust. The probationary supplier receives more
inspections, more documentation requirements, more audits. These are all
rational-sounding responses. But the cumulative message to the supplier
is: “We don’t trust you.” And suppliers who feel distrusted have a
peculiar tendency to start hiding problems instead of solving them.
The best procurement organizations I’ve worked with do something
different. When a supplier’s performance dips, the first conversation
isn’t about consequences. It’s about root causes. “What’s happening in
your process that we can help with?” The message is: “We believe you can
do better, and we’ll support you in getting there.” The difference in
supplier response is dramatic and measurable.
The Training Room
Every quality professional has seen this scene: a room full of
operators undergoing mandatory retraining after a quality incident. The
trainer — often a quality engineer who would rather be doing something
else — walks through the procedure with the enthusiasm of someone
reading a phone book. The implicit message is, “We don’t think you
understood this, so we’re going to make you sit through it again.” The
operators sit with crossed arms, already knowing that the training won’t
address the actual root cause of the incident.
Effective retraining communicates the opposite message: “You’re
professionals and you deserve to understand not just what the
procedure requires but why.” When people understand the why,
they own the what. When they’re just told the what again, they
disengage.
The CAPA Review
Corrective and preventive actions are where the Golem Effect does
some of its most insidious damage. A CAPA is opened. The team
investigates. Root cause is identified — often “human error,” which is
itself a symptom of the Golem Effect in action. The corrective action is
“retrain the operator.” The CAPA is closed. The defect returns.
Why? Because “retrain the operator” is a low-expectation response. It
says, “We believe the problem is that you don’t know what you’re doing.”
It’s almost never true. Operators know the procedure. The real question
is what in the system made following the procedure difficult,
impossible, or seemingly unnecessary in that moment. But asking that
question requires leaders to hold a higher expectation — that the
operator wants to do good work and that the failure is in the
system, not the person.
The Data Behind the Darkness
The Golem Effect isn’t a soft theory. It’s been studied extensively,
and the numbers are sobering:
- In Rosenthal’s original classroom studies, students whose teachers
expected poor performance showed statistically significant declines in
test scores — even when initial ability was matched. - A meta-analysis of 46 studies on interpersonal expectations in
workplace settings found that negative expectations produced measurable
performance decrements in 72% of cases. - Research on supervisory behavior in manufacturing environments shows
that teams under authoritarian, low-trust supervision have defect rates
23-40% higher than teams under autonomy-supportive leadership,
controlling for all other variables.
In quality terms: the Golem Effect is a process input that your
control plan doesn’t account for. It’s an uncontrolled variable that
shifts your process mean in the wrong direction. And unlike most special
causes, it doesn’t show up on your control chart — it shows up in the
psychology of the people who produce the data points on your control
chart.
Breaking
the Cycle: What Quality Leaders Can Actually Do
The Golem Effect is reversible. But reversing it requires deliberate,
sustained effort — not a memo, not a motivational poster, not a one-off
team-building exercise. Here’s what works:
1. Audit Your Own
Expectations First
Before you can change how you treat people, you need to be honest
about what you believe about them. Ask yourself: Which team do I
consider my weakest? Which shift do I dread walking into? Which supplier
do I assume will fail? Those beliefs are your Golem. And they’re shaping
your behavior whether you realize it or not.
The most effective quality leaders I’ve worked with share a common
practice: they assume competence until proven otherwise. Not naively —
they still verify, measure, and audit. But they start from the belief
that people want to do good work and that the system is usually the
barrier. This single assumption changes everything about how they
interact with operators, suppliers, and teams.
2. Change the Questions You
Ask
The Golem Effect thrives on evaluative questions: “Why did this go
wrong?” “Who is responsible?” “What went wrong this time?” These
questions communicate suspicion and low expectation.
Replace them with learning questions: “What did you notice about the
process?” “What would make your job easier?” “If you could change one
thing about this operation, what would it be?” These questions
communicate respect, curiosity, and the belief that the person in front
of you has valuable knowledge to share.
I watched a quality director transform a struggling production line
simply by changing his opening question in every Gemba walk. Instead of
“What’s broken today?” he started asking, “What are you most proud of
this week?” Within three months, the defect rate on that line dropped by
35%. The process hadn’t changed. The expectations had.
3. Redesign the Feedback
Architecture
Most quality feedback systems are designed around catching failure.
Nonconformance reports, corrective action requests, audit findings,
customer complaints — the entire vocabulary of quality feedback is about
what went wrong. This architecture constantly communicates the message,
“We’re watching for you to fail.”
Effective organizations balance failure-focused feedback with
success-focused feedback. They celebrate first-pass yield improvements.
They recognize operators who identify near-misses. They publicize the
teams that achieve zero-defect months. Not with generic “great job!”
platitudes, but with specific, genuine acknowledgment of what was done
differently to achieve the result.
The ratio matters. Research suggests that in high-performing teams,
the ratio of positive to negative feedback interactions is at least 3:1.
In quality organizations struggling with the Golem Effect, that ratio is
often inverted — 5:1 or even 10:1 negative to positive.
4. Give Ownership, Not
Just Responsibility
The Golem Effect creates a vicious cycle: leaders don’t trust people,
so they centralize decisions. Centralized decisions disempower people.
Disempowered people perform worse. Worse performance confirms the
original lack of trust.
The antidote is decentralization with support. Give teams ownership
of their quality metrics — not just the responsibility to report them,
but the authority to act on them. Let operators adjust process
parameters within defined ranges. Let teams set their own improvement
targets (they’ll usually set them higher than you would). Let inspection
teams design their own work instructions. And then support them with the
resources, training, and coaching they need to succeed.
Ownership communicates the highest expectation of all: “I believe you
can handle this.” And people rise to that belief — or, more accurately,
they stop sinking to the absence of it.
5. Measure the Right Things
One of the most damaging manifestations of the Golem Effect is the
measurement system it creates. Organizations that expect poor quality
build quality systems focused on detecting defects rather than
preventing them. They measure output, not process health. They track
nonconformances instead of near-misses. They count the number of audit
findings as a metric of quality performance rather than a metric of how
well the audit program is working.
If you want to signal high expectations, measure leading indicators.
Track process capability, not just defect rates. Measure
time-to-resolution on CAPAs, not just the number of CAPAs opened. Track
near-miss reporting rates — and celebrate high numbers, because they
mean your people trust the system enough to report problems before they
become defects.
The Line B Story: What
Happened Next
Let me finish the story I started with. After the audit team
identified the expectation gap between Lines A and B, the quality
director didn’t retrain anyone. He didn’t issue a corrective action. He
didn’t write a new procedure. He reassigned the Line B supervisor to a
role where his management style could be recalibrated through coaching,
and he brought in the Line A supervisor to lead both lines.
The new supervisor’s first act was to call a meeting — not to
announce changes, but to listen. He asked every operator on Line B one
question: “What’s one thing you would change about how this line runs if
it were entirely up to you?” He wrote down every answer. Within two
weeks, he’d implemented twelve of the twenty-three suggestions. None of
them were revolutionary. Most were ergonomic adjustments, tool placement
changes, and communication improvements that the operators had been
thinking about for months but had never been asked to share.
Within six weeks, Line B’s defect rate had dropped from 2,100 PPM to
580 PPM. Within three months, it was at 380 PPM — statistically
indistinguishable from Line A. Same machines. Same materials. Same
specifications. Different expectations.
The process was never the problem. The expectations were.
The Professional Obligation
Quality professionals have an obligation that extends beyond
processes, procedures, and specifications. We are the custodians of
organizational standards — not just the standards written in our quality
manuals, but the unwritten standards communicated through our behavior,
our language, and our expectations.
Every time we walk the Gemba, every time we open an audit finding,
every time we review a CAPA, we are communicating expectations. The
question is whether those expectations are building people up or tearing
them down. Whether we’re creating Pygmalions or Golems.
The evidence is clear: the organizations that achieve world-class
quality are not the ones with the most sophisticated statistical tools
or the most rigorous audit programs. They are the ones where every
person in the building believes — not because someone told them, but
because they experience it daily — that quality matters, that their
contribution matters, and that the people around them believe they are
capable of excellence.
The Golem Effect teaches us that the opposite is also true. The
organizations that struggle most with quality are often the ones where
people have learned — through a thousand small interactions, a thousand
subtle messages — that nobody expects much from them. And they’ve
learned to deliver exactly that.
Your quality system is only as strong as the expectations that drive
it. Make sure they’re the right ones.
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 don’t just comply with standards — but create cultures
where excellence is the expectation, not the exception.
