You love what you helped build — and so will they

Give two people the same finished object. Tell the first it was made in a factory. Have the second assemble it themselves from parts — the same object, now with their own half-hour of fumbling with an Allen key baked in. Ask each what it’s worth, and the assembler will price it higher. Not because their version is better. Because they made it. Effort you put into a thing reappears as value you see in it.

Researchers named this the IKEA effect — the flat-pack furniture being the obvious emblem — in work by Michael Norton, Daniel Mochon, and Dan Ariely. Across studies of assembled boxes, folded origami, and built Lego, people consistently valued their own handiwork above identical pre-made versions, sometimes rating their amateur results as worth about as much as an expert’s. Two details from that work matter more than the headline. First, the premium came from labor, not from choice or customization alone — the sweat itself did the revaluing. Second, and this is the part builders forget: the effect depended on completing the task. When people assembled something and then took it apart, or never finished, the extra valuation didn’t appear. Effort creates attachment only when it succeeds. Abandoned assembly buys you nothing.

For a 0→1 product this is a design instruction hiding as a curiosity. The most common onboarding — a guided tour, a passive walkthrough, a product doing tricks for the user — generates no IKEA effect at all, because the user did no work. The onboarding that makes people stay is the one where they make one real thing: a configured board, a first project, a profile in their own words, a small artifact that is now theirs. That’s not just “learning by doing.” It’s manufacturing a little ownership. The user who built something in your product on day one is holding an object they value more than an identical one you’d have handed them — and people are far slower to abandon what they had a hand in making.

Now the turn, because this mechanism doesn’t only run in your users. It runs in you. The IKEA effect is one of the cleaner explanations for why teams can’t kill their darlings. The feature you personally sweated over feels more valuable to you than it is to a user who feels none of that labor — your estimate of its worth is inflated by exactly the hours you can’t get back. This is how a product accumulates lovingly-built things nobody uses: every one of them is somebody’s assembled bookshelf, over-valued by its maker. The defense isn’t to care less. It’s to not trust your own valuation of what you built. Judge your features the way a stranger would — watch what users actually do with the thing, and let someone who didn’t build it hold the knife when it’s time to cut.

⁂

Two honest caveats keep this from turning manipulative. Manufactured effort backfires — busywork the user is forced through to “earn” attachment reads as friction, and forced friction triggers resentment, not ownership. The labor has to be meaningful, producing something the user actually wanted, and it has to succeed. And attachment is not the same as usefulness: the IKEA effect can make a user over-value a bad configuration just as easily as a good one. Use it to help people invest in a product worth investing in — not to glue them to a mistake.

The build decision, then, is two-sided, and both sides are worth writing down. On the user’s side: design a first run where they make one real, completable thing, not one where they watch. On your side: assume every feature you built feels more valuable to you than it is, and check it against behavior before you defend it.