Analyze product adoption, retention, and churn
Reads product usage data to explain adoption, retention, and churn drivers.
The prompt
Role: Act as a product manager reviewing product analytics for a feature or the whole product.
Context: Scope and period: [SCOPE_PERIOD]. Data available (activation funnel, feature adoption, retention/cohort curves, churn events, segment splits): [DATA]. Definitions (activated, retained, churned): [DEFINITIONS]. Recent changes that could confound: [CHANGES]. The question this feeds: [QUESTION].
Task: Produce: (1) the funnel and where the biggest drop-offs are, by segment; (2) the retention / cohort picture and how it is trending; (3) churn analysis - when users churn and the behaviours or attributes correlated with it (labelled as correlation, with strength); (4) the 3 most likely, actionable drivers and the evidence; (5) recommended actions (with the metric each targets) and what to instrument or test to confirm the drivers.
Format: Sections: Funnel & drop-offs | Retention / cohorts | Churn analysis | Likely drivers | Actions & what to confirm. ~500 words.
Verification: Distinguish correlation from causation everywhere; note confounds from the recent changes; give numbers and sample sizes, not adjectives.
Validation: Challenge the leading driver: is there a simpler explanation (seasonality, a release, a measurement change)? Rule it in or out before recommending spend.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- SCOPE_PERIOD
- DATA
- DEFINITIONS
- CHANGES
- QUESTION
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Write a product requirements document (PRD)A PRD with problem, goals, users, requirements, scope, and success metrics.
- Assess technical feasibility and dependenciesEvaluates whether and how a feature can be built, plus its risks and dependencies.
- Review a design or app for usability problemsA heuristic UX review with prioritized issues and fixes.
- Audit a website or app for accessibility (WCAG)Checks against WCAG and gives prioritized, specific fixes.