Quality
and the IKEA Effect: When Your Organization Falls in Love With Its Own
Processes — and Rejects Better Solutions Because They Came From
Somewhere Else
There is a peculiar thing that happens when human beings
build something with their own hands. They start to believe it’s worth
more than it actually is.
In 2011, a group of behavioral economists at Harvard published a
paper that would change how we understand human valuation. Michael
Norton, Daniel Mochon, and Dan Ariely demonstrated that people who
assembled IKEA furniture themselves valued it significantly higher than
identical furniture assembled by someone else. They called it the IKEA
Effect, and it explained something fundamental about the human brain:
we overvalue what we help create.
The effect has been replicated dozens of times since — with LEGO
sets, with origami, with business plans, with investment portfolios. And
every single time, the result is the same: when you put effort into
building something, your brain rewards you by inflating its perceived
value far beyond its objective worth.
If you’ve spent any time in manufacturing, you already know where
this is going.
The
Process Your Team Built Is Never the Process Your Team Should Have
Built
Walk into any factory that has been operating for more than five
years, and you will find processes that were designed by the people who
work there. Work instructions written by operators. Inspection sheets
created by quality engineers. Control plans developed by launch teams.
Setup procedures improvised by technicians and gradually formalized into
standard work.
These processes represent hundreds — sometimes thousands — of hours
of collective effort. They carry the fingerprints of the people who
built them. And because of the IKEA Effect, those same people will
defend them with a ferocity that has absolutely nothing to do with how
good the processes actually are.
I watched this play out at an automotive supplier in the Midwest. The
plant had a complex manual assembly operation for a sensor housing. The
process had been designed by the original launch team eight years
earlier, and it had been tweaked, adjusted, and patched so many times
that nobody could remember what the original intent had been. The cycle
time was 47 seconds. The defect rate was 1.8 percent. The rework station
had two full-time operators.
A new engineering manager joined the team and, after studying the
operation, proposed a redesign based on a similar process he had
implemented at his previous company. The new approach would reduce cycle
time to 31 seconds and, based on the data from his prior plant, would
cut the defect rate to below 0.3 percent. He presented the proposal with
full documentation, time studies, and a pilot plan.
The team rejected it in under twenty minutes.
Not because the data was wrong. Not because the proposal was flawed.
But because, as one operator put it: “We built this process. We know it.
It works.” The engineering manager had walked into a room full of people
who had invested eight years of intellectual and emotional capital into
a process, and he had asked them to throw it away for something they
didn’t build.
The IKEA Effect had turned a perfectly reasonable improvement
proposal into a personal attack.
Why the IKEA
Effect Is So Dangerous in Quality
The IKEA Effect doesn’t just make people attached to their processes.
It creates three specific pathologies that can quietly destroy a quality
system from the inside.
Pathology One: The
Not-Invented-Here Syndrome
When your team overvalues its own work, it automatically undervalues
work that comes from outside. Industry best practices, competitor
benchmarks, supplier recommendations, consultant proposals — all of
these get filtered through a lens of suspicion. “That might work there,
but our situation is different.” “We tried something like that once and
it didn’t work.” “They don’t understand our process.”
The Not-Invented-Here syndrome is the IKEA Effect’s most visible
symptom, and it’s one of the most expensive blind spots a quality
organization can have. Because the truth is that most quality problems
have been solved before, by someone else, in a different factory, in a
different industry, sometimes decades ago. The solution exists. The data
exists. The proof exists. But your organization won’t adopt it because
it didn’t invent it.
I saw this at a medical device manufacturer that spent eighteen
months developing an in-house statistical process control system. The
system was mediocre — it could plot control charts and calculate Cpk
values, but it couldn’t handle multivariate analysis, it had no
automated alerting, and its reporting was a manual export to Excel that
took a quality engineer four hours every Monday morning. When the
quality director proposed buying an off-the-shelf SPC platform that
could do everything the in-house system did and more — for less money
than they were spending on maintenance — the IT team pushed back hard.
They had built the system. It was theirs. And the idea that a commercial
product could do it better felt like a rejection of their
competence.
The company eventually adopted the commercial platform. It took a
change in leadership to make it happen. And within three months, the
quality team had recovered over twenty hours per week in reporting time,
and the automated alerting had caught two process shifts that the old
system would have missed.
Pathology Two: The Sunken
Improvement
The IKEA Effect also distorts how organizations evaluate their own
improvement efforts. When a team invests weeks or months designing a new
process, writing procedures, training operators, and running pilots, the
effort itself becomes a source of attachment. The process isn’t just a
process anymore — it’s a repository of the team’s time, energy, and
creative investment.
This becomes dangerous when the process doesn’t work as well as
expected. Instead of objectively evaluating the results and making a
go/no-go decision, the team finds reasons to keep going. “We just need
more time.” “The operators need more training.” “The data isn’t
representative yet.” These might be legitimate arguments, but when
they’re driven by the IKEA Effect rather than by evidence, they become
rationalizations for throwing good money after bad.
A Tier 1 automotive supplier I worked with spent seven months
implementing a homegrown machine vision inspection system for a critical
surface defect. The system had been designed by their internal
engineering team, and it was achieving a detection rate of 82 percent —
well below the 95 percent target they had set for themselves. A
commercial vision system vendor offered a solution that could be
installed in three weeks and had a demonstrated detection rate of 97
percent at a similar plant.
The internal team argued passionately for another three months of
development. They had invested too much to abandon the project. The
detection rate was “improving.” They just needed better lighting and a
different camera angle. The plant manager, to his credit, looked at the
data and made the hard call. The commercial system was installed. The
internal project was retired.
Three of the four engineers who had worked on the internal system
resigned within six months. They didn’t leave because the commercial
system was better. They left because they had been told — implicitly but
unmistakably — that something they had built with their own hands wasn’t
good enough. The IKEA Effect doesn’t just distort organizational
decision-making. It creates emotional bonds that, when broken, can
damage team cohesion and morale.
Pathology
Three: The Immunity to External Standards
Perhaps the most insidious consequence of the IKEA Effect is the way
it makes organizations resistant to external standards — even when those
standards are demonstrably superior.
ISO 9001, IATF 16949, AS9100 — these standards exist because decades
of quality engineering have produced a body of knowledge about what
works. They represent the distilled wisdom of thousands of organizations
and millions of quality events. And yet, in every organization I have
ever worked with, there is a moment — sometimes a quiet one, sometimes a
loud one — when someone says: “We already do this. Our way is just as
good.”
Sometimes that’s true. Often it isn’t. But the IKEA Effect makes it
impossible for the person saying it to tell the difference, because
their own process has been inflated in their perception to meet or
exceed the standard, regardless of what the evidence actually shows.
I audited a plant once where the quality manager proudly showed me
their corrective action system. It was a collection of Excel
spreadsheets, shared network drives, and email chains that had evolved
organically over a decade. He was genuinely convinced it was superior to
any CAPA software on the market. When I asked him to show me the average
time from defect detection to corrective action implementation, he
couldn’t find the data. When I asked for the open CAPA list, he had to
search through three different folders and two email inboxes. When I
asked for evidence of effectiveness verification, he admitted they
“usually” checked but didn’t always document it.
His system was a mess. But he had built it himself, and in his mind,
it was a palace.
The Neuroscience of Building
Understanding why the IKEA Effect exists doesn’t require a degree in
psychology. It requires understanding one simple fact about the human
brain: effort creates ownership, and ownership creates
loyalty.
When you invest time and cognitive energy into creating something — a
process, a document, a system, a solution — your brain registers that
investment as a form of self-extension. The thing you built becomes part
of your identity. It’s not just a quality procedure; it’s your
quality procedure. It’s not just a control plan; it’s the control
plan you designed. And when someone suggests that your creation
could be improved — or worse, replaced — your brain processes that
suggestion as a form of personal criticism.
This is why process improvement initiatives so often fail in
organizations with strong internal cultures. It’s not that the
improvements are bad. It’s that the improvements require people to
abandon things they’ve built, and abandoning something you’ve built
feels like abandoning a part of yourself.
The effect is amplified in manufacturing environments where processes
are developed through trial and error — through the school of hard
knocks that is the shop floor. An operator who has spent five years
refining a setup technique doesn’t just know that technique. She
is that technique, in the sense that her professional identity
is intertwined with it. Ask her to adopt a different approach, and
you’re not asking her to change a process. You’re asking her to change
who she is at work.
Five
Strategies for Overcoming the IKEA Effect in Quality
Recognizing the IKEA Effect is the first step. Overcoming it requires
deliberate, sustained effort. Here are five strategies I’ve seen work in
practice.
Strategy
One: Separate the Builder from the Building
When introducing an external solution or a new standard, frame it as
an evolution, not a replacement. Don’t say: “We’re replacing your
process.” Say: “Your process got us this far. Now we’re building on that
foundation.” Acknowledge the effort that went into the existing approach
explicitly and genuinely. People need to hear that their investment was
valued before they can let go of the product of that investment.
At the medical device manufacturer I mentioned earlier, the quality
director who pushed for the commercial SPC platform made a critical
mistake: she didn’t acknowledge the IT team’s work. She presented the
business case as if the decision were purely rational, purely financial.
It was a decision that needed to be made. But by ignoring the emotional
dimension, she made the decision harder than it needed to be and
alienated a team she would need for the implementation.
Strategy Two:
Make Objective Comparison Automatic
The IKEA Effect thrives in the absence of objective comparison. When
the only benchmark for your process is your process, it’s easy to
believe it’s excellent. Build systematic benchmarking into your quality
management system — not as a one-time event, but as a continuous
practice. Compare your processes to industry standards, competitor data,
supplier capabilities, and published best practices. Make the comparison
visible, regular, and non-negotiable.
One automotive supplier I worked with instituted a quarterly
“external benchmark review” where every process owner had to present
their process metrics alongside at least two external benchmarks. The
rule was simple: if you couldn’t find an external benchmark, you had to
explain why your process was so unique that no comparison was possible.
In three years of running this practice, no process owner ever
successfully made that argument. The benchmark reviews became one of the
most powerful drivers of continuous improvement in the plant — not
because they introduced new ideas, but because they made it impossible
to hide behind the inflated self-assessment that the IKEA Effect
produces.
Strategy Three:
Co-Create, Don’t Dictate
When implementing external standards or new processes, involve the
people who will be affected in the adaptation and implementation. Don’t
hand them a finished product. Give them a framework and let them fill in
the details. The IKEA Effect works both ways: if you want people to
value a new process, let them help build it.
This doesn’t mean letting people water down standards or ignore
requirements. It means giving them genuine ownership over the
implementation — the sequence, the pacing, the local adaptations, the
training approach. When people contribute to the construction of a new
system, they begin to extend their identity around it. The new system
becomes theirs, and the resistance evaporates.
A plant I consulted with was implementing IATF 16949 for the first
time. The quality manager made the mistake of writing all the new
procedures himself and then presenting them to the department heads for
implementation. The pushback was enormous. Every department found
reasons why the new procedures “wouldn’t work in our area.” After six
months of frustration, the quality manager changed his approach. He
presented the IATF requirements and asked each department to write their
own procedures to meet them. He provided templates, examples, and
coaching — but the actual writing was done by the people who would have
to follow the procedures.
Implementation time dropped from six months of resistance to eight
weeks of enthusiastic adoption. The procedures that the departments
wrote were, in most cases, nearly identical to the ones the quality
manager had originally proposed. But because the departments had written
them themselves, they owned them. The IKEA Effect, properly channeled,
had become an asset instead of an obstacle.
Strategy Four: Ritualize
the Letting Go
Many manufacturing cultures celebrate creation but have no ritual for
retirement. A new process is launched with fanfare. An old process is
quietly discontinued, often without acknowledgment. This asymmetry
reinforces the IKEA Effect by suggesting that creation is valuable and
retirement is loss.
Create formal retirement rituals. When an old process is replaced,
acknowledge its service. Document what it achieved, what it taught the
team, and why it’s being retired. Celebrate the people who built it and
maintained it. A simple practice I’ve seen work: every process
retirement meeting starts with five minutes of “what this process did
for us” before moving to the transition plan.
This feels soft. It is soft. It’s also one of the most effective
change management techniques I’ve ever seen, because it addresses the
emotional reality that the IKEA Effect creates. People need permission
to let go of what they’ve built. A retirement ritual gives them that
permission.
Strategy
Five: Build a Culture of External Learning
The strongest antidote to the IKEA Effect is a culture that genuinely
values external learning — one where the default assumption is that
someone, somewhere, has already solved your problem better than you
can.
This culture has to be modeled from the top. When plant managers,
quality directors, and engineering leads openly reference external
sources — industry publications, conference presentations, supplier
expertise, competitor practices — they signal that the organization’s
own ideas are not the ceiling of its ambition. They signal that learning
from others is not a weakness but a strength.
One of the most effective quality leaders I’ve ever worked with
started every Monday morning meeting with a five-minute “what I learned
this week” segment. He would share an article, a conference
presentation, a conversation with a peer at another plant, or a case
study from a completely different industry. He never presented these as
prescriptions. He presented them as provocations: “Here’s something
interesting. How might this apply to us?”
Over time, this practice transformed the plant’s culture. Operators
started bringing in ideas they’d seen at trade shows. Engineers started
benchmarking against industries outside automotive. The quality team
started subscribing to journals and participating in professional
networks. The plant went from being an island of internal invention to
being a node in a network of continuous external learning.
And the IKEA Effect didn’t disappear — it never does — but it lost
its grip. The team still felt ownership of their processes. They still
took pride in their work. But they no longer confused the pride of
creation with the proof of excellence. They learned to love what they
had built while remaining open to the possibility that someone,
somewhere, had built something better.
The Paradox at the Heart of
Quality
Here is the deepest irony of the IKEA Effect in quality management:
the very organizations that need external ideas the most are the ones
most resistant to them. The plant with the highest defect rate is the
one most likely to defend its processes. The team with the worst
performance is the one most likely to reject outside help. The manager
with the most outdated approach is the one most likely to insist that
“our way works fine.”
This isn’t ignorance. It isn’t stubbornness. It’s a fundamental
feature of human psychology — a feature that served us well for most of
our evolutionary history, when the things we built with our own hands
literally kept us alive, and when trusting external ideas could be
genuinely dangerous.
But in a manufacturing world where best practices evolve monthly,
where industry standards are updated annually, and where the competitive
landscape shifts faster than any single organization can track through
internal innovation alone, the IKEA Effect is a liability. It’s a
cognitive bias that feels like loyalty, looks like dedication, and acts
like a brake on every improvement initiative you’ll ever launch.
The organizations that master quality in the long term are not the
ones that build everything themselves. They’re the ones that build what
they must, borrow what they can, and never let the pride of creation
blind them to the evidence of results.
Your process is not your child. It’s a tool. And the moment you start
loving it more than you love the outcomes it produces, the IKEA Effect
has already won.
Peter Stasko is a Quality Architect with over 25
years of experience in automotive, industrial, and electronics
manufacturing. He specializes in building quality systems that balance
rigorous standards with practical shop-floor reality — and in helping
organizations recognize when their attachment to their own processes has
become the biggest obstacle to the excellence they’re trying to
achieve.
