The Danger of Expecting the
Worst
There is a pattern that runs through manufacturing plants around the
world, and it is devastating in its simplicity. A supervisor walks the
production floor convinced that the night shift cuts corners. Inspectors
review parts from a particular line with the assumption that defects are
lurking. Engineers design poka-yoke devices around the belief that
operators will make every mistake possible if given the chance. And
slowly, inexorably, the people being watched, measured, and
second-guessed begin to deliver exactly the poor performance that was
expected of them.
This is the Golem Effect, named after the creature of Jewish
mythology — a being shaped from clay and brought to life, but ultimately
driven by the limitations imposed upon it by its creator. In
organizational psychology, the Golem Effect describes a phenomenon in
which low expectations placed upon individuals lead to diminished
performance. It is the dark mirror of the Pygmalion Effect, where high
expectations elevate performance. Both are powerful. Both are real. But
in manufacturing and quality management, it is the Golem Effect that
does the more insidious damage, precisely because so few organizations
recognize that their quality problems are not originating on the factory
floor — they are originating in the minds of the people managing it.
The mechanism is not mystical. It is psychological, structural, and
deeply human. When leaders communicate — through their actions, their
words, their inspection regimes, their disciplinary policies, and their
investment decisions — that they expect poor performance, the recipients
of those messages internalize them. Effort decreases. Engagement
collapses. Why try to hit a target that nobody believes you can hit? Why
flag a defect when the response is suspicion rather than appreciation?
Why invest yourself in a process that was designed around the assumption
that you will fail?
The Golem Effect does not require malice. It does not require
conscious intent. It requires only a pattern of low expectations,
consistently communicated, over time. And manufacturing environments are
uniquely fertile ground for this pattern to take root, because the
entire apparatus of quality control — inspections, audits, corrective
actions, statistical process control — can be deployed in ways that
scream “we don’t trust you” to the people doing the actual work.
How the Golem
Effect Takes Hold in Manufacturing
Consider a midsize automotive components plant in the American
Midwest. The plant produces machined aluminum housings for transmission
systems — tolerances measured in thousandths of an inch, surface finish
requirements that demand consistent tooling maintenance, and a customer
audit schedule that keeps everyone on edge. The plant manager, a
meticulous engineer by training, has watched defect rates fluctuate for
years and has gradually built an elaborate system of controls: multiple
inspection stations, 100% final inspection on critical dimensions,
rework authorization forms that require supervisor sign-off, and a
disciplinary policy that ties scrap rates to performance reviews.
The intent behind every one of these measures was noble. The plant
manager wanted to reduce defects. But the cumulative message to the
operators was unmistakable: We don’t trust you to get this right on
your own.
The operators responded in ways that were entirely predictable to
anyone familiar with the Golem Effect, though invisible to the plant
manager himself. Some stopped caring about the subtle signals their
machines gave them — the slight change in vibration, the barely audible
shift in cutting tone — because they knew someone downstream would catch
anything they missed. Others stopped suggesting improvements to fixtures
and workflows because previous suggestions had been met with skepticism
or ignored entirely. A few began to resent the constant surveillance
and, whether consciously or not, began to put in the minimum effort
consistent with not being fired. The defect rate did not improve. In
some months, it worsened.
The plant manager’s response was to add more inspections. The
operators’ response was to withdraw further. The cycle continued.
This is the Golem Effect in action. It is not a story about bad
workers or bad managers. It is a story about a system of expectations
that creates the very outcome it fears. And it is far more common than
most quality professionals are willing to admit.
The
Psychological Mechanism: Four Stages of Decline
Research in organizational psychology, building on the foundational
work of Rosenthal and Jacobson in educational settings and later adapted
to workplace contexts by Dov Eden and others, identifies a four-stage
process through which the Golem Effect operates:
Stage 1: Expectation Formation. A manager forms a
low expectation of an individual or group. In manufacturing, this might
be based on historical data (“that line always has the highest scrap
rate”), on stereotypes (“new hires always struggle with this
operation”), or on a single negative experience (“the last time I
trusted that team, we had a customer complaint”). The expectation may be
accurate or inaccurate — what matters is that it exists and that it is
negative.
Stage 2: Behavioral Communication. The manager’s
expectation manifests in behavior. Supervisors hover over operators they
consider unreliable. Inspection frequency increases for lines perceived
as problematic. Corrective action requests are issued with a tone of
accusation rather than inquiry. Training opportunities are withheld from
employees deemed unlikely to benefit from them. Job instructions become
longer, more prescriptive, and more patronizing. The target of these
behaviors reads the message clearly, even if no one ever says “we expect
you to fail” out loud.
Stage 3: Recipient Response. The recipient of the
low-expectation message adjusts their behavior accordingly. Motivation
drops. Effort decreases. The willingness to take initiative evaporates.
Engagement with continuous improvement activities collapses. In some
cases, the response is conscious and deliberate — a form of quiet
protest. In most cases, it is unconscious and automatic, a natural human
response to being undervalued and distrusted.
Stage 4: Outcome Confirmation. The diminished
performance confirms the original low expectation, reinforcing the
manager’s belief and setting up the next cycle. The supervisor sees the
rising defect rate and thinks, “I was right not to trust them.” The
operators feel the increased scrutiny and think, “Nothing we do is ever
good enough.” The loop closes and tightens.
This cycle can operate for years without anyone recognizing it for
what it is. The quality system records the defects. The management team
responds with more controls. The operators comply with the controls but
disengage from the work. The defect rate stays stubbornly high. Everyone
is working hard. Nobody is getting results. And the root cause — the
expectation itself — remains invisible.
Where the Golem
Effect Hides in Quality Systems
The Golem Effect does not announce itself. It embeds itself in the
ordinary machinery of quality management, wearing the mask of due
diligence. Here are the places it most commonly hides:
Over-Inspection as Distrust
Every inspection station is, on some level, an acknowledgment that
the previous step might have been done incorrectly. This is reasonable
and necessary within limits. But when inspection layers accumulate
beyond what the process risk analysis justifies, the message shifts from
“this is a high-risk operation” to “we don’t believe the people doing
this work can do it correctly.” Operators who sense this message stop
taking ownership of quality at their own station. After all, why bother
when someone else is checking everything anyway? The over-inspection
becomes a self-fulfilling prophecy: the more you inspect, the less care
goes into the original operation, and the more defects you find — which
justifies the over-inspection.
Blame-Oriented Corrective
Action
The difference between a root cause investigation that asks “what
went wrong with the system?” and one that asks “who is responsible?” is
the difference between a learning organization and a Golem-generating
one. When corrective action processes consistently converge on operator
error as the root cause — without examining the system conditions that
made the error likely or even inevitable — the organization is
communicating that it views its people as the problem. Operators who are
repeatedly blamed for system-level failures learn to hide problems, to
deflect responsibility, and to invest their energy in self-protection
rather than in quality improvement.
Training as Remediation Only
Organizations affected by the Golem Effect tend to deploy training
almost exclusively as a response to problems. “You made a defect; here
is retraining on the standard work.” The implicit message is that
training is a consequence of failure rather than an investment in
growth. Over time, the word “training” itself becomes associated with
punishment and inadequacy. Operators who would benefit from advanced
skills development are never offered it because they have been
categorized as “needing remediation” rather than “ready for
advancement.”
Exclusion from
Problem-Solving
In many plants, continuous improvement activities — kaizen events,
quality circles, six sigma projects — are dominated by engineers,
managers, and quality professionals. The operators who actually perform
the work are either excluded entirely or included in a token capacity.
This exclusion communicates that the organization does not value the
knowledge and insight of its frontline workers. The operators respond by
withholding the very knowledge that could solve the quality problems the
engineers are struggling with. Why share what you know when nobody asks,
and when your input has been dismissed in the past?
Micromanagement of Standard
Work
Standard work is a cornerstone of lean manufacturing, and for good
reason. But there is a difference between clear, concise standard work
that defines the critical elements of a task and a twenty-page document
that specifies every breath an operator should take. When standard work
documents become excessively detailed and prescriptive — when they
attempt to eliminate all operator judgment rather than channel it
effectively — they communicate that the organization views operator
intelligence as a liability rather than an asset. Operators who are
treated as interchangeable extensions of their machines begin to act
like it.
The Cost: What the
Golem Effect Destroys
The damage inflicted by the Golem Effect extends far beyond the
immediate increase in defect rates. It corrodes the foundations of
quality culture in ways that are difficult to measure but impossible to
ignore.
Loss of Tacit Knowledge. Experienced operators
accumulate an enormous body of tacit knowledge — the subtle signs of
tool wear, the feel of a proper fit, the instinct for when a process is
drifting. When the Golem Effect causes disengagement, this knowledge is
neither applied nor shared. It dies with each frustrated departure.
Destruction of Psychological Safety. Quality
improvement requires people to speak up about problems, to challenge
assumptions, and to experiment with new approaches. The Golem Effect
destroys the psychological safety that makes this possible. In an
environment where low expectations are the norm, admitting to a defect
becomes an act of self-sabotage. Reporting a near-miss becomes a
confession of incompetence. Suggesting an improvement becomes an act of
defiance.
Erosion of Continuous Improvement. Continuous
improvement depends on the willingness of every person in the
organization to look for opportunities to make things better. The Golem
Effect kills this willingness at its source. People who are not expected
to contribute anything beyond minimal compliance do not look for ways to
improve. They look for ways to survive the shift.
Escalation of Quality Costs. The financial impact is
straightforward and severe. More defects mean more scrap, more rework,
more warranty claims, and more customer complaints. More inspections
mean more labor hours devoted to finding defects rather than preventing
them. More turnover means more training costs and more ramp-up periods
during which defect rates spike. The Golem Effect is not just a
psychological phenomenon — it is a cost multiplier.
Breaking the Cycle:
Practical Strategies
Reversing the Golem Effect requires a fundamental shift in how an
organization views its people. It is not sufficient to add a “positive
thinking” module to the next all-hands meeting. The change must be
structural, sustained, and genuine.
Audit Your Own Expectations
Before changing any policy or process, managers must examine their
own beliefs about the people they manage. This is uncomfortable work. It
requires honesty about the assumptions that drive daily decisions. Ask
yourself: When was the last time I was genuinely surprised by good
performance from an operator I had previously written off? When was the
last time I gave someone a challenging assignment without hedging it
with extra oversight? If the answers are difficult to come by, the Golem
Effect may already be at work.
Redesign
Inspection as Support, Not Surveillance
Shift the language and the practice of inspection from “catching
defects” to “supporting quality.” Cross-train inspectors and operators
so that each understands the other’s work. Rotate inspection
responsibilities so that the inspector role is not permanently
associated with distrust. Share inspection data with operators in real
time, not as a report card but as a tool for self-correction. When
operators experience inspection as a resource rather than a judgment,
they engage with it rather than resist it.
Invest in People Before
Problems Arise
Training should be a proactive investment in capability, not a
reactive response to failure. Offer skills development opportunities to
all operators, not just those who have demonstrated exceptional
performance or those who have made errors. Create visible career
pathways that give operators a reason to invest in their own
development. When people see that the organization is investing in them,
they invest in the organization.
Include Operators in
Problem-Solving
The people closest to the work have the most relevant knowledge about
what is going wrong and what could go better. Create structured
opportunities for operators to participate in root cause analysis,
process improvement, and design review. Not as tokens — as genuine
contributors whose input is valued and acted upon. When people see their
ideas implemented, they generate more ideas. When they see their ideas
ignored, they stop offering them.
Reframe Failure as Learning
When a defect occurs, the first question should be “what in our
system allowed this to happen?” — not “who is responsible?” This does
not mean abandoning accountability. It means directing accountability at
the system first and the individual second. Organizations that master
this distinction create environments where people are willing to report
problems early, when they are small and solvable, rather than hiding
them until they become catastrophes.
Measure Engagement
Alongside Quality
Most manufacturing plants track defect rates, scrap rates, and
customer complaint volumes with meticulous precision. Very few track
operator engagement, morale, or psychological safety with the same
rigor. If you want to know whether the Golem Effect is at work in your
plant, start measuring the human dimensions of quality alongside the
technical ones. Employee engagement surveys, anonymous feedback
mechanisms, and turnover rates by line and shift are all leading
indicators that can reveal a Golem problem before it shows up in the
defect data.
The Deeper Lesson:
You Get What You Expect
The Golem Effect is ultimately a story about belief. Not belief in
the abstract, but belief as it manifests in the daily decisions,
structures, and interactions of a manufacturing organization. Every
inspection station you add, every corrective action you issue, every
training session you mandate, and every problem-solving meeting you hold
without your operators communicates something. The question is whether
what you are communicating is “we believe in your ability to do great
work” or “we expect you to fail.”
The plants that consistently achieve the highest quality are not the
ones with the most sophisticated inspection systems or the most
elaborate control plans. They are the ones that have figured out how to
align their quality systems with a genuine belief in the capability and
commitment of their people. They inspect because it is smart, not
because they distrust. They train because they want people to grow, not
because they need people to be fixed. They involve operators in
problem-solving because they know that the best solutions come from the
people closest to the work.
The Golem Effect reminds us that quality is not just a technical
discipline. It is a human one. The tolerances on your drawings, the
capability indices on your control plans, and the algorithms in your
statistical software are all necessary. But they are not sufficient. The
most powerful quality system in the world will underperform if the
people operating it believe — because they have been told, through a
thousand small signals — that they are not trusted to do it well.
Expect more. Trust more. Invest more. And watch what happens when the
people you believed in start believing in themselves.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality management, continuous
improvement, and organizational transformation. He has worked with
organizations across automotive, aerospace, electronics, and medical
device manufacturing to build quality systems that respect the
intelligence and capability of every person in the organization.
