Lean analytics is not a dashboard. It is a sequencing framework — a way to decide what question deserves your attention right now, and what evidence would let you move on. After five stages — empathy, stickiness, virality, revenue, and scale — the natural last question is practical: how do you know which stage you are actually in?
This is the complete lean analytics checklist for all five stages. Use it as a diagnostic tool, not a scorecard. When a team feels stuck, the cause is almost always the same: they are trying to solve a later-stage problem with evidence from an earlier stage, or vice versa. A revenue problem is usually a stickiness problem in disguise. A scale problem often unravels because the empathy work was thin. The checklist below helps you locate the real bottleneck and the actionable metrics that should be guiding the next experiment.
Stage 1 — Empathy: Does Anyone Care Enough to Change Their Behavior?
The first stage is not about your product. It is about reducing uncertainty around the problem, not the solution. Most early teams collapse these two and confuse interest with intent.
A useful test is whether you can describe the problem without describing your product. If the problem only exists in the shape of your feature set, the empathy work is incomplete. Real problems leave fingerprints in user behavior — spreadsheets, hacks, Slack threads, copy-pasted workflows — long before any software gets built.
Run through this checklist:
- Can you define the problem without describing the product?
- Are users already taking action today (workarounds), or are they just “interested”?
- Is the pain frequent or expensive enough to trigger a behavior change?
- Do you know who has willingness to pay (or budget authority), and why?
- Can you describe the target market concretely, not with vague labels like “SMB”?
- Do you understand the alternatives users rely on (including “do nothing”)?
- Have you deliberately removed at least one feature or idea for lack of evidence?
Passing signal: A clearly articulated problem, a narrow segment, and credible evidence of urgency or workarounds.
For a deeper walkthrough of this stage, see the empathy stage.
Stage 2 — Stickiness: Do People Keep Coming Back?
Stickiness is the proof that repeated behavior exists and becomes more reliable over time. This is the stage where most teams confuse activity with retention, and where a flattering vanity metric can keep a team busy for months without changing the underlying truth.
The clearest tell of a sticky product is that users return to the same core loop without being pushed. They do not need an email, a notification, or a re-engagement campaign to remember why they came. The loop pulls them back because it produces value reliably. Cohort analysis, not the overall average, is what makes this visible — averages hide the death of early cohorts behind the noise of new signups.
- Is there one clear core loop that users repeat?
- Can you distinguish between retention and engagement?
- Do you know the earliest “moment of value” and how quickly users reach it?
- Are you evaluating stickiness with cohort analysis rather than the overall average?
- Do you know where usage consistently breaks down (for example, week 2 drop-off)?
- Are feature decisions tied to explicit hypotheses about the core loop?
- Can you describe what “good use” looks like in the user’s actual workflow?
Passing signal: Retention curves flatten by cohort, and the core behavior repeats predictably without external pushes.
For more on cohort analysis examples and what stickiness looks like in practice, see the stickiness stage.
Stage 3 — Virality: Do Users Naturally Bring Others?
Virality is not a growth trick. It is a byproduct of value. When teams treat it as a tactic — referral bribes, share-to-unlock prompts, growth-hacky funnels — they usually pollute retention and learn nothing about whether the product actually deserves to spread.
The honest version of this stage asks whether users invite others because the product becomes more useful when shared, or because they were rewarded for the click. The difference shows up in second-order behavior: invited users who stay versus invited users who churn after the bonus expires.
- Do you know the type of virality you are observing (inherent, incentivized, word-of-mouth)?
- Are you treating K and viral cycle time as diagnostic signals, not vanity numbers?
- Do invitations clearly convey value to the recipient (acceptance rate reflects clarity)?
- Are you improving viral potential by:
- Increasing acceptance rate
- Extending user lifetime
- Shortening viral cycle time
- Making invitations feel natural rather than coerced
- In a B2B context, are you using appropriate proxy signals (NPS, referrals, shared artifacts)?
Passing signal: Virality meaningfully reduces acquisition friction or accelerates learning without hurting retention.
For more on viral mechanics and B2B proxies, see the virality stage.
Stage 4 — Revenue: Do People Pay, and Keep Paying?
The revenue stage tests the business model with the same rigor you used to test the product. Many teams quietly skip this — they treat pricing as a launch decision, not an experiment, and discover too late that customers who said they would pay do not, or that the ones who pay do not stay.
Revenue is the present, not the future. If you cannot run a paid experiment today because “the product is not ready,” what you usually have is a stickiness problem disguised as a readiness problem. The willingness to pay is part of the product hypothesis, not a separate phase that begins after launch.
- Are you treating revenue as a current experiment, not a future problem?
- Is the market clearly defined by budget authority, urgency, and alternatives?
- Do you understand who pays vs. who uses (especially in B2B)?
- Are you tracking business health through:
- CAC vs. CLV
- Cash flow sensitivity
- Break-even lenses (customer payback, operations, minimum viable survival)
- Revenue growth relative to prior sales and marketing spend
- Are you avoiding a freemium default unless the conditions genuinely support it?
- Can you map several revenue paths and explain why one is winning?
Passing signal: Repeatable conversions, retention that holds after payment, and unit economics that do not degrade as you grow.
For more on payback models and freemium pitfalls, see the revenue stage.
Stage 5 — Scale: Does the Model Hold Up in the Market?
Scale is where teams discover whether the model is repeatable across channels and segments without losing strategic focus. The trap at this stage is mistaking attention for direction — treating every inbound interest as a signal that the roadmap should expand, instead of as an input to evaluate.
Scaling is also the stage where the difference between standardization and expansion matters most. Standardization means serving the same customer with less effort per unit. Expansion means entering new markets, channels, or constraints. Most failures at scale come from expanding before the core has been standardized — adding complexity to a model that has not proven repeatable.
- Are you treating attention signals as inputs, not automatic roadmap mandates?
- Are you tracking customer acquisition payback by channel, region, and segment?
- Is your strategy clearly anchored to one path (focus, efficiency, or differentiation)?
- Are you explicitly distinguishing between:
- Standardization (same customer, less effort per unit)
- Expansion (new markets, channels, constraints)
- Is the core standardized enough to withstand expansion?
- Are you operating with disciplined constraints (for example, a fixed number of hypotheses and experiments per cycle)?
Passing signal: Growth strengthens core metrics, economics stay predictable, and complexity remains controlled.
For more on payback discipline and the standardization vs. expansion distinction, see the scale stage.
Why Lean Analytics is a Sequencing Framework, Not a Dashboard
Lean analytics is often misread as a measurement system — pick the right metrics, build the right dashboard, and the answers will appear. The lean startup methodology behind it points to something different. The framework’s value is not the metrics themselves. It is the order in which the questions get answered.
Most teams that fail are not failing for lack of effort.
- They are spending effort in the wrong place.
- They polish onboarding before they have proof anyone cares about the problem.
- They tune pricing before they have a sticky core.
- They chase channels before the model is repeatable.
The principle is simple, even if it is hard to follow:
- Identify the stage the business is actually in.
- Identify the most important metric and the analysis method for that stage.
- Run experiments until evidence — not guesswork — lets you move forward.
Used this way, lean analytics becomes more than measurement. It becomes a thinking framework that keeps your attention on the right question at the right time.
Conclusion
This checklist exists to be used badly the first time. Run through it honestly and you will almost always find that one stage is doing less work than you assumed, and another is being asked to carry more weight than it can. That gap is the most useful output. The point is not to score five out of five — it is to locate where the next experiment belongs.
If you are starting fresh with the series, the lean analytics overview explains the core premise and how the five stages connect. Each stage also has a dedicated piece: empathy, stickiness, virality, revenue, and scale. Diagnose first, then read the stage that matches where the evidence is thinnest. That is where the next move lives.
Lean Analytics Series
(1) What is Lean Analytics? The Real Meaning of Lean and Why Experimentation Is at Its Core
(2) Lean Analytics Empathy Stage: How to Find Real Market Problems Worth Solving
(3) Lean Analytics Stickiness Stage: Measuring Retention and Engagement
(4) Viral Growth in Lean Analytics: How Users Bring Other Users (Coefficient, Cycle Time, B2B)
(5) Lean Analytics Revenue Stage: Proving Your Business Model Works (CLV > CAC)
(6) Lean Analytics Stage 5: Scale — How to Know If Your Business Can Survive Market Pressure
(7) The Complete Lean Analytics Checklist: Diagnose Your Stage from Empathy to Scale