There is a peculiar thing that happens when people build something
with their own hands. They fall in love with it. Not gently, not
reasonably — they fall hard. They overestimate its quality, inflate its
value, and defend it against all criticism, not because it is good, but
because it is theirs. Psychologists call this the IKEA Effect, named
after the Swedish furniture company that figured out something
deceptively powerful: when customers assemble their own furniture, they
like it more. Not because the furniture is better. Because their sweat
is in it.
In the world of quality management and manufacturing, this effect is
not a curiosity. It is a landmine. And your organization has probably
stepped on it more than once.
The IKEA Effect Explained
The IKEA Effect was formally documented in 2011 by researchers
Michael Norton, Daniel Mochon, and Dan Ariely. Their experiments were
elegant in their simplicity. Participants who built their own IKEA
boxes, folded their own origami, or assembled their own Lego sets
consistently valued their creations far higher than identical items
assembled by others. The effect was robust. It was replicable. And it
was deeply irrational.
The researchers found that the effect required two conditions: you
had to successfully complete the task, and you had to exert personal
effort. Half-finished products generated no pride. Tasks that were too
easy generated no attachment. But when people invested real effort and
crossed the finish line, something clicked in their psychology. The
product transformed from an object into an extension of the self.
Criticism of the product became criticism of the person.
Now translate that to your factory floor, your quality department, or
your engineering team.
When the Effect
Strikes in Manufacturing
Consider the following scenario, which plays out in manufacturing
organizations every single day.
Your engineering team spends six months developing a custom quality
inspection system. It is built in-house, tailored to your specific
production line, and integrated with your existing infrastructure. The
team is proud. They should be — they worked hard, overcame obstacles,
and delivered something functional.
Then an external auditor reviews the system and points out that a
commercially available solution would do the same job better, faster,
and at lower total cost of ownership. The team’s response is swift and
visceral: the external solution doesn’t understand our unique
requirements. It won’t integrate properly. It doesn’t capture the nuance
of our process. Our system is better because it was built for us, by
us.
Is it? Maybe. Maybe not. But the team cannot evaluate that question
objectively because they are under the spell of the IKEA Effect. They
built it. Therefore, it is valuable. Therefore, it must be defended.
This is not a hypothetical. I have watched organizations cling to
homemade statistical process control spreadsheets while world-class SPC
software sat unused on a shelf. I have seen quality engineers defend
manual inspection checklists they designed themselves while automated
vision systems gathered dust. I have listened to plant managers explain
why their homegrown corrective action tracking system was superior to
proven, validated platforms — systems that had been refined across
thousands of implementations in similar industries.
The reasoning was always the same: ours is different. Ours is
special. Ours was built for this exact purpose. What they meant was:
ours is ours.
The Three Faces
of the IKEA Effect in Quality
The IKEA Effect in quality management does not manifest as a single
problem. It shows up in three distinct and equally dangerous forms.
1. The Not-Invented-Here
Defense
When your team has built something, they will reject alternatives
regardless of merit. This goes beyond healthy skepticism. Healthy
skepticism says: let us evaluate this alternative rigorously and compare
it to what we have. The IKEA Effect says: we do not need to evaluate it
because what we have is already the best. The evaluation never happens.
The comparison is never made. The status quo persists not because it is
superior, but because it is self-made.
This is particularly dangerous in quality because the cost of
inferior systems is not immediately visible. A mediocre inspection
system does not cause a spectacular failure on day one. It causes a
slow, steady drift — a few defects missed here, a few false alarms
there, a gradual erosion of confidence in the quality process. By the
time the damage is measurable, years may have passed, and the team’s
attachment to their creation will have calcified into institutional
resistance.
2. The Effort Justification
Trap
The IKEA Effect makes people conflate effort with value. If we spent
2,000 hours building it, it must be worth 2,000 hours. This is effort
justification — a close cousin of the sunk cost fallacy, but with an
emotional dimension that makes it even harder to escape.
In quality management, this shows up when organizations refuse to
replace internally developed systems because of the investment already
made. We cannot abandon this — think of all the work that went into it.
The work is treated as evidence of the system’s quality rather than as a
cost that has already been incurred and cannot be recovered.
The rational question is simple: given where we are today, what is
the best path forward? The IKEA Effect replaces that question with a
different one: given what we have already invested, how can we justify
continuing? The first question leads to improvement. The second leads to
stagnation.
3. The Immunity to Feedback
Perhaps the most insidious consequence of the IKEA Effect is the way
it shields self-made systems from legitimate criticism. When an external
system produces poor results, the organization can evaluate the feedback
objectively: this system is not working; we should replace it. When an
internal system produces poor results, the organization filters the
feedback through a protective lens: the system is fine; the inputs were
wrong, or the operators were not trained properly, or the conditions
were unusual.
The system itself becomes immune to criticism because criticizing the
system feels like criticizing the people who built it. And in a very
real psychological sense, it is. The IKEA Effect fused the creator’s
identity with the creation. You are not attacking a quality management
system. You are attacking someone’s professional self-worth.
This is how organizations end up with quality systems that everyone
knows are suboptimal but nobody is willing to replace. Not because the
evidence is ambiguous. Because the emotions are overwhelming.
Real-World Consequences
The IKEA Effect is not just an academic theory. It has real,
measurable consequences in manufacturing environments.
Consider the case of a mid-size automotive supplier that developed
its own layer of process documentation on top of the standard IATF 16949
requirements. The quality team spent months creating custom forms,
tailoring procedures, and building a documentation architecture that
they believed was uniquely suited to their operation. When a customer
audit identified nonconformities, the team’s first response was not to
fix the problems but to defend the system. The forms are fine — the
auditor just doesn’t understand our approach. The nonconformities were
eventually addressed, but the underlying system was never questioned.
Three years later, the same nonconformities reappeared. The system had
been designed around the team’s assumptions, not around the actual
failure modes of the process, and those assumptions were never
challenged because challenging them meant challenging the team’s
creation.
Or consider the medical device manufacturer that built its own
complaint handling database. The system worked — barely. It was slow,
required manual workarounds, and lacked basic reporting capabilities
that off-the-shelf complaint management software provided out of the
box. But the quality engineering team had built it over several years,
and they defended it with the fervor of parents defending a child. When
regulatory inspectors cited the system as inadequate, the team’s
response was to add more features — more custom code, more complexity,
more of their own effort invested in a system that was fundamentally the
wrong architecture. They were solving the wrong problem. The problem was
not that their system lacked features. The problem was that their system
was the wrong tool for the job. But admitting that meant admitting that
hundreds of hours of their work had been misdirected, and the IKEA
Effect would not allow that admission.
The Institutional Dimension
The IKEA Effect is powerful enough when it operates on individuals.
But in organizations, it compounds. It becomes institutional.
When an entire department has contributed to building a system, the
collective attachment is even stronger than any individual’s. Replacing
the system means telling every person who contributed that their work is
being set aside. Even if the new system is objectively better, the
emotional cost of the transition is enormous. People feel replaced. They
feel their expertise is being questioned. They feel irrelevant.
Smart organizations manage this transition carefully. They do not
frame it as replacing the old system because the old system was bad.
They frame it as building on the foundation that the team created. They
involve the original builders in the selection and implementation of the
replacement. They honor the effort while acknowledging that the
requirements have evolved.
This is not deception. It is an honest recognition that the old
system served its purpose at the time, and the organization’s needs have
grown beyond what a homegrown solution can support. The builders’ effort
was valuable. The system’s time has passed. Both things can be true
simultaneously.
Breaking the Spell
So how do you recognize and counteract the IKEA Effect in your own
organization? There is no single antidote, but there are practical
strategies that work.
First, build awareness. When your team responds to criticism of an
internally developed system with emotional intensity rather than
analytical rigor, name what is happening. This is not about the quality
of our work. This is about our attachment to our work. Those are
different things. Simply naming the bias can create enough distance for
rational evaluation.
Second, separate the builders from the evaluators. The people who
built a system should not be the sole judges of whether it should be
replaced. This is not because they are dishonest or incompetent. It is
because they are human, and humans cannot objectively evaluate things
they created. Bring in external reviewers, cross-functional teams, or
consultants who have no emotional investment in the existing system.
Third, benchmark relentlessly. Compare your internal systems against
external alternatives on objective criteria: speed, accuracy, cost,
scalability, maintainability, compliance. If your internal system wins
on the merits, keep it. If it loses, replace it. The key is to make the
comparison honestly and to define the criteria before you start
evaluating, not after.
Fourth, normalize replacement. Build into your quality management
system the expectation that tools, processes, and systems will be
periodically reassessed and replaced when better alternatives become
available. Make it clear that replacing a system is not a judgment on
the people who built it. It is a recognition that the organization is
evolving and that the tools must evolve with it.
Fifth, and perhaps most importantly, apply the same scrutiny to your
own work that you would apply to a vendor’s. If a supplier proposed a
quality management system with the limitations that your internal system
has, would you accept it? If a contractor delivered a process with the
same documentation gaps, would you approve it? If the honest answer is
no, then you have your answer about your internal system too.
The Paradox of Ownership
Here is the deepest irony of the IKEA Effect in quality management:
the same psychological mechanism that makes people overvalue their own
creations is also the mechanism that drives genuine improvement. People
who feel ownership over their work care more about it. They invest more.
They iterate more. They take more pride in excellence. Ownership is not
the enemy of quality — it is one of quality’s most powerful engines.
The problem is not ownership itself. The problem is unexamined
ownership. Ownership without humility. Ownership that refuses to
acknowledge its own limitations. The goal is not to eliminate the
emotional connection between creators and their creations. The goal is
to build enough self-awareness that the connection enhances quality
rather than distorting it.
The best quality engineers I have worked with share a common trait:
they are proud of what they build and willing to replace it when
something better comes along. They hold their creations with an open
hand. They invest their effort fully and then release their attachment
when the evidence demands it. This is not easy. It requires emotional
maturity that most organizations do not cultivate and most individuals
do not develop on their own.
But it is the difference between an organization that improves
continuously and one that defends its status quo with increasing
desperation. The IKEA Effect tells you that what you built is precious.
Quality demands that you ask: is it good enough?
Those are different questions. And the difference between them is the
difference between an organization that grows and one that merely
ages.
The Cost of Not Knowing
Organizations that understand the IKEA Effect can account for it.
They can build decision-making processes that compensate for the bias.
They can create cultures where replacing an internal system is treated
as growth rather than failure.
Organizations that do not understand the IKEA Effect are at its
mercy. They will overinvest in internal solutions, reject superior
alternatives, and rationalize mediocrity as uniqueness. They will watch
their competitors adopt better tools, faster processes, and more
effective quality systems while they explain to themselves why their
homemade solution is somehow special.
It is not special. It is yours. And in quality management, those are
not the same thing.
The next time your team defends an internal system with passion
rather than data, ask yourself: are we defending quality, or are we
defending the feeling of having built something? If the answer is the
latter, the IKEA Effect has you. And the first step to escaping it is
admitting that you are caught.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing excellence, process optimization,
and quality management systems. He writes about the intersection of
human psychology and industrial quality — because the most interesting
defects are the ones that live between the ears before they show up on
the production line.
