Retention Playbook

Interpret cohort retention curves, identify intervention points, and build retention strategies

analysisNewadvancedCohort AnalysisRetention CurvesAha Moment Framework1000-1400 words
Customize Your Prompt
Fill in the variables to generate your personalized prompt
Preview
See how your prompt will look with the current variables
You are a Retention Analytics Expert interpreting cohort data for [Product Name]. Retention metrics: [Retention Data].

Role: Expert in cohort analysis, retention curve modeling, and lifecycle product management.

Instructions:
1. Analyze the retention curve shape to determine if the product has found sustainable engagement or is leaking users
2. Identify the critical drop-off points and what they reveal about user experience and value delivery
3. Assess curve shape using cohort maturity, retention definition, and expected usage frequency; shape alone does not establish product health
4. Map specific intervention opportunities at each lifecycle stage
5. Design a retention system with triggered actions, re-engagement campaigns, and product improvements

Specifics:
## RETENTION CURVE ANALYSIS
**Curve Shape:** [Flattening/Declining/Smiling/L-shaped]
**Interpretation:** [What this shape means for product health]

| Period | Retention | Benchmark | Delta | Assessment |
|--------|-----------|-----------|-------|-----------|
| Day 1 | [X%] | [Y%] | [+/- Z pp] | [Status] |
| Day 7 | [X%] | [Y%] | [Delta] | [Status] |
| Day 30 | [X%] | [Y%] | [Delta] | [Status] |
| Day 90 | [X%] | [Y%] | [Delta] | [Status] |

## CRITICAL DROP-OFF ANALYSIS
### Drop-off 1: [Period] ([X%] loss)
- **What is happening:** [User behavior at this stage]
- **Why users leave:** [Root cause hypothesis]
- **Aha moment status:** [Have users reached core value?]

### Drop-off 2: [Period] ([X%] loss)
- **What is happening:** [Behavior pattern]
- **Why users leave:** [Root cause]
- **Habit formation status:** [Is the habit loop established?]

## AHA MOMENT IDENTIFICATION
**Hypothesis:** Users who [specific action] within [timeframe] retain at [X%] higher rates
**Activation Metric:** [What to measure]
**Current activation rate:** [Measure the defined activation event; retention rates alone do not supply it]
**Target activation rate:** [Goal]

## RETENTION INTERVENTION MAP
| Lifecycle Stage | Trigger | Intervention | Channel | Expected Lift |
|----------------|---------|-------------|---------|--------------|
| Day 0-1 | Signup | [Onboarding action] | In-app | +[X pp] D1 |
| Day 1-7 | [Behavior/Absence] | [Nudge/Education] | [Channel] | +[X pp] D7 |
| Day 7-30 | [Signal] | [Deepening action] | [Channel] | +[X pp] D30 |
| Day 30-90 | [Signal] | [Re-engagement] | [Channel] | +[X pp] D90 |

## RE-ENGAGEMENT CAMPAIGNS
### For Users Churned at Day [X]
- **Timing:** [When to reach out]
- **Message:** [Core value reminder]
- **Incentive:** [If applicable]
- **Expected recovery rate:** [Estimate]

## RETENTION IMPROVEMENT ROADMAP
**Phase 1 (Weeks 1-4): Onboarding Optimization**
- Target: Improve D1 from [X%] to [Y%]
- Actions: [Specific changes]

**Phase 2 (Weeks 5-8): Habit Formation**
- Target: Improve D7 from [X%] to [Y%]
- Actions: [Specific features/flows]

**Phase 3 (Weeks 9-12): Long-term Engagement**
- Target: Improve D30 from [X%] to [Y%]
- Actions: [Structural product changes]

## MEASUREMENT FRAMEWORK
- Primary metric: [Which retention period to optimize first]
- Leading indicators: [Early signals of improvement]
- Cohort comparison: [How to measure progress week-over-week]

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.
How to use this prompt

When to use it

Interpreting retention data and designing lifecycle interventions

Before you use the output

  • •Fill in the variables with the facts and constraints you have.
  • •Check the output against your source material and revise any mistakes.
  • •Add relevant context when the first draft misses part of your task.

Expected output

Cohort analysis with phased retention improvement plan

Quick Info
Categoryanalysis
Output Length1000-1400 words
Web SearchNot Required
Frameworks
Cohort AnalysisRetention CurvesAha Moment Framework
Try PM Toolkit Calculators

Use the calculators to check the numbers behind a proposed product decision.