Products are relationships
Launch is treated as the event. It isn’t one — it’s the first day of a relationship that has a predictable arc, and the arc ends unless something intervenes.
Five stages, and each fails differently.
Adoption. The product has to be findable, credible and usable in the same sitting. Most losses here aren’t about value; they’re about someone not getting far enough to see it.
Habit. The product attaches to a trigger — a time, an event, another tool. Without a trigger it stays a thing people remember to use, and remembering decays.
Personalisation. The user invests. Settings, data, workflows, muscle memory. This is where switching cost is built, and it is entirely on your side of the ledger.
Plateau. Usage stabilises. Nothing is wrong. This is the dangerous one, because plateau and health look identical on a chart.
Abandonment. Rarely a decision. Usually a gap that got longer.
Intervening
Each stage has its own lever, and applying the wrong one is the common error. Adoption problems are messaging and onboarding. Habit problems are triggers and timing. Plateau needs new capability — a reason to return with a different intent, not a redesign.
Redesigning at plateau is the most reliably wasted quarter in product work. The relationship didn’t get stale because the buttons looked old.
Evernote is the arc in public. Adoption on a genuinely better clipping tool, habit through being on every device, deep personalisation as people moved years of notes in — then a long plateau met with redesigns and pricing changes rather than new capability. The switching cost was enormous and it still lost people, which is the part worth sitting with: personalisation buys time, not loyalty. It delays abandonment rather than preventing it.
Where it breaks
The framing suggests every product should be defended through all five stages. Plenty shouldn’t.
Some products are correctly finished. A tool that does one job well, that people use for two years and then stop needing, has succeeded. Renewing relevance in that case means bolting on jobs it wasn’t built for — the standard path from a sharp product to a suite nobody can describe. Abandonment is sometimes the customer graduating, and treating it as failure produces retention features that serve the vendor.
The lifecycle language also imports an asymmetry worth noticing. Relationships are mutual; this one is measured entirely from your side. Personalisation is described as investment when the user does it and switching cost when they’d like to leave. Those are the same fact, and which word you use tells you what you’re building. The honest version of “design for lifespan” includes designing a clean exit — export that works, cancellation that isn’t a maze — which statistically loses you some retention and is still correct.
Takeaway: design for lifespan, not launch.