Retention Cohorts for Product Teams
Build a weekly grid from a retained event you can defend, then present it to people who will try to break it.
Course notesWest Country school for product analytics
Retention is a story about people who came back, not a colour on a heatmap.
Desktop Routecore trains analysts and product leads to build, interrogate, and present user retention cohort analysis without borrowing someone else’s north star.
2,180
analysts taught since 2019
37
product organisations in the UK and EU
8.4 / 10
alumni would send a colleague
63%
still using their cohort template six months later
On the timetable
Programmes you can join this season
Each course is a complete unit. The flagship is the only one with weekly live studios.
Lifecycle Intervals for Subscriptions
Map billing cycles against behavioural tenure so a “month 2 drop” is not just a calendar artefact.
On the listing
Reading a Cohort Chart
For directors who inherit slides. Learn which cells are noise, which are mix, and which deserve a project.
On the listing“The ‘Composition bias’ week stopped us congratulating ourselves for a cohort that was just a cheaper acquisition channel. I still dislike how long the SQL homework takes.”Priya M., growth analyst, Leeds — Retention Cohorts for Product Teams
What changes after class
You leave with a grid you can explain, not a template you cannot name.
Most teams copy a retention widget and then argue about colours. We start from the retained event, the clock, and the people excluded from the denominator.
- A retained event with a paper trail Write the definition in language a new analyst can re-run in six months.
- Tenure weeks, not marketing weeks Separate calendar cut-offs from how long a person has actually been around.
- Mix before miracle Check whether the latest cohort is a different kind of user wearing the same product.
- Board language Present a limitation in the same slide as the claim, so the claim survives.
From the journal
Recent notes
Why week-one retention is a lazy north star · Survival curves versus classic cohort grids
Quiet office hours: replies to hello@desktop-routecore.digital usually land within two working days.