Growth is an easy metric to fall in love with. New users, new signups, charts pointing up and to the right. It feels like evidence that the work is working. But Sarah's learned enough this year to know that a good-looking number isn't the same as a true one. And this month, in the final chapter of PM 201, she finds out what happens when acquisition and retention stop telling the same story. It's a fitting place to end the season. Because fixing retention turned out to need every skill she'd picked up along the way. Let's get into it.
Article by Hamza Atique, Product Management Consultant at Product People.
Over the past few months in PM 201, Sarah learned to read the cultural room, built the ceremonies that kept her team in sync, agreed on what success actually meant, and developed the discipline to say no with rigour instead of apology. By most accounts, things were going well. Signups were climbing. The quarterly review deck had charts that pointed up and to the right.
Then the finance lead asked a question that nobody in the room could answer: “If we’re acquiring this many users, why isn’t revenue growing at the same pace?”
Sarah went back to the data. And that’s when she found it. The users were coming in fine. They just weren’t staying.
The Leaky Bucket Nobody Was Watching
When Sarah pulled the numbers apart, the picture was uncomfortable. Out of every hundred users who signed up, fewer than twenty were still active a month later. Marketing was filling the bucket every week, and the bucket was draining almost as fast.
Nobody had been hiding this. It just wasn’t anyone’s job to look. Acquisition had an owner. Activation had a dashboard. But retention sat in the gap between teams, and gaps don’t show up in anyone’s weekly update.
The worst part: aggregate numbers had been masking it for months. Total active users kept rising because acquisition kept outpacing the leak. The topline looked healthy right up until it didn’t.
First, Define What “Retained” Even Means
Sarah’s instinct from the metrics episode kicked in: before measuring anything, define it. “Retained” means different things for different products. For a SaaS tool it might be a renewing subscription. For an app, a user who returns within a set window. For e-commerce, a repeat purchase.
For her product, the team landed on a simple definition: a user who completes the core action at least once a week. Not logins. Not opens. The action the product actually exists for. Once that was agreed, the retention rate itself was easy. Take the customers you end the period with, subtract the new ones you acquired during it, and divide by the customers you started with. That number tells you how well you kept the people you already had, which is a different question from how many new ones you found.
Cohorts, Not Snapshots
The single rate was a starting point, but it couldn’t tell Sarah where users were leaving. So the team switched to cohorts: grouping users by the week they signed up, then tracking each group at day 7, day 30, and day 90.
The curve told the story instantly. The steepest drop came in the first week, long before users ever reached the feature the team was proudest of. People weren’t churning because the product was bad. They were churning because they never got far enough to find out whether it was good.
That reframed the whole problem. The fix wasn’t a loyalty programme or a re-engagement email campaign. It was onboarding. The team mapped the shortest path from signup to first real value, cut everything that stood in the way, and watched the day 7 number move within two release cycles.
Retention Is Where the Whole Series Comes Together
Here’s what Sarah realised at the end of it: retention wasn’t a new skill. It was the test of every skill she’d built this year.
The stakeholder work mattered, because fixing retention meant pulling marketing, design, and engineering toward a problem none of them individually owned. The ceremonies mattered, because the cohort review needed a recurring home or it would die quietly like every other “important” initiative. The metrics discipline mattered, because retention only became actionable once “retained” had one agreed definition instead of four. And the ability to say no mattered most of all, because every week spent fixing onboarding was a week not spent on a stakeholder’s pet feature, and she had to defend that trade-off more than once.
A new feature can be shipped by one team. Retention can’t. It’s the metric that tells you whether the whole system is working.
Where This Leaves Sarah, and Us
The retention curve flattened. Not perfectly, and not forever, because retention is never finished. But the leak slowed, the cohorts improved, and for the first time the growth numbers meant what everyone assumed they meant.
And that’s where we leave Sarah. She started PM 201 navigating office politics she didn’t understand, and she ends it running a product where acquisition, activation, and retention are finally telling the same story. The frameworks helped. But the real shift was learning that the hard parts of product management are rarely technical. They’re about getting people to agree on what matters, and then having the discipline to act on it.
Thanks for following along all season. Sarah would say goodbye, but she’s busy. There’s a cohort review in ten minutes.
This month’s centerpiece zoomed in on the part of growth no one brags about: keeping users once you’ve acquired them. What often breaks retention isn’t one big mistake; it’s accumulated complexity: extra features, extra processes, extra “just ship it” decisions that slowly make the product harder to adopt (and harder to love).
This livestream is a sharp reminder that scaling fast doesn’t have to mean scaling chaos. It offers practical ways to simplify how you build and operate, so growth compounds, instead of creating a bigger leaky bucket.
Associate Product Management Consultant II
Mirza cannot leave a question half answered. Whether he’s picking out a monitor for his home office, figuring out why his wife’s car won’t start, or working out how to make chicken Kiev without an oven, he reads everything, compares everything, and always seems to have one more question before he is satisfied. It isn’t fussiness. He genuinely enjoys the process of working things out, and a decision only feels real to him once he has earned it through that process.
He also cannot resist turning a chore into a small project. A repetitive task at work is, to him, basically an invitation to build something. He has to put together bots, templates, and personal workflows just to make his own life a little easier, and he clearly gets a kick out of watching something he built quietly handle itself afterwards.
He gathers the facts, lays out exactly what is going on, and shows up prepared. Underneath the curiosity and the love of tinkering is someone who just wants things done properly, whether that is a presentation for work, a recipe for dinner, or even mapping out the right order to watch a string of movies for someone seeing them for the first time.
(Pssst, if you like our content, subscribe and share this Newsletter. It makes our editor very happy.)
Our Interim/Fractional Product Managers/Owners, Product Ops, or Product Leaders cover parental leaves, scale your Product Management team quickly, or lead key initiatives while bridging the gap until a full-time employee joins.
We onboard fast, align teams and deliver outcomes.Schedule a Call!
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.