Journal · 2 June 2025

What UK product teams get wrong about retention

We keep importing a Silicon Valley curve and then acting surprised when a weekly habit in Leeds does not look like a daily one in California. The chart is not broken. The analogy is.

Retention Cartography spends a morning on this cultural mismatch. A grocery app used twice a week can be healthier than a social toy opened twenty times a day. If you grade both on D1/D7/D30 as if they were the same species, you will “fix” the grocery app by spamming reminders until people mute you.

Choose a clock that matches the job

Banking, council services, insurance, and many United Kingdom health products are episodic. The right clock might be “returned within a billing cycle,” or “completed the task they opened the app to do.” Daily curves punish products that are behaving politely.

Ask what would have to be true in a person’s week for a return to be reasonable. Then draw that interval. Amira Ellison has a habit of writing the interval on the whiteboard before anyone is allowed to paste a screenshot from a vendor template.

Bank holidays are not noise

American templates treat late December as an anomaly to exclude. In the United Kingdom, late December is a real economy. If your retail app cannot explain Christmas week, it cannot explain itself. Annotate the calendar; do not delete it to make a smooth line for a US parent company.

NPS is not retention

We still see teams wave a quarterly survey as if it were a curve. Sentiment can inform; it cannot substitute for whether people came back and did the job. If you need a spoken version of this argument for a board that grew up on NPS, Board Pack Analytics is the shorter room. If you need to redraw the curve itself, sit the Cartography.

The Signal Atlas places this work under Return. The door is a conversation, not a downloadable benchmark. We do not publish “good” D7 numbers for the United Kingdom. Those tables make people dishonest.