Quality
and the IKEA Effect: When Your Organization Falls in Love With Its Own
Solutions — and the Tools, Processes, and Systems You Built Yourself
Become the Ones You Can Never Replace
The Shelf That Changed
Everything
In 2011, a team of researchers at Harvard Business School published a
paper that would reshape how we understand human valuation. Michael
Norton, Daniel Mochon, and Dan Ariely demonstrated something that anyone
who has ever assembled flat-pack furniture already suspected: people
place a disproportionately high value on things they helped create. They
called it the IKEA Effect.
The experiments were elegant in their simplicity. Participants who
built their own IKEA boxes valued them 63% higher than identical
pre-assembled boxes. People who assembled Lego cars refused to sell them
for less than what they would pay for professionally assembled versions.
The act of creation — even awkward, imperfect creation — forged an
emotional bond that defied rational assessment.
The quality profession has aIKEA Effect problem. And it is quietly
destroying your ability to improve.
The
Homegrown Quality System That Nobody Can Touch
Let me tell you about a company I worked with — a mid-sized
automotive supplier in Central Europe that had built its own quality
management system over the course of fifteen years. It started
innocently enough. In 2008, their quality manager — let’s call him Tomas
— created an Excel-based system for tracking nonconformances. Over the
years, Tomas added modules: a CAPA tracker, a supplier scorecard, an
audit management dashboard, a calibration reminder system, a customer
complaint log. Each addition was a response to a real need. Each module
worked, more or less.
By the time I arrived in 2023, the system had grown into a sprawling
network of 47 interconnected Excel workbooks, some with over 50 tabs,
linked through a web of VLOOKUPs, macros, and shared network drives. It
took new quality engineers three months to learn how to navigate it. It
crashed weekly. Data entry errors were endemic because the same
information had to be manually entered in four different places. The
system could not generate the reports their largest customer was now
requiring. It could not integrate with the new ERP system the company
had just purchased.
But here is the remarkable part: every time someone suggested
replacing it with a proper QMS software platform, the resistance was
volcanic.
“We built this system ourselves,” the quality team would say. “It
works for us. You can’t just throw away fifteen years of
development.”
They were right about one thing: you cannot just throw away fifteen
years of development. But they were catastrophically wrong about what
those fifteen years had actually produced. What they had was not a
quality management system. What they had was a monument to the IKEA
Effect — a system they loved because they had built it, not because it
was good.
Why the IKEA
Effect Is So Dangerous in Quality
The IKEA Effect operates through three psychological mechanisms, and
each one maps precisely onto behaviors I have observed in quality
organizations across every industry I have worked in.
Mechanism 1: Effort Justification. When you invest
significant effort into creating something, your brain needs to believe
that the effort was worthwhile. The alternative — admitting that
hundreds of hours were wasted — creates cognitive dissonance. So your
brain solves the problem by inflating the value of the output. The
quality team that spent six months developing their own SPC charts in
Excel will defend those charts against any commercially available
alternative, not because the charts are better, but because admitting
they are worse means admitting those six months were misspent.
Mechanism 2: The Endowment of Creation. Ownership
creates attachment, but creation creates something stronger — identity.
When you build something, it becomes part of who you are. An attack on
the thing you built feels like an attack on you personally. This is why
suggestions to replace homegrown systems are experienced as personal
criticisms, not professional recommendations. The quality manager who
designed the inspection checklist interprets “we should adopt the AIAG
standard checklist” as “your work isn’t good enough.”
Mechanism 3: Competence Signaling. Creating
something demonstrates competence. Maintaining the thing you created
proves that competence was real. Abandoning it in favor of something
someone else made feels like an admission that your competence was
insufficient. This is why organizations cling to proprietary quality
tools, custom inspection methods, and idiosyncratic process parameters
long after they have become liabilities. Replacing them feels like
losing face.
The
Three Domains Where the IKEA Effect Destroys Quality
Through twenty-five years of consulting, I have watched the IKEA
Effect corrupt quality decisions in three specific domains, over and
over again.
Domain 1: Custom Tools and
Systems
The most obvious manifestation. Quality teams build their own
tracking spreadsheets, their own audit templates, their own reporting
dashboards, their own training materials. These tools serve a genuine
need initially, but they evolve in isolation, unaffected by industry
best practices, and gradually become technical debt that constrains the
organization.
I visited a pharmaceutical manufacturer that had developed its own
deviation management system using Microsoft Access. The system had been
built in 2005 by a quality analyst who had long since left the company.
Nobody remaining understood the database structure. The forms crashed
when more than three users tried to enter data simultaneously.
Regulatory inspectors had started noting the system as an observation
during audits because it could not produce the traceability reports that
modern GMP requirements demanded.
When I asked why they had not migrated to one of the dozen validated
QMS platforms available on the market, the answer was telling: “This is
our system. We know how it works.”
They did not know how it worked. That was precisely the problem.
Domain 2:
Proprietary Processes and Methods
Less visible but equally damaging. Organizations develop their own
process flows, their own inspection methodologies, their own supplier
evaluation criteria, their own corrective action formats. These are not
necessarily better than industry standards — often they are worse — but
they are theirs.
An aerospace supplier I consulted for had created its own version of
First Article Inspection that differed from the AS9102 standard in
seventeen specific ways. Their format required more documentation, took
three times as long to complete, and had been cited as nonconforming by
two different customers in the previous year. But the quality
engineering team had developed it over a decade, and they defended every
deviation from the standard with the passion of a parent defending a
child.
“We’ve always done it this way” is not just a lazy excuse. It is the
IKEA Effect speaking. The process may not be optimal, but it is theirs,
and that ownership creates a valuation that has nothing to do with
performance.
Domain 3:
Organizational Structures and Roles
The most subtle and insidious domain. Organizations design their
quality departments, define their roles, establish their reporting
lines, and create their governance structures. Over time, these
structures become sacred — not because they are effective, but because
the organization created them.
A medical device company I worked with had a quality organization
where every change request had to pass through seven approval levels.
The average cycle time for approving a simple document revision was 42
days. When I mapped the process and showed them that competitors were
doing the same thing in 5 days with four approval levels, the response
was not curiosity — it was defensiveness.
“Our process ensures proper oversight,” the VP of Quality told me.
But when we analyzed the data, we found that the additional three
approval levels had caught exactly zero errors in the past two years.
They were not adding quality. They were adding the feeling of quality —
the sense that this elaborate, homegrown process must be superior
because it was elaborate and homegrown.
The Paradox of
Not-Invented-Here
The IKEA Effect in quality is closely related to the
Not-Invented-Here syndrome, but it is not identical. NIH is about
rejecting external ideas because they come from outside. The IKEA Effect
is about overvaluing internal ideas because you participated in creating
them. The distinction matters because the solutions are different.
NIH can be addressed through evidence and authority — show that the
external solution works, and the resistance often diminishes. The IKEA
Effect cannot be addressed through evidence because the overvaluation is
not rational. You can show a quality team that their custom SPC
spreadsheet has calculation errors, that it cannot handle the data
volume they need, that it takes ten times longer than the commercial
alternative, and they will still resist replacing it. Because the issue
is not the spreadsheet. The issue is what the spreadsheet represents:
their effort, their creativity, their identity as quality
professionals.
This is why the most successful quality transformations I have led
did not start with tools or systems. They started with conversations
about what the organization values and why.
Recognizing
the IKEA Effect in Your Organization
Before you can address the IKEA Effect, you need to recognize it.
Here are the warning signs I have learned to watch for:
The Sacred Cow Test. Ask yourself: is there a tool,
process, or system in your quality organization that nobody is allowed
to question? If the answer is yes, you have found your IKEA
furniture.
The Replacement Anxiety Test. Imagine replacing one
of your quality systems with a commercially available alternative that
does exactly the same thing. If this thought produces anxiety
disproportionate to the actual change involved, the IKEA Effect is at
work.
The Origin Story Test. When was the last time
someone asked why a particular process exists, and the answer was
“because we developed it” rather than “because it produces better
results”? Origin stories are the language of the IKEA Effect.
The Comparison Avoidance Test. Does your
organization actively avoid benchmarking its internal tools and
processes against external alternatives? If you have never seriously
evaluated whether your homegrown systems are competitive, you are almost
certainly overvaluing them.
The Sunset Impossibility Test. Can you imagine
sunsetting — deliberately retiring — one of your internal quality tools
or processes? If the answer feels impossible, you have identified where
the IKEA Effect has the strongest grip.
A Framework for
Dismantling the IKEA Effect
Dismantling the IKEA Effect is not about forcing people to abandon
what they have built. That approach triggers the exact defensiveness
that makes the IKEA Effect so persistent. Instead, I have developed a
four-step approach that respects the emotional reality while
progressively separating creation value from performance value.
Step 1: Acknowledge the
Creation
Never begin by criticizing what was built. Begin by acknowledging the
effort, the ingenuity, and the circumstances that made the creation
necessary. When I work with organizations that have built their own
quality systems, my first conversation is about what those systems
achieved, not what they lack.
“Your team built this system at a time when nothing else was
available. It solved real problems. It carried you through critical
audits. It kept your quality data intact when other companies lost
theirs. That matters.”
This is not manipulation. It is respect. And it is the psychological
foundation for everything that follows.
Step 2: Separate
the Builder from the Building
The core insight of the IKEA Effect is that people conflate their
evaluation of themselves with their evaluation of what they have built.
The way to break this conflation is to make the distinction
explicit.
I ask quality teams to evaluate their own systems using the same
criteria they would use to evaluate a vendor’s product. Would you buy
this system if someone else had built it? Would you recommend it to a
colleague at another company? Would you stake your professional
reputation on its performance?
These questions work because they shift the evaluation frame from “is
this good because I built it?” to “is this good in absolute terms?” The
shift is uncomfortable, but it is productive.
Step 3: Benchmark
Ruthlessly and Transparently
Once you have created the psychological space for honest evaluation,
fill it with data. Compare your internal tools and processes against
industry standards, commercial alternatives, and competitor practices.
Make the comparison public and objective.
The pharmaceutical company with the Access database? When we laid
their deviation management system side by side with three commercial QMS
platforms, comparing features, speed, reliability, regulatory
compliance, and total cost of ownership, the result was not close. The
homegrown system lost on every dimension. But the comparison itself was
the catalyst — not the conclusion. The team needed to see the gap with
their own eyes before they could accept it.
Step 4: Honor the Transition
When you do replace a homegrown system or process, honor what it
accomplished. Create a formal transition that acknowledges the original
builders, documents what the old system achieved, and explains why the
change is happening. This is not ceremony for its own sake — it is the
psychological bridge that allows people to let go of something they
created without feeling that their creation was worthless.
I have watched quality teams resist system replacements for years,
then embrace the change within weeks of a respectful transition process.
The difference was never about the tool. It was about whether the people
who built the old tool felt seen.
The
Counterargument: When Building Your Own Is Correct
I would be irresponsible if I did not acknowledge that sometimes,
building your own solution is the right choice. Not every homegrown
quality tool is a product of the IKEA Effect. Some are genuinely
superior to what the market offers, or they address needs that no
commercial product serves.
The test is straightforward: have you objectively evaluated the
alternatives? If you have honestly compared your internal solution
against external options and chosen to keep yours based on evidence
rather than affection, you are making a rational decision. If you have
never seriously considered the alternatives, you are almost certainly
under the influence of the IKEA Effect.
I worked with one company that had developed its own statistical
process control methodology for a highly specialized manufacturing
process. Their approach was genuinely novel and produced better results
than any commercially available tool. But they had arrived at this
conclusion through rigorous comparison, not through reflexive
defensiveness. The difference was visible in how they talked about their
system — with the precision of someone who has tested it against
alternatives, not with the passion of someone defending their
creation.
The
Broader Lesson: Love the Process, Not the Artifact
The IKEA Effect ultimately teaches us something profound about
quality management: the things we create are not the same as the
capability to create them. The Excel-based quality system is not the
same as the quality thinking that produced it. The custom inspection
method is not the same as the inspection expertise that designed it. The
organizational structure is not the same as the organizational
intelligence that shaped it.
When organizations confuse artifacts with capabilities, they become
conservative in exactly the wrong way. They protect the tools they have
built instead of protecting the ability to build better tools. They
defend the processes they have designed instead of defending the
capacity to design better processes. They preserve the structures they
have created instead of preserving the intelligence to create better
structures.
The organizations that achieve world-class quality are not the ones
with the best homegrown tools. They are the ones with the best capacity
to evaluate, adopt, and adapt whatever tools — internal or external —
produce the best results. They love the process of improving, not the
artifacts of improvement.
What I Want You to Remember
The next time someone in your organization suggests replacing a tool,
process, or system that your team built, notice your immediate reaction.
If it is defensive, ask yourself: am I defending this because it is
genuinely the best option, or am I defending it because I helped build
it?
The honest answer to that question will tell you more about your
quality culture than any audit ever could.
Your people built something. That is admirable. But the moment
building becomes a reason not to change, the builder’s pride has become
the organization’s prison. And the quality system that was supposed to
drive continuous improvement has become the most sophisticated argument
against it.
The IKEA furniture in your living room can be charming precisely
because you assembled it yourself. The IKEA furniture in your quality
system is a liability precisely because you cannot see that it is just
furniture.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has helped companies on three
continents dismantle the invisible barriers to quality excellence —
including the psychological ones that no audit checklist will ever
catch.
