cyberneticlibrary

Assess product health weekly

product-health-analysisskillsetup L1327
mohitagw15856/pm-claude-skills
What it does

Assess product health across acquisition, activation, engagement, retention layers

Best for

Weekly or monthly health check shared with leadership; forces discipline to separate metrics that matter from noise, and to answer 'so what' before recommending action.

Inputs
  • · Key metrics data (current values)
  • · Targets or benchmarks (OKR targets, historical baseline, industry benchmarks)
  • · Time period (week/month/quarter)
Outputs
  • · Product Health Report with: overall health rating (green/yellow/red), metric snapshot table, key observations, investigation priorities, recommended actions
  • · Root-cause hypothesis for each flagged metric
Preconditions
  • · Metrics data collected (even rough numbers work)
  • · Targets defined (can't compare without baseline)
Failure modes
  • · Overall health rating without justification (cherry-picks metrics)
  • · Every metric flagged as 'watch' (alert fatigue, no prioritization)
  • · Observations written in technical language (data team only, not for exec)
  • · No correlation drawn between metrics (missing funnel story)
Trust signals
  • · Overall health rating (green/yellow/red) justified with specific metric evidence
  • · Four-layer framework: acquisition, activation, engagement, retention
  • · Observations written in plain English (non-technical stakeholders can read)
  • · Correlations drawn (e.g., 'activation dip explains retention drop 2 weeks later')
  • · Top 3 investigation areas with specific diagnostic queries