Retention without the hockey stick

Consumer social products get to show a retention curve that looks like a story: steep drop, then a floor, then a miracle if the team is lucky. Most apps we teach — lending, hospitality, B2B field tools, regional marketplaces — do not get that shape. Pretending they do makes executives look naïve.

Name the job, then the return

Retention only means something once you have named the job. A guest who books a hotel twice a year may be perfectly retained. A rider who disappears after week two may not be. If your appendix uses “D30 retention” without saying retained at what, the board will invent a consumer-social story and you will spend the meeting undoing it.

We ask teams to write the job in the metric dictionary: “retained = completed at least one paid ride in the window,” or “retained = made a repayment.” Then month-two paid retention becomes a sentence a non-product director can repeat.

Lumpy is allowed

Seasonal apps should compare to the same period last year, not to last week. Campaign-driven apps should annotate the campaign on the curve rather than calling the bump “organic improvement.” Reactivation after a push notification is not the same as retention; mixing them inflates the floor and hides whether the product is actually wanted.

What to say when the curve is ugly

Ugly curves are still information. “Month-two paid retention is 41%, down three points, concentrated in iOS users who hit the new checkout” is a board sentence. “We are focused on engagement” is not. The Cohort Narratives studio practises that sentence until it is boring. Boring is good. Hockey sticks belong on posters.

If you only remember one thing: do not apologise for a shape that matches the job. Apologise for a definition that nobody in the room shares.

All field notes