In 2011, researchers at Harvard Business School demonstrated that people place a disproportionately high value on things they helped create. Participants who built their own IKEA boxes valued them significantly higher than identical pre-assembled boxes. The act of creation, even imperfect creation, forged an emotional bond that defied rational assessment.
The quality profession has this exact problem, and it is quietly destroying the ability to improve. Organisations fall in love with their own solutions, guarding proprietary spreadsheets, custom inspection formats, and idiosyncratic approval workflows long after those tools have become technical debt.
Through two decades of implementing and transitioning ISO 9001 and IATF 16949 systems, I have watched quality teams defend broken processes with volcanic resistance. The obstacle is rarely a lack of evidence. The obstacle is psychological attachment.
The Homegrown System Nobody Can Touch
I worked with a mid-sized automotive supplier that had built its own quality management system over fifteen years. It started innocently: a quality manager created an Excel-based tracker for nonconformances. Over the years, he added a CAPA tracker, a supplier scorecard, an audit dashboard, and a calibration reminder system. Each addition addressed a genuine need at the time.
By the time I arrived, the system had grown into a sprawling network of over forty interconnected Excel workbooks linked through VLOOKUPs and shared network drives. It took new quality engineers three months to learn. It crashed weekly. Data entry errors were endemic because the same information had to be manually entered in four different places. It could not generate the reports their largest customer now required, nor integrate with the new ERP system.
Every time someone suggested replacing it with a validated QMS platform, the resistance was immediate. The team argued they had built it themselves, that it worked for them, and that replacing it meant throwing away fifteen years of development. They were catastrophically wrong about what those years had produced. What they had was not a quality system. It was a monument to the IKEA Effect, loved because it was built, not because it was good.
Three Psychological Mechanisms in Quality
The IKEA Effect operates through three distinct psychological mechanisms, each mapping precisely onto behaviours I have observed across automotive and aerospace plants. Understanding the mechanism is prerequisite to breaking it.
The first is effort justification. When a quality team spends six months developing custom SPC charts in Excel, they will defend those charts against any commercially available alternative. Admitting the charts are slower or less capable means admitting those six months were misspent. Cognitive dissonance resolves the problem by inflating the perceived value of the output.
The second is the endowment of creation. Ownership creates attachment, but creation creates identity. When you build something, an attack on the artefact feels like an attack on you. This is why suggesting a team adopt the AIAG standard checklist is interpreted as a personal insult by the engineer who designed the internal version. The third mechanism is competence signalling. Abandoning a proprietary tool in favour of a commercial one feels like admitting your professional competence was insufficient from the start.
Where the IKEA Effect Destroys Value
I have watched this cognitive bias corrupt quality decisions in three specific domains. The first and most obvious is custom tools and IT systems. A pharmaceutical manufacturer I worked with had built a deviation management database in Microsoft Access back in 2005. The original builder had long since left. Nobody remaining understood the structure, and the forms crashed when multiple users entered data simultaneously. Regulatory inspectors had begun citing it because the system could not produce required GMP traceability reports.
When I asked why they had not migrated to a validated platform, the answer was telling: this is our system, and we know how it works. They did not, in fact, know how it worked. The system had become a liability actively generating audit findings.
The second domain is proprietary processes and methodologies. An aerospace supplier I audited had created its own First Article Inspection format that differed from the AS9102 standard in seventeen distinct ways. Their custom format required more documentation and took three times as long to complete as the standard. It had been cited as nonconforming by two different customers. But the engineering team had developed it over a decade, and they defended every deviation with the passion of a parent defending a child.
The third domain is organisational structures and approval workflows. A medical device company had a change request process requiring seven approval levels. The average cycle time for a simple document revision was 42 days. When I showed them competitors doing the same thing in 5 days with four approvals, the response was defensiveness, not curiosity. Analysis of the data showed the extra three levels had caught zero errors in two years. They were adding the feeling of quality, not quality itself.
Symptoms of the IKEA Effect in Quality Operations
Attachment-driven behaviour
- Reflexive defence of a tool when alternatives are proposed
- Processes justified by origin rather than current performance
- Active avoidance of benchmarking against industry standards
- Inability to imagine sunsetting a legacy internal system
Evidence-based practice
- Willingness to objectively compare internal and external options
- Processes justified by cycle time, defect rate, and audit results
- Regular benchmarking against commercial QMS platforms and standards
- Treating systems as replaceable tools rather than permanent fixtures
Not-Invented-Here vs. the IKEA Effect
The IKEA Effect is closely related to Not-Invented-Here syndrome, but the distinction matters because the interventions are different. Not-Invented-Here is about rejecting external ideas because they come from outside. The IKEA Effect is about overvaluing internal solutions because you participated in building them.
You can often overcome Not-Invented-Here resistance through evidence and authority. Show the team that the external solution works, and the pushback frequently diminishes. The IKEA Effect does not yield to evidence because the overvaluation is not rational to begin with. You can demonstrate that a custom SPC spreadsheet contains calculation errors, cannot handle the required data volume, and takes ten times longer than a commercial alternative. The team will still resist replacing it.
The issue is never the spreadsheet. The issue is what the spreadsheet represents: the effort, creativity, and professional identity of the people who built it. This is why the most successful quality system transformations I have led did not start with tools. They started with conversations about what the organisation values and why those values exist.
A Framework for Dismantling Attachment
Dismantling the IKEA Effect requires more than presenting a business case. Forcing people to abandon what they have built triggers the exact defensiveness that makes the bias persistent. The framework I use respects the psychological reality while progressively separating creation value from performance value.
Four-Step Process for Transitioning Off Homegrown Systems
- 01Acknowledge the creationBegin by validating the effort and the circumstances that made the internal system necessary. State explicitly what it achieved.
- 02Separate builder from buildingAsk the team to evaluate their system using the same criteria they would apply to a vendor proposal.
- 03Benchmark transparentlyCompare the internal tool against commercial alternatives across features, speed, regulatory compliance, and total cost.
- 04Honour the transitionDocument what the legacy system accomplished and formally recognise the builders before switching to the new platform.
The first step is acknowledging the creation. Never begin by criticising what was built. When I work with organisations reliant on legacy spreadsheets, my first conversation is about what those systems achieved. I tell the team they built something at a time when nothing else was available, that it solved real problems, carried them through audits, and kept data intact when competitors lost theirs. This is not manipulation. It is respect, and it is the psychological foundation for everything that follows.
The second step separates the builder from the building. 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 plant? Would you stake your professional reputation on its performance? These questions shift the evaluation frame from ownership to absolute performance. The shift is uncomfortable, but productive.
The issue is never the spreadsheet. The issue is the effort, creativity, and identity it represents.
The third step is transparent benchmarking. When we laid the pharmaceutical company's Access database side by side with three commercial QMS platforms, comparing features, speed, and regulatory compliance, 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.
The fourth step is honouring the transition. When you replace a homegrown system, create a formal handover that documents what the old system achieved and explains the rationale for the change. I have watched quality teams resist replacement for years, then embrace the change within weeks of a respectful transition. The difference was never about the tool. It was about whether the people who built the old tool felt seen.
When Building Your Own Is Correct
Not every homegrown quality tool is a product of the IKEA Effect. Sometimes building your own solution is the right choice. A specialised manufacturing process may require a statistical approach that no commercial platform provides. The test is whether the decision was made through rigorous comparison or reflexive defensiveness.
I worked with a company that had developed its own SPC methodology for a highly specialised automotive weld line. Their approach was genuinely novel and produced better capability results than the standard tools. But they had arrived at this conclusion through objective measurement. The difference was visible in how they talked about their system: with the precision of engineers who had tested alternatives, not the passion of people defending their creation. They could tell you exactly why the commercial options failed.
If your team can articulate the specific performance reasons a proprietary tool outperforms alternatives, you are likely making a rational decision. If the defence relies on tradition, ownership, or the effort invested, the IKEA Effect has taken hold. The language people use to describe their systems tells you whether the attachment is professional or emotional.
The artefacts we build are not the same as the capability to build them. The Excel-based tracking sheet is not the same as the quality thinking that produced it. When organisations confuse artefacts with capability, they become conservative in the wrong direction. They protect legacy tools instead of protecting the ability to build better ones. The most effective quality cultures love the process of improvement, not the artefacts of improvement.