The data your users made is worth more to them than it is to you

There’s a moment in almost every product’s life where you open a user’s account and see a thin layer of stuff. A few saved items. A half-filled profile. Three projects, two of them empty. A couple of settings nudged off default. You think: that’s not much. If we reorganized it, or migrated it, or quietly cleaned it up, nobody would really mind.

You are almost always wrong, and there’s a precise reason why. That stuff isn’t worth much to you. It’s worth a surprising amount to the person who made it — far more than its contents would suggest to any outside observer. The gap between those two valuations is not sentimentality. It’s a measurable quirk of how brains price the things they own.

Psychologists call it the endowment effect. In the classic demonstration, you hand out coffee mugs to half a room at random, then let people trade. The ones holding a mug demand roughly twice what the ones without a mug are willing to pay — for the identical mug, assigned seconds ago by chance. Ownership alone, with no time and no effort, inflates value. Underneath it sits loss aversion: losing something registers in the brain as roughly twice as painful as gaining the same thing is pleasant, so the moment an item becomes yours, giving it up reads as a loss and the price of parting with it jumps.

Now stack a second effect on top. The IKEA effect: we value things we built ourselves more than equivalent things we didn’t — the wobbly bookshelf we assembled feels worth more than a nicer one off the shelf, because our own labor is baked into how we see it. User-created data is the perfect storm of the two. They own it and they made it. Every row in your database that a person typed carries a little charge of effort and identity that never shows up in the byte count.

Once you see this, several build decisions rearrange themselves.

Getting their stuff in early is the fastest way to feel valuable. An empty account has nothing to be endowed with. The point of a good import step, a good first setup, a “connect your existing tools” flow, is not efficiency — it’s endowment. The moment the product reflects the user’s own world back at them, it stops being your product and starts being theirs. That flip is worth more than three features.

Destructive actions are more expensive than your logs admit. Because that data feels precious, deleting it — or letting the user delete it carelessly — carries real emotional weight. Show concretely what will be lost, make it recoverable, and never ambush. A “delete everything” that feels casual on your end reads as a small betrayal on theirs, even when the user asked for it.

The same force that keeps your users also blocks new ones — so build the on-ramp. Endowment is why people don’t switch away from you. It’s also why they don’t switch to you: their stuff is trapped in someone else’s product, and moving it feels like a loss. An excellent importer from a competitor isn’t a data-plumbing feature; it’s a way to transfer the endowment. You’re not just copying rows. You’re moving the feeling of ownership across the fence.

And there’s a line you can cross. You can weaponize all of this — make export hard, make the data a hostage, let the endowment curdle into a cage the user can’t leave. It works, for a while, and then it turns into the exact resentment that fuels a competitor’s “switch away in one click” ad. The honest version earns the stickiness by making the stuff genuinely useful, and then lets people walk out the door carrying it. Trust that if the product is good, most of them won’t.

The number in your database is bytes. To the person who typed it, it’s an hour of their attention and a small piece of their judgment. Design like you can tell the difference.