Designing products people actually keep

There is a version of consumer goods where the product is designed to be replaced, and the replacement is the revenue. It works, up to the point where the customer notices. When they do, they do not just stop buying the product — they stop trusting the brand, which is a much more expensive loss.

The alternative is not making things that last forever. It is being clear about how long something should last and then meeting that promise.

Objects survive for reasons that have very little to do with durability testing. They survive because they still look right after a year, because the part that wears out can be replaced, because they were the right size for the drawer they live in, and because nothing about owning them became annoying.

A phone case rarely fails structurally. It gets replaced because it yellowed, or because the buttons went soft, or because the edge collected grease that never fully cleaned off. None of those are strength problems. All of them are keepability problems, and all of them are decided at specification.

Ask what will make someone throw this away, then design against that instead of against a drop test.

• What is the first thing that will look bad? Usually a finish, not a structure.
• What is the first thing that will annoy them? Usually a closure, a button or a cable fit.
• What is the first thing that will break? Make it the thing that can be replaced.

A product people keep generates reviews written a year later, which are the only reviews that carry weight in a crowded category. It generates repeat purchases across a range rather than a replacement of the same item. And it lets a brand raise price over time, because the claim has evidence behind it.

Replacement revenue is easy to model and hard to defend. Retention is the opposite, which is exactly why it is worth building for.