Quality
and the IKEA Effect: When Your Organization Overvalues the Systems It
Built Itself — and the Homegrown Process Everyone Defended Became the
Liability Nobody Could Replace
The
Inspection Room That Nobody Was Allowed to Touch
There’s a mid-sized automotive supplier in central Europe — I won’t
name them, but you’d recognize their parts if you looked under the hood
of your car — that had a final inspection process unlike anything I’d
ever seen. It wasn’t in the control plan. It wasn’t in the work
instructions. It wasn’t even documented anywhere in their QMS. But every
single part that left their facility passed through it.
The room had been set up fifteen years earlier by a quality engineer
named Tomas, who had since retired. Tomas had been brilliant — genuinely
brilliant. He’d designed a custom gauging fixture from scratch, wired
together a proprietary data collection system using components from
three different manufacturers, and written the analysis algorithms
himself in a spreadsheet that only he understood. The system worked. For
fifteen years, it caught defects that the standard inspection process
missed.
When I arrived as a consultant to help them prepare for a customer
audit, I asked about the room. The quality manager, Martin, beamed with
pride. “We built that ourselves,” he said. “It’s our secret weapon.”
I asked to see the validation records. There were none. The
calibration certificates? Nonexistent. The measurement system analysis?
Never done. The training records for the operators who used it?
Informal, at best — Tomas had trained them verbally, one by one, over
the years.
“We should probably document it,” Martin admitted. “But it works so
well. Why mess with something that works?”
Here’s why: because Tomas was gone. The spreadsheet had a macro that
nobody could decode. Two of the gauging components were obsolete and no
longer manufactured. And the last operator who fully understood the
fixture had transferred to another plant six months ago.
The room they had built themselves — the room they were fiercely
proud of — had become a single point of failure wrapped in nostalgia and
protected by the IKEA effect.
What the IKEA Effect Really
Means
The IKEA effect is a cognitive bias first documented by researchers
Michael Norton, Daniel Mochon, and Dan Ariely in 2012. The name comes
from the Swedish furniture company: people who assemble their own IKEA
furniture consistently overvalue it compared to identical furniture
assembled by someone else. A wobbly bookshelf you built with your own
hands feels more valuable than a sturdier one that arrived
pre-assembled.
The research is rigorous and replicable. Across multiple experiments,
participants assigned significantly higher monetary value to things they
had a hand in creating. Origami folded by amateurs was rated as more
valuable by the folders themselves than by independent observers.
Custom-built LEGO sets, self-designed T-shirts, even self-assembled
boxes — the pattern held. Labor leads to love.
And the effect is strongest when the effort is moderate. Too easy,
and there’s no emotional investment. Too difficult, and frustration
overwhelms pride. But when people expend just enough effort to feel
competent, they bond with the result in ways that defy rational
evaluation.
This is a quality problem of the first order.
How the IKEA Effect
Infects Quality Systems
Quality organizations are uniquely vulnerable to this bias because
quality professionals are, by nature, builders. They build inspection
systems. They build control plans. They build failure mode analyses.
They build corrective action programs. And because they built them —
often under enormous pressure, often with limited resources, often
through sheer force of will — they fall in love with them.
I’ve seen this play out in ways that range from amusing to
catastrophic.
The Homegrown Tracking
Spreadsheet
A medical device company I worked with had a CAPA tracking system
built entirely in Excel. It had 47 tabs, 312 named ranges, and a
color-coding system that only the original creator understood. It took
three clicks and a password to add a new corrective action. It couldn’t
generate reports without crashing. It couldn’t be audited without the
creator sitting beside the auditor to explain what each column
meant.
But the team fought tooth and nail to keep it. “We built this from
nothing,” the quality engineer told me. “It does everything we
need.”
It didn’t. It couldn’t track overdue actions. It couldn’t flag
recurring issues. It couldn’t produce the trend analysis their customer
was asking for. But it was theirs, and that was enough.
The Custom SPC Solution
An aerospace supplier had developed their own SPC software in-house.
Not a configured commercial package — custom code, written by a team
that had long since moved on. The software ran on a server running an
operating system that hadn’t been supported in years. The source code
was stored on a single hard drive in a drawer.
When I suggested they migrate to a commercial SPC platform, the
reaction was visceral. “Our system is better,” the plant manager
insisted. “It was designed specifically for our processes.”
I asked what made it better. He couldn’t articulate a single specific
advantage. What he could articulate, at length, was how hard the team
had worked to build it. The late nights. The weekends. The breakthrough
moment when they got the real-time charting to work.
He wasn’t describing the software’s capability. He was describing his
emotional attachment to the effort of creating it.
The “Our Way” Inspection
Protocol
Perhaps the most dangerous manifestation I’ve encountered was at a
pharmaceutical packaging company that had developed its own visual
inspection protocol for particulate contamination. The protocol had
evolved organically over a decade, shaped by dozens of individual
decisions and workarounds. It was idiosyncratic, inconsistent, and — as
a blinded study later revealed — only marginally better than random
chance at detecting actual contaminants.
But the inspection team had complete confidence in it. They had built
it. They had refined it. They had trained each other on it. And when the
regulatory auditor questioned its validity, they responded not with data
but with indignation.
The auditor wasn’t impressed by indignation.
The Three Symptoms of
IKEA-Effect Quality
You can spot the IKEA effect in your quality system by watching for
three patterns:
1. Disproportionate defensiveness. When someone
questions a process, tool, or system, the response is emotional rather
than analytical. The defense centers on the effort that went into
building it, not on evidence of its effectiveness. “We spent two years
developing that” is an IKEA-effect response. “Here’s the data showing it
reduces defects by 34%” is not.
2. Rejection of alternatives without evaluation.
When a new tool, method, or system is proposed, it’s dismissed before
being assessed. “We already have something that works” is the reflex
response, and no amount of demonstration or evidence shifts the
position. The existing system isn’t being compared to the alternative —
it’s being protected from the comparison.
3. Maintenance blindness. The homegrown system
receives less and less maintenance over time, but this deterioration is
either not noticed or rationalized. The Excel tracker gets slower but
nobody migrates it. The custom gauging fixture drifts but nobody
recalibrates it. The proprietary process becomes dependent on retiring
knowledge but nobody documents it. The love of creation has been
replaced by the neglect of ownership.
Why This Bias
Is Especially Dangerous in Quality
Most cognitive biases affect judgment. The IKEA effect affects
something more fundamental: it affects what we’re willing to see.
When you’ve built a quality system yourself, you don’t just overvalue
it — you stop being able to evaluate it objectively. You stop noticing
its flaws because noticing its flaws would mean admitting that your
effort was misdirected. You stop comparing it to alternatives because
comparing it to alternatives would mean accepting that someone else
might have built something better.
In quality management, this creates a specific and dangerous dynamic:
the systems that need the most improvement are often the ones most
fiercely defended, because they’re the ones that required the most
effort to build. The most outdated processes are the ones most resistant
to change, because they carry the most emotional investment.
And here’s the cruelest twist: the IKEA effect is strongest for
things that are almost good enough. A truly terrible system is easy to
replace — nobody’s proud of it. A truly excellent system doesn’t need
replacing. But a system that’s 70% effective, that represents hundreds
of hours of effort, that works well enough to feel like an achievement
but not well enough to be truly reliable? That’s the system people will
defend to the death.
The Antidote: Structural
Humility
You can’t think your way out of the IKEA effect. It’s not a knowledge
problem — it’s an emotional one. The solution isn’t to recognize the
bias (though that helps) but to build structures that compensate for
it.
Separate Building from
Evaluating
The people who built a system should not be the sole judges of
whether it’s still fit for purpose. This is basic quality thinking — you
don’t self-audit — but it’s remarkable how often it’s violated for
internally developed tools and processes.
Establish a regular review cycle where quality systems are evaluated
by people who weren’t involved in their creation. This isn’t about
expertise; it’s about objectivity. A fresh pair of eyes can see what
love has made invisible.
Benchmark Relentlessly
Don’t compare your homegrown system to nothing — compare it to the
best available alternative. Every year, conduct an honest assessment: if
we were starting from scratch today, would we build this same system, or
would we choose something different?
If the answer is “something different,” the IKEA effect is the only
thing keeping the current system in place.
Document the
Rationale, Not Just the Procedure
When you build a quality system, document not just what it does but
why you made each design decision. What alternatives did you consider?
What trade-offs did you accept? What limitations did you
acknowledge?
This documentation becomes invaluable later, because it lets you
evaluate the system against its original design intent rather than
against the emotional memory of building it. It transforms “we built
this and it’s good enough” into “we built this to solve problem X, and
here’s how well it’s solving it.”
Plan for Obsolescence From
Day One
Every quality system, tool, and process should have a planned
retirement date or a scheduled comprehensive reassessment. Not because
everything needs to be replaced regularly, but because building in the
expectation of change reduces the emotional attachment to
permanence.
“We built this to last three years, and then we’ll reassess” produces
a very different psychological relationship than “we built this, and
it’s our system forever.”
The Hard Truth About
Building Things
I eventually helped that automotive supplier replace Tomas’s
inspection room. It took six months. We implemented a commercial
measurement system, validated it properly, calibrated it on schedule,
trained the operators with documented procedures, and built in the
redundancy that the original setup lacked.
The new system caught more defects than Tomas’s ever had. It produced
data that auditors could trace from measurement to report without a
single verbal explanation. It ran on supported hardware with available
spare parts.
But here’s what I remember most: on the day we decommissioned Tomas’s
fixture, Martin stood in the room for a long time, alone, just looking
at it. He didn’t say anything. He didn’t need to. I could see it in his
face — not just the loss of a system, but the loss of something he had
helped build. Something that had made him feel capable and resourceful
and proud.
That feeling is real. It’s valid. The IKEA effect exists because
building things is genuinely meaningful. The effort we invest does
create real emotional value.
But emotional value isn’t quality value. And in the gap between what
we love about the systems we’ve built and what those systems actually
deliver, defects find their hiding places.
Tomas built something remarkable for its time. But his time was
fifteen years ago, and quality doesn’t care about nostalgia. Quality
cares about whether the system works today, whether it will work
tomorrow, and whether it can be proven to work by someone who never met
the person who built it.
The best quality systems aren’t the ones we’re most proud of. They’re
the ones we can most objectively evaluate — and most willing to replace
when the evidence says we should.
That’s not a failure of effort. That’s the highest form of respect
for the effort that came before.
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, guided companies through IATF 16949 and ISO 9001
certifications, and helped organizations build cultures where excellence
is a habit, not an accident. Peter specializes in bridging the gap
between technical quality requirements and the human dynamics that
determine whether systems succeed or fail.
