Reading the Data PM

A more expensive way to lose the same users you already had.

Reading the Data Reading the DataBeginner

AARRR Is Not the Metric, It's the Diagnostic

AARRR is not five goals to chase at once. It is a way to find the one leak worth fixing first.

Most PMs can recite the five stages of AARRR. Almost none use the framework the way it was meant to be used, and that gap is where a lot of wasted quarters come from.

AARRR (Acquisition, Activation, Retention, Referral, Revenue) gets taught as a funnel and then treated as a to-do list. The implicit instruction is: improve all five. Get more people in, activate more of them, keep more of them, turn them into referrers, make more money per user. It sounds complete. It sounds responsible. It is also the wrong way to read it.

The framework is not a set of five targets to optimize in parallel. It is a diagnostic. It exists to answer one question: of the five stages, where is the product leaking the most right now, and what should you fix before anything else?

The Funnel Is a Leaky Bucket

Picture the product as a bucket. Acquisition is water going in. Each stage below it is a hole where some of that water runs out before it reaches the bottom.

If you pour more water into a bucket with a hole in the side, you do not end up with a fuller bucket. You end up spending more on water and watching most of it drain out exactly where it drained before. This is what it looks like when a team responds to a retention problem by raising the acquisition budget. The dashboard shows more sign-ups for a few weeks. The number that actually matters, users who stay, does not move, because the hole was never the top of the bucket. This is the same trap as mistaking traffic for engagement, where a metric climbs while the behavior you care about stays flat (see adoption vs tourism).

flowchart TD
    A[Acquisition\nAre people finding the product?]
    B[Activation\nDo they reach the aha moment?]
    C[Retention\nDo they come back?]
    D[Revenue\nDo the unit economics work?]
    E[Referral\nAre users bringing others in?]

    A --> B
    B --> C
    C --> D
    D --> E

The growth meeting shows acquisition up 40%. Nobody has opened the retention chart. That is not a growth strategy. That is a more expensive way to lose the same users.

The leaky-bucket view forces a discipline the to-do-list view never does: you have to look at the whole funnel and decide where the largest hole actually is before you touch anything. Not the stage that is easiest to influence. Not the stage your team already knows how to move. The one that is losing you the most.

Find the Biggest Leak, Fix Only That One

The instinct, once you accept there is a leak, is to fix several leaks at once. Resist it. Working on three stages simultaneously means you cannot tell which change moved which number, and it spreads a small team thin enough that nothing gets fixed properly.

A product losing users at Retention should not be running larger Acquisition campaigns. The retention hole has to be patched first, or every acquisition dollar pours straight through it.

A product that has not nailed Activation, where users try it once and never come back, should not be building Referral mechanics. People who never reached the moment the product becomes useful to them have nothing to refer. You would be asking unconvinced users to recruit on your behalf.

This is the part that feels uncomfortable, because it means deliberately not working on four of the five stages. The team that fixes one real leak beats the team that makes marginal progress on all five and cannot point to a single number that moved because of it.

The Right Stage Depends on Where the Product Is

Which leak is biggest is not random. It tends to track the stage of the product, and naming that stage tells you where to look first.

Pre-launch, the question is Acquisition: does anyone outside the building know this exists? Early growth, the question moves to Activation: are the people who show up actually reaching the point where the product clicks? Once there is product-market fit to defend, Retention becomes the question: are they staying, or is the curve a cliff? At the growth stage, Referral matters: is organic spread starting to replace paid acquisition? And at scale, the question is Revenue: do the unit economics actually work? Naming the stage before you act is the same discipline as reading a product through a deliberate lens rather than reacting to whatever number is loudest (the habit behind the five frames every PM uses).

The single most common mistake is working on a later-stage problem while an earlier-stage hole is still wide open. Optimizing referral loops while activation is broken is not ambitious. It is solving a problem you do not have yet while ignoring the one draining the bucket today.

Activation Has a Number, So Find Yours

Activation is the stage teams describe in the vaguest terms, which is exactly why it leaks. "Users see the value" is not measurable, so nobody knows whether it is happening. The teams that get this right replace the vague phrase with one specific, countable event that reliably predicts a user will stay.

Facebook's was seven friends in ten days. Slack's was two thousand team messages sent. Dropbox's was one file saved. None of these are arbitrary milestones picked to look good on a slide. Each was the threshold their data showed separated users who stuck from users who churned. The point is not to copy any one of these numbers; it is to do the work of finding yours, which usually means going back to the behavior before the number and asking what it actually represents (the kind of digging behind research before building). Until you can name the single action that reliably turns a trial into a habit, your activation stage is a guess, and a guess is not something you can fix.

What This Costs If You Skip It

The framework is easy to memorize and easy to misuse, and the misuse is expensive in a way that stays invisible for a while.

A team that treats AARRR as five parallel goals will look busy. There will be acquisition campaigns, referral experiments, pricing tests, all running at once. The reports will be full. And the core metric, whatever it should have been for the product's actual stage, will sit flat, because the effort was spread across stages instead of aimed at the one leak that mattered.

The diagnostic question is shorter and harder: of the five, which stage is leaking most right now, and what is the one thing I should fix before touching anything else? Answer that honestly and you will spend the quarter fixing the hole. Skip it and you will spend the quarter buying more water.

Related Articles

Train this · Reps

Acquisition is up 40% this quarter but retention is flat. Your boss wants a bigger ad budget; do you take it, redirect it, or push back?

Make the call in Reps and see whether your reasoning holds up under pressure.

Make the call
AW

Anmoll Wadhwa

Senior PM · writing The PM Code

Field notes on product judgment: essays, teardowns, and reps for PMs who would rather think than template. A sharper take most days on LinkedIn.

More like this. Once a week.

Tactical essays on the calls that actually matter. In your inbox before they are on the feed.

LEARN·BUILD·COLLABORATE