retention-analysis
$
npx mdskill add mohitagw15856/pm-claude-skills/retention-analysisDiagnose why users leave, identify what keeps them, and recommend specific, testable interventions — not vague "improve onboarding" suggestions.
SKILL.md
.github/skills/retention-analysisView on GitHub ↗
--- name: retention-analysis description: "Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions." --- # Retention Analysis Skill Diagnose why users leave, identify what keeps them, and recommend specific, testable interventions — not vague "improve onboarding" suggestions. ## Retention Fundamentals **The retention curve has two components:** 1. **Steepness of initial drop** (D1–D7) — onboarding problem 2. **Long-term floor level** — product-market fit indicator A product with PMF has a retention curve that flattens. If it trends to zero, you have a PMF problem, not an onboarding problem. Name this distinction explicitly. --- ## Retention Metrics Definitions | Metric | Formula | What It Tells You | |---|---|---| | D1 Retention | Users who return on day 2 ÷ new users day 1 | Quality of first experience | | D7 Retention | Users active on day 8 ÷ users who joined 7 days ago | Early habit formation | | D30 Retention | Users active on day 31 ÷ users who joined 30 days ago | Product-market fit signal | | DAU/MAU Ratio | Daily active users ÷ monthly active users | Stickiness (>20% good, >50% excellent) | | Churn Rate | Users lost in period ÷ users at start of period | Monthly or annual | | Net Revenue Retention | MRR at end of period ÷ MRR at start (same cohort) | Revenue health including expansion | --- ## Retention Investigation Framework ### Step 1: Segment the problem Don't analyse "retention" — analyse retention for specific cohorts: - New vs returning users - Paid vs free - Acquisition channel (organic vs paid vs referral) - Onboarding path completed vs not - Feature usage (power users vs lurkers) ### Step 2: Find the inflection points Where does the drop happen? D1? D7? Month 3? - D1 drop → First session experience - D7 drop → Habit loop not formed - D30 drop → Value not delivered at depth - Month 3+ drop → Boredom, competition, or lifecycle event ### Step 3: Identify the "aha moment" correlation Which early behaviour predicts long-term retention? - Run correlation: users who did [X] in first 7 days vs 30-day retention - Common patterns: connected an integration, invited a teammate, completed a core action N times ### Step 4: Qualify the churn Interview churned users — never skip this. Survey data alone is insufficient. - "What was the trigger that led you to cancel/stop?" - "What were you trying to accomplish that you couldn't?" - "What would need to change for you to come back?" --- ## Output Format ### Retention Analysis — [Product/Segment] — [Date] **Question:** [Specific retention question being answered] **Period Analysed:** [Date range] **Segment:** [Which users] --- **Current Retention Snapshot:** | Metric | Current | Industry Benchmark | Status | |---|---|---|---| | D1 Retention | [X%] | 25–40% | 🔴/🟡/🟢 | | D7 Retention | [X%] | 10–25% | 🔴/🟡/🟢 | | D30 Retention | [X%] | 5–15% | 🔴/🟡/🟢 | | DAU/MAU | [X%] | 10–20% typical | 🔴/🟡/🟢 | **Retention Curve Shape:** [Flattening / Still declining / Trending to zero] **PMF Signal:** [Strong / Weak / Absent — based on curve shape] --- **Root Cause Hypotheses:** | Hypothesis | Evidence | Confidence | Test | |---|---|---|---| | [Cause] | [Data point] | H/M/L | [How to validate] | **"Aha Moment" Correlation:** Users who [specific action] in first [N] days retain at [X%] vs [Y%] for those who don't. --- **Recommended Interventions:** | Intervention | Target Drop | Expected Lift | Effort | Priority | |---|---|---|---|---| | [Specific change] | D1 / D7 / D30 | [X%] | S/M/L | 1/2/3 | **Monitoring Plan:** - Metric to track: [X] - Review cadence: [Weekly / Monthly] - Alert threshold: [If X drops below Y, investigate immediately] --- ## Required Inputs Ask the user for these if not provided: - **Product and business model** (SaaS / consumer app / marketplace / other) - **Current retention metrics** (D1, D7, D30 if available) - **Segment to analyse** (all users / paid / free / a specific cohort) - **Key question to answer** (why is retention dropping? what drives retention?) - **Available data** (analytics events, churn surveys, interview notes) ## Quality Checks - [ ] Retention curve shape is diagnosed (flattening vs trending to zero = PMF vs onboarding) - [ ] Cohorts are segmented before analysis (not all users lumped together) - [ ] "Aha moment" correlation is identified or flagged as unknown - [ ] Interventions are specific (not "improve onboarding") - [ ] Churned user interviews are recommended (not just data analysis) - [ ] Monitoring plan includes an alert threshold ## Guidelines - Never recommend "improve onboarding" without specifying *what* to change and *why* - Benchmark against industry — consumer apps, SaaS, and marketplaces have very different retention norms - If DAU/MAU is below 5%, that's a PMF conversation, not a retention tactics conversation - Always recommend talking to churned users — no amount of data replaces understanding the *reason*
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.