The Prophecy That Fulfills
Itself
In Jewish folklore, the Golem was a clay figure brought to life — not
through love or intention, but through ritual. It served its creator,
but it was always crude, always limited, never quite what was hoped for.
The Golem did what it was made to do, and nothing more. It could not
transcend its origins because its origins contained no belief in
transcendence.
Modern organizational psychology gave this myth a second life. In
1982, researchers Dov Eden and Abraham Shapira documented what they
called the Golem Effect: the phenomenon whereby low expectations placed
upon individuals lead to diminished performance. It was the dark mirror
of the Pygmalion Effect, Rosenthal and Jacobson’s famous 1968 finding
that high expectations improve outcomes. Where Pygmalion elevated, the
Golem diminished.
For quality professionals, this is not academic trivia. It is a
structural risk. Every day, in factories, laboratories, assembly lines,
and inspection rooms across the world, managers communicate — often
without a single word — that they do not expect excellence. And the
people receiving that message comply. Not out of rebellion. Not out of
laziness. But because human beings are exquisitely tuned to the
expectations of those who hold power over them.
The Golem Effect is not a character flaw in your workforce. It is a
design flaw in your management system.
How the Golem
Effect Works in Manufacturing
The mechanism is deceptively simple, and devastatingly effective. It
operates in a closed loop:
Stage 1: The Manager Forms a Low Expectation. A
supervisor believes that the second shift is less competent. Perhaps
they are newer. Perhaps they had one bad audit result six months ago.
Perhaps the supervisor simply inherited someone else’s prejudice. The
origin barely matters. The belief is formed.
Stage 2: The Expectation Is Communicated. Rarely is
this explicit. No competent manager says, “I expect you to produce
defects.” Instead, the communication is environmental. The second shift
receives fewer resources. Their training is abbreviated. Their questions
are answered impatiently. Their inspection equipment is older,
calibrated less frequently, or shared across more stations. They are
watched more closely but coached less often. Their suggestions in
continuous improvement meetings are met with polite nods and no
follow-up.
Stage 3: The Worker Internalizes the Expectation.
People are remarkably skilled at reading organizational signals. When
every structural cue says, “We do not trust you to produce excellent
work,” the message is received. The worker begins to invest less effort
— not maliciously, but rationally. If excellence is not expected, why
pay the cognitive and emotional cost of pursuing it? If careful
inspection will not be rewarded, why inspect carefully?
Stage 4: Performance Declines. The prophecy is
fulfilled. The second shift’s defect rate rises. Their first-pass yield
drops. Their rework hours increase. The data, when it arrives on the
manager’s desk, confirms the original belief.
Stage 5: The Belief Is Reinforced. The manager sees
the numbers and thinks, “I was right. They are not as good.” The loop
tightens. Resources are further reduced. The spiral continues.
This is not speculation. Eden’s research in Israeli military units
demonstrated that trainees whose commanders expected less of them
performed measurably worse on objective tests of competence. The
commanders’ expectations were randomly assigned — the trainees had no
inherent differences. The difference was created entirely by the
expectation.
Where the Golem
Effect Hides in Quality Systems
The Golem Effect does not announce itself. It does not appear in your
audit reports as a line item. It hides inside systems that look
perfectly reasonable on paper.
Inspection Assignment
Patterns
Consider how inspection tasks are distributed. In many organizations,
the most experienced inspectors are assigned to the most critical
products. This seems logical — put your best people on your most
important work. But consider the implicit message sent to the newer
inspectors: the less critical products are all you are trusted with. The
organization’s lowest-stakes work is your ceiling.
The result is predictable. New inspectors, placed on easier work with
lower expectations, develop habits of inattention. They learn to inspect
at the level the organization has signaled is sufficient. When they are
eventually promoted to more critical products — if they ever are — they
bring those diminished habits with them. The organization has trained
them to be mediocre and then wonders why they are.
Supplier Quality Management
The Golem Effect extends beyond your walls. How does your
organization treat its suppliers? Are some suppliers designated as
“strategic partners” while others are treated as interchangeable
vendors? The strategic partners receive collaborative problem-solving,
joint development sessions, and investment in their processes. The
interchangeable vendors receive audits, scorecards, and threats.
Which suppliers improve? Which ones innovate? Which ones catch
defects before shipping? The ones treated as partners — because the
investment signals expectation and trust. The ones treated as
adversaries learn to do the minimum required to pass the next audit.
They game the scorecard rather than improve the system. The Golem Effect
has created precisely the supplier behavior you feared.
Training Programs
Training is perhaps the most visible vector for the Golem Effect.
Organizations that believe in their people invest heavily in training —
not just initial onboarding, but continuous development, cross-training,
and advanced problem-solving skills like Six Sigma or statistical
process control. Organizations that do not believe in their people offer
the minimum training required by regulation and nothing more.
The divergence compounds over time. Well-trained workers develop
deeper understanding of their processes. They detect subtle shifts that
untrained workers miss. They ask better questions. They propose better
solutions. The training gap becomes a competence gap, which becomes a
quality gap — and the organization attributes the gap to the workers
rather than to the investment decision that created it.
Corrective Action Culture
When a defect occurs, what happens? In healthy organizations, the
focus is on the system: what process failed? What control was missing?
How do we prevent recurrence? In Golem-affected organizations, the focus
is on the person: who made the mistake? What disciplinary action is
appropriate? How do we make an example?
The personalization of failure is the Golem Effect made explicit. It
tells every worker that mistakes are career-threatening rather than
information-generating. Under that regime, the rational response is to
hide defects, underreport near-misses, and deflect blame. The
organization’s quality data degrades not because quality is worse, but
because visibility into quality has been intentionally destroyed by the
people who need it most.
The Cost of Low Expectations
The financial impact of the Golem Effect is difficult to isolate
because it is a second-order effect. It does not appear on any ledger.
But its consequences are visible everywhere.
Higher defect rates in teams with low managerial
trust. Research in automotive manufacturing has shown that teams with
high-trust supervisors produce 20-40% fewer defects than teams with
low-trust supervisors, controlling for all other variables.
Higher turnover among skilled workers who sense they
are not valued. Replacing a trained quality inspector costs between 50%
and 200% of their annual salary when you account for recruitment,
training, lost productivity, and the learning curve of their
replacement.
Slower continuous improvement. Kaizen depends on
frontline engagement. Workers who believe their ideas are not valued
stop offering them. The organization’s improvement pipeline narrows to
whatever management can think of — a tiny fraction of what the
collective intelligence of the workforce could generate.
Audit failures. When external auditors arrive, they
sense organizational culture within hours. A workforce that has been
Golem-treated will not help the auditor. They will answer questions
literally, volunteer nothing, and offer no context. The auditor sees a
technically compliant but hollow system — and they are correct.
How to Break the Golem Cycle
Reversing the Golem Effect requires deliberate action at every level
of the organization. It is not enough to simply “think positive.”
Structural changes are required.
Audit Your Expectation
Signals
Walk your production floor with fresh eyes. What signals does your
environment send? Are some areas cleaner, better lit, better equipped
than others — and if so, is the distinction based on product criticality
or on the team that works there? Do some teams get newer tools, better
calibration schedules, more comfortable workstations? Do some
supervisors have open-door policies while others operate behind closed
doors?
Every one of these differences is a message. Make sure the message
you are sending is the one you intend.
Equalize Investment
If you invest in training for your best teams, invest in training for
all teams. If your strategic suppliers get collaborative engagement,
find a way to extend at least some of that engagement to your developing
suppliers. Investment is the most credible signal of expectation. When
people see resources allocated to their development, they understand
that someone believes they are worth developing.
This does not mean treating every team identically. High-performing
teams have earned additional responsibility and autonomy. But
developmental investment — training, coaching, equipment — should be
distributed on the basis of need, not on the basis of past performance
alone. The teams that are struggling need more investment, not less.
Measure System, Not Just
People
When defects increase, the first question should always be “What
changed in the system?” not “Who made the error?” This is not idealism.
It is empiricism. Deming estimated that 94% of quality problems are
attributable to the system, not to individual workers. Blaming people
for system failures is not only unjust — it is inaccurate, and it
activates the Golem Effect in its most destructive form.
Shift your corrective action process to begin with systemic analysis.
Use the 5 Whys, Ishikawa diagrams, and fault tree analysis before you
ever look at individual performance data. In most cases, the systemic
cause will be obvious long before you need to consider whether a
specific person made an error.
Communicate
Explicit Expectations of Excellence
Do not assume that excellence is the default expectation. State it.
Repeat it. Back it with resources. When a new team member joins, tell
them: “We expect you to produce excellent work, and we will invest in
making sure you can.” When a team struggles, tell them: “We know you are
capable of better, and we are going to help you get there.”
The words matter, but the follow-through matters more. Stating high
expectations without providing the resources to meet them is not the
Pygmalion Effect — it is negligence dressed in motivational
language.
Protect Psychological Safety
The Golem Effect thrives in environments of fear. When workers are
afraid to report defects, ask questions, or admit uncertainty, they
retreat to the minimum viable performance. Why take risks in an
environment that punishes failure?
Psychological safety — the belief that one can speak up without fear
of punishment — is the antidote. Organizations with high psychological
safety report more defects, not because they have more, but because
their people are willing to surface them. That visibility is the
foundation of improvement. You cannot fix what you cannot see.
A Personal Observation
Over twenty-five years in quality, I have seen the Golem Effect more
times than I can count. I have walked into factories where an entire
shift was written off by management — and performed accordingly. I have
sat in corrective action reviews where the conversation was 90% about
who to blame and 10% about what to fix. I have watched talented
inspectors leave organizations because they were treated as
interchangeable labor rather than as skilled professionals.
And I have seen the reverse. I have watched organizations transform
struggling teams by the simple act of believing in them — and backing
that belief with training, resources, and genuine attention. The
turnaround is not instantaneous. But it is real, and it is measurable,
and it compounds.
The most important quality instrument in any organization is not the
coordinate measuring machine or the optical comparator. It is the
expectation that managers carry in their heads and transmit through
their actions. If that expectation is low, no inspection regime can
compensate. If that expectation is high — and supported with genuine
investment — the results will exceed what any control chart can
capture.
The Question You Need to Ask
Look at your lowest-performing team, your highest-defect process,
your weakest supplier. Ask yourself: Have they failed because they are
incapable — or because we have never given them a reason to succeed?
If the answer makes you uncomfortable, good. The Golem Effect feeds
on comfort. It grows in the spaces where managers have already decided
who is good enough and who is not. Breaking it requires the courage to
question those decisions — and the discipline to invest in the people
you have already decided are not worth investing in.
Your workforce is not a Golem. It is a collection of human beings who
will rise or fall to the level of expectation you set. Set it high. Mean
it. Fund it. And watch what happens.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing excellence, process optimization,
and quality system design. He has helped organizations across
automotive, aerospace, electronics, and medical device industries build
quality systems that work — not just on paper, but in practice.
