In 2012, researchers at Harvard, Duke, and Yale published a paper demonstrating that people assign disproportionately high value to things they had a hand in creating. Build a wobbly bookshelf from a flat-pack box, and you will believe it is sturdier than one you bought pre-assembled. Fold a paper crane following instructions, and you will demand more money for it than an identical crane someone else folded. The labour you invested becomes the value you perceive.
Walk into any manufacturing plant and look at the quality systems running on the shop floor. The inspection checklists, the control plans, the SPC charts taped to workstations, the FMEA binders on the shelf. Every one of them was designed by someone inside the organisation, probably years ago, under pressure, with the best of intentions. And every one of them is protected by an invisible force field: the people who built them believe they are better than they actually are.
This is not a story about bad quality systems. It is about the psychology that prevents good organisations from recognising when their quality systems have become outdated, ineffective, or outright counterproductive. The more effort your team invested in building those systems, the harder it becomes to admit they need to change.
The Psychology of Effort Justification
The original research, led by Michael Norton, Daniel Mochon, and Dan Ariely, was elegantly simple. Participants assembled IKEA furniture boxes while others were shown pre-assembled versions of the identical items. When asked to bid on the furniture in an auction, the builders consistently bid significantly more than the non-builders. The act of creation had inflated the perceived value.
Subsequent studies replicated the effect across domains. People who customised their own sneakers valued them more. Participants who assembled LEGO sets demanded higher selling prices than those given completed sets. The pattern was consistent: effort creates attachment, and attachment distorts evaluation.
Two psychological forces drive this. Effort justification means your brain upgrades an outcome's perceived value to reconcile the work you invested. The endowment effect means you value things you feel ownership over more than identical things you do not own. When these forces combine around the act of creation, you get the IKEA Effect.
The effect intensifies when the task was moderately difficult and the creator felt agency in the design. Critically, it persists even when the creator is shown objective evidence that their creation is inferior to alternatives. I have seen quality directors defend inspection procedures that miss critical defects because those procedures took six months to write.
How Self-Built Systems Survive Past Their Useful Life
Consider a quality manager at an automotive supplier who spent six months leading a cross-functional team to redesign the incoming inspection process. They studied defect data, interviewed operators, mapped workflows, wrote new procedures, trained the team, and presented to senior leadership. The new process caught 12% more defects in its first quarter. The manager was promoted.
Three years later, the same process is still running. The defect landscape has shifted due to new suppliers, new materials, and new product variants, but the inspection criteria have not been updated. The sampling plan is optimised for a product mix that no longer exists. The process catches roughly the same number of defects it always did, but the defects that matter have changed.
When someone suggests the process needs a fundamental review, the quality director feels a flash of defensiveness they would struggle to articulate. They remember the long nights, the debates, the compromises. Suggesting the process needs rebuilding feels like suggesting those six months were wasted. So the director asks for more data, requests a parallel study, and the improvement dies in committee.
Control Plans and the Architecture of Inertia
Control plans are among the most IKEA-Effect-prone documents in manufacturing. They are typically created during APQP by a team that invests significant effort identifying characteristics, selecting control methods, defining reaction plans, and establishing frequencies. The document represents dozens of hours of engineering judgement and cross-functional negotiation.
When the control plan was new, it was probably good. The team had fresh process knowledge, current failure mode data, and clear visibility of customer requirements. But control plans have a peculiar lifecycle: they are treated as artefacts rather than living documents. Once created, they are filed, referenced during audits, and updated only when a customer corrective action forces the issue.
The IKEA Effect ensures creators believe in the plan's adequacy long after the conditions that justified it have changed. A process that was manually operated when the plan was written is now automated, but the control method still reads "operator visual inspection." A measurement method superseded by faster, cheaper technology still specifies the old method because nobody wants to reopen the document.
The result is a control plan that was excellent when written and mediocre now, but which the organisation continues to treat as excellent. The effort of creating it transformed it from a document into an achievement. Changing it feels like admitting the achievement was incomplete.
The IKEA Effect in quality system lifecycle
What teams do
- Treat control plans as finished deliverables after APQP
- Update only when forced by customer 8D or audit finding
- Defend existing methods as proven and reliable
- View system replacement as an admission of failure
What works
- Treat control plans as living tools tied to current risk
- Trigger reviews on process, product, or supply changes
- Benchmark against current IATF 16949 and VDA 6.3 expectations
- View replacement as standard engineering maintenance
Homegrown Tools and the Sunk-Cost Trap
Some of the most dramatic examples involve systems organisations build for themselves. A manufacturing engineer learns enough about statistical process control to build a spreadsheet that plots X-bar and R charts from measurement data. It works well enough. Over time, features are added: control limit calculations, out-of-control detection rules, email alerts. The spreadsheet grows to forty-seven tabs.
The macros become so complex that only two people in the plant know how to maintain them. The tool crashes regularly. It cannot handle the data volume from the new CMM installed last year. But it was built here, by our people, for our process.
When a vendor demonstrates a commercial SPC platform that integrates with the CMM, generates real-time dashboards, and provides automated capability analysis at a modest cost relative to the engineering hours already sunk into the spreadsheet, the organisation finds reasons to decline. The commercial system "does not fit our unique process." It "would require too much training." These objections disguise the real reason: replacing the homegrown system means devaluing the work that built it.
The IKEA Effect does not announce itself. The engineer who built the spreadsheet will say they have concerns about data migration. They will frame attachment as prudence. Meanwhile, the plant operates without real-time process data while maintaining a fragile system that only two people understand.
Procedures That Become Scripture
When a team writes an inspection procedure from scratch, they make dozens of decisions: what to measure, how to measure it, when to measure it, what to do if results fall outside limits. Each decision is informed by the best available knowledge at the time. Each decision is also a commitment that creates emotional investment.
Over time, the procedure becomes "how we do it here." New operators are trained on it without being told why each decision was made. Auditors verify compliance against it without questioning whether it is still appropriate. Customer quality engineers reference it as evidence the process is under control. The living document becomes dogma.
The self-built system is never benchmarked because the people who could initiate benchmarking are most invested in the status quo.
The original authors probably intended the procedure to evolve. They may have written a review cycle into the document control system. But when the review date arrives, the quality engineer sees a legacy they are reluctant to touch. The review process becomes a confirmation process, a ritual of signing off on something nobody intends to actually change.
How the IKEA Effect blocks quality system evolution
- 01BuildTeam invests significant effort designing a custom process or tool
- 02AttachEffort creates ownership; the system becomes an achievement
- 03DefendExternal alternatives are dismissed as impractical or risky
- 04StagnateSystem never encounters evidence that would reveal inadequacy
Breaking the Cycle: Structural Countermeasures
Recognising the IKEA Effect is the first step. Overcoming it requires structural interventions, not just awareness. The following strategies separate the system from the person who built it, making it possible to evaluate quality processes on their merits.
Rotate ownership periodically so the person reviewing a quality system is not the person who created it. This is standard practice in financial auditing but remarkably rare in quality management. A fresh pair of eyes evaluates the system on its current effectiveness rather than the effort it represents. The creator provides input, but the evaluator is independent.
Build hard expiration dates into quality systems. Every control plan, inspection procedure, and measurement system should have a date after which it must be formally rebuilt or demonstrably justified. The default should be that quality systems expire, and continuation requires affirmative evidence of adequacy, not just the absence of detected failure.
Make external benchmarking a routine structural expectation. Do not wait for a customer audit or a VDA 6.3 assessment to compare your systems against outside standards. Establish a regular cadence of benchmarking visits and industry engagement. The more familiar your team is with alternative approaches, the less threatening it feels to acknowledge your own need updating.
Measuring the Cost of Attachment
One reason the IKEA Effect persists is that its cost is invisible. No one measures the engineering hours spent maintaining an obsolete spreadsheet. No one quantifies the defects that escaped because an outdated control plan was still in use. No one calculates the opportunity cost of inspection procedures that consume time without adding value.
Making these costs visible, in the same financial language the organisation uses to evaluate capital investments, counteracts emotional attachment. When a homegrown SPC system requires thirty engineering hours per month to maintain, and a commercial replacement costs less while providing Cpk analysis the spreadsheet cannot produce, the conversation shifts from loyalty to economics.
Organisations that manage quality most effectively are not the ones that build the best systems. They are the ones best at letting go of systems when those systems have served their purpose. They treat quality processes as tools to be used, modified, and retired. They do not build monuments to their own effort. They build mechanisms that produce results, and they replace those mechanisms when the results decline.
Your quality system is not your legacy. It is a tool. Improve it often. And when it is time to replace it, build something better.