📊 Cohort analysis shows what aggregates hide

PM Cohort Analysis Guide
(2026 Edition)

5 reasons cohorts beat aggregates, 6 segmentation dimensions, 6 patterns to spot, and 6 common mistakes.

Build PM Analytics Skills Daily — Free →

5 Reasons Cohorts Beat Aggregates

1.

Aggregate metrics hide change — new users pull retention down; old users pull it up

2.

Cohorts show whether product changes actually improve user experience over time

3.

Cohorts separate onboarding effects from deep retention

4.

Cohorts reveal which user segments to invest in (and which to stop acquiring)

5.

Cohort trends often precede aggregate trends by weeks — early warning system

6 Dimensions to Segment By

1.

Signup date — standard retention cohorts

2.

Acquisition channel — organic vs paid vs referral

3.

Geography — metro vs Tier-2 vs rural

4.

Device / platform — iOS vs Android vs web

5.

Persona / use case — power users vs occasional users

6.

Onboarding path — completed full onboarding vs skipped

6 Patterns to Spot

🔍

Recent cohorts retaining worse than old cohorts — warning: product may be degrading

🔍

Recent cohorts retaining better — confirmation a product change worked

🔍

Retention curves flatten — healthy habit formation

🔍

Retention curves decay to zero — no sustainable value; product-market fit issue

🔍

Paid cohorts retain much worse than organic — CAC:LTV is unsustainable

🔍

Geographic cohorts diverge — product is working in some markets and not others

6 Common Mistakes

Comparing cohorts of different sizes without normalising — raw counts mislead

Reading too much into small cohorts — <500 users per cohort is noisy

Ignoring seasonality — Diwali signups behave differently than summer signups

Not using multiple segmentations — one lens misses context

Treating cohort trends as eternal — product changes break the pattern

Not investigating WHY cohorts differ — observing without diagnosing

FAQ

When should PMs run cohort analysis vs aggregate analysis?

Cohorts for product changes, aggregates for dashboards. If you're asking 'did our recent feature help?' — cohort analysis is usually the right tool. If you're reporting 'overall DAU' — aggregate works. PMs who always use aggregates miss product-change impact; PMs who always use cohorts over-analyse for simple dashboards.

What's the biggest mistake PMs make with cohort analysis?

Drawing conclusions from cohorts too small to be meaningful. 300 users per cohort is noisy; 3,000+ is usually reliable. PMs who celebrate a 'cohort win' in a small sample often see it reverse next month. Build intuition for your product's baseline variance before reading cohort signal.

Build PM Analytics Skills Daily

Daily scenarios on cohort analysis, segmentation, and reading real product signal.

Start Free Trial →