Field Notes · 2026-04-02
Reading retention without vanity cohorts
How to choose retention windows that match how people actually return to your application.
A seven-day retention curve copied from a consumer social app rarely helps a weekly planning tool. Retention windows should mirror the natural return rhythm of the product.
Ask what a healthy account does in a normal week. If the answer is “opens once to approve invoices,” daily active counts will punish success. Prefer return definitions tied to meaningful actions in that rhythm.
Compare retained accounts against quiet accounts on three behaviors only. More than that turns the review into noise. Look for behaviors that appear before the retention cutoff, not after.
Report retention as both a curve and a short narrative: who stayed, what they did early, and which segment never returned after day three. Numbers alone rarely change a roadmap.
When leadership asks for a single retention score, give them the window you chose and why. Transparency about the definition prevents later arguments when the curve shifts after a feature launch.