In a set of experiments published in 2011, people who assembled a plain IKEA storage box valued it 63 percent higher than an identical prebuilt one. The IKEA effect, named by the researchers who ran that study, is the bias that makes you overvalue what you built yourself. It quietly...
In a set of experiments published in 2011, people who assembled a plain IKEA storage box valued it 63 percent higher than an identical prebuilt one. The IKEA effect, named by the researchers who ran that study, is the bias that makes you overvalue what you built yourself. It quietly distorts build versus buy, "our custom tool," and the decision to keep a homegrown system long after it stops earning its place.
I study behavioral psychology because these biases do not announce themselves. They feel like judgment. A founder who insists the internal tool is better than the off-the-shelf one usually believes it, sincerely, and can list reasons. The IKEA effect is interesting precisely because the person holding the bias experiences it as clear-eyed evaluation, not attachment.
Michael Norton, Daniel Mochon, and Dan Ariely coined the term in a paper titled "The IKEA effect: When labor leads to love," published in the Journal of Consumer Psychology in 2012. Across four studies, participants assembled boxes, folded origami, and built Lego, then priced what they made. The people who did the labor consistently priced their own output higher.
The furniture result was the 63 percent premium. The origami result was starker. In the working paper, builders were willing to pay roughly five times more for their own folded frogs and cranes than non-builders were, and they rated their amateur creations as close in value to expert-made ones. They did not just like their work more. They expected everyone else to see the same value.
The study also found the limit. When people failed to finish the task, or built something and then took it apart, the premium disappeared. Labor only turns into love when the labor produces a completed thing. That detail matters for business, because it means the effect attaches most strongly to the systems you actually shipped and now depend on.
The mechanism sits on top of older research into effort justification. In a classic 1959 experiment, Elliot Aronson and Judson Mills found that women who went through a more embarrassing initiation to join a discussion group rated that group as more attractive than women who joined easily, even though the discussion itself was deliberately dull.
The explanation is cognitive dissonance. Effort and a low opinion of the result do not sit comfortably together, so the mind resolves the tension by raising its opinion of the result. The harder you worked, the more valuable the outcome must have been, or the effort feels foolish. Your brain would rather adjust the valuation than admit the labor was wasted.
This is why the IKEA effect resists reasoning. You cannot argue someone out of it with a spreadsheet, because the bias is not living in the spreadsheet. It is living in the hours already spent. The valuation is doing emotional work, protecting the effort from looking like a mistake, and that job continues no matter what the numbers say.
The most expensive place it appears is the build versus buy decision. When a team debates whether to adopt an existing tool or build its own, the internal option arrives with a hidden thumb on the scale. The custom build is not evaluated at its true cost. It is evaluated at its true cost minus the pride of authorship, and that discount is invisible to the people applying it.
Software people have a name for the pattern: Not Invented Here syndrome, the tendency to reject outside solutions in favor of internally built ones. The IKEA effect is the psychological engine underneath it. Once your team has built the thing, they will defend it against replacements that are objectively better, because they are not comparing tools. They are comparing a tool to their own labor.
The stakes are not small. Research by McKinsey and the University of Oxford across more than 5,400 projects found that large IT projects run 45 percent over budget on average while delivering 56 percent less value than predicted. A great deal of that overrun is custom work that someone overvalued at the start and could not bring themselves to abandon partway through.
The bias also shapes what you refuse to retire. A homegrown reporting script, a spreadsheet that grew into a system, an internal dashboard nobody else understands. Each one gets defended not on merit but on history. I have written before about what I stopped outsourcing and what I will never build in-house, and the honest version of that decision requires subtracting the pride before you weigh the options.
When people price a custom build, they price the building. They rarely price the owning. That is where the IKEA effect does the most damage, because the assembly is a weekend and the maintenance is a decade.
Anything you build from scratch, you are responsible for maintaining fully. The library you reinvented needs security patches. The custom auth system needs to keep up with new attack patterns. The internal tool needs a person who understands it, and that person eventually leaves. None of this shows up in the moment of creation, when the effect is strongest and the object feels most valuable.
This is why I treat automation maintenance as the job, not the launch. A system is not finished when it works. It is finished when someone is accountable for keeping it working, and that accountability is a recurring cost you signed up for the day you chose to build. The IKEA effect makes that day feel like a win and hides the bill.
Existing tools often look inferior for a reason that has nothing to do with quality. Their complexity is invisible until you try to rebuild it. The kludges and workarounds you scorned in someone else's product were usually solving real problems you have not hit yet. You will hit them, and then you will build the same kludges, and call yours elegant.
It rarely acts alone. The IKEA effect pairs with the sunk cost fallacy, where the labor already spent becomes a reason to keep spending. I have described how the sunk cost fallacy runs a technology stack, and the IKEA effect is what loads the gun. First you overvalue what you built, then you treat that inflated value as a debt you owe the project.
It also overlaps with the endowment effect, the tendency to value something more simply because you own it. When I wrote about the endowment effect and the self-hosting decision, the pattern was the same shape. Ownership and authorship both inflate valuation, and a system you both own and built gets a double markup that has nothing to do with what it delivers.
Stack these together and you get a founder who cannot see their own tooling clearly. This is the broader lesson of studying the biases making your technology decisions: the dangerous ones are not exotic. They are the everyday feeling of being sure, applied to something you have a personal stake in.
You cannot delete the bias, so the goal is to correct for it. The most reliable method is to change who does the evaluating. Ask someone with no labor invested to price the option, because the IKEA effect only inflates the valuation of the person who did the work. An outside read is not smarter. It is just unbiased in the one place you are not.
A second method is a simple test the build must pass: does the custom option offer a genuine, differentiating advantage, or does it merely feel more yours? Building is sometimes right. Security-sensitive work, a truly novel core capability, a place where your specific needs really are unusual. The problem is not building. The problem is building for pride and calling it strategy. I make the case for starting simple in start with a monolith, and the same discipline applies here.
Third, price the maintenance before you price the build. If you would not commit to owning a system for five years, you should not celebrate building it today. The real number is in what self-hosting actually costs, and the honest version includes the years after launch, not just the sprint that shipped it.
The completion detail from the original study gives one last handle. The effect attaches to finished things, so you feel it least before you start. That is the moment to make the call, while the box is still flat and the labor has not yet turned into love. Decide what to build and what to adopt at the beginning, in writing, before the bias has anything to grip.
These ideas run through the wider Kief Studio blog, and they shape how LTFI decides what to build, what to adopt, and what to keep running for the businesses we support.
The IKEA effect is a cognitive bias where people place a higher value on things they helped make. In the original study, people who assembled a box valued it 63 percent more than an identical prebuilt one, and people who folded their own origami valued it about five times higher than others did. Effort inflates your sense of worth.
It was named by Michael Norton, Daniel Mochon, and Dan Ariely in a 2011 working paper, published in the Journal of Consumer Psychology in 2012 under the title "The IKEA effect: When labor leads to love." The name refers to the flat-pack furniture that arrives requiring assembly.
It puts an invisible discount on the internal option. Because your team built it, they value the custom tool above its true cost and defend it against better alternatives. This overlaps with Not Invented Here syndrome and helps explain why so many custom projects run over budget and stay in service too long.
No. Building is right when the work is genuinely differentiating, unusually specific to you, or sensitive in a way off-the-shelf tools cannot address. The mistake is building for the feeling of ownership and calling it strategy. The test is whether the custom option offers a real advantage or just feels more yours.
Have someone with no labor invested evaluate the option, since the bias only inflates the builder's own valuation. Price the long-term maintenance, not just the build. And make build-versus-adopt decisions early, before the work is finished, because the effect attaches most strongly to completed things.
Survivorship bias overstates the typical mutual fund's reported returns by roughly 1.6 percentage points a year, according to the University of Chicago's Center for Research in Security Prices: surviving U.S. stock funds averaged 8.8 percent over the decade ending 2003, while counting...
In a famous experiment, owners demanded twice what buyers would pay for the same mug. That's the endowment effect, and it quietly distorts the cloud versus self-hosting decision in both directions. The fix is to decide as if you owned neither option.
Imagining that a project has already failed raises a team's ability to correctly identify the reasons for a future outcome by about 30 percent, according to research by Deborah Mitchell, Jay Russo, and Nancy Pennington published in the Journal of Behavioral Decision Making. That single...
Work With Us
Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.
Newsletter
Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.
Subscribe
