Default retention charts are calendars. They ask: of the people who showed up on day zero, how many showed up on day seven? That is a respectable question for a newspaper. It is a slippery question for a product, because “showed up” is doing too much work.
In App Analytics, a return can be a notification wake, a password reset, or the one job the product actually exists to finish. If you treat those as equivalent, the curve will flatter whoever still has the app installed.
Cohort by first job, not by first open
Retention Drawing starts by naming the first job you are willing to call a real beginning. For a lending app it might be “affordability check started,” not “account created.” For a language app it might be “first lesson completed as a student,” not “opened after install.” People who never finish that job are not a retention problem. They are an onboarding geography problem, which is a different map.
Once the beginning is honest, split the cohort by how they arrived and by role if roles exist. The language-app case on our voices page looked healthy until teachers and students shared a path. The curve was not lying. It was answering a question nobody had meant to ask.
Ask who is missing, not only who remains
A studio prompt we reuse: take the people who disappeared between day 1 and day 7 and describe three plausible lives for them. If you cannot, you do not understand the drop. If all three lives are “they hated the UI,” you are still guessing with confidence.
Sometimes the missing people finished the job elsewhere — a web surface, a partner, a phone call. App Analytics will not see that unless you instrument the elsewhere or admit the blind spot in the Monday pack. Admitting the blind spot is a reading. Pretending the curve is the whole product is not.
Keep one ugly chart
We ask students to keep a single unflattering view: retention of people who completed the first job, excluding those whose return was only a push notification. It is rarely the chart you would present to a board. It is the chart that stops a team from congratulating itself with session counts. If that sounds like the sitting you need, write to us about Retention Drawing.