Product Analytics

Product Analytics

Use when defining product KPIs, building metric dashboards, running cohort or retention analysis, or interpreting feature adoption trends across produ

Category: development Source: alirezarezvani/claude-skills

What Is Product Analytics?

Product analytics is the systematic process of defining, measuring, and interpreting key performance indicators (KPIs) to understand how users interact with a product throughout its lifecycle. It encompasses the tracking of user behaviors, feature usage, and engagement trends to inform product decisions. By leveraging specialized frameworks and methodologies, product analytics enables teams to surface actionable insights, optimize user experience, and drive sustainable growth. The Claude Code skill "Product Analytics" provides a structured approach to metric definition, dashboard creation, cohort analysis, and feature adoption interpretation, making it an essential tool for modern product teams.

Why Use Product Analytics?

Effective product analytics empowers organizations to make data-driven decisions at every stage of the product journey. Without a robust analytics strategy, teams risk focusing on vanity metrics or missing critical inflection points that impact retention, growth, and revenue. Key benefits include:

  • Objective Decision-Making: Replace intuition with quantifiable evidence, reducing bias in prioritization and iteration.
  • KPI Alignment: Clearly define and communicate success metrics across pre-product/market fit (pre-PMF), growth, and mature stages.
  • User-Centric Insights: Uncover how users navigate onboarding, adopt features, and achieve value, enabling targeted improvements.
  • Cohort and Retention Clarity: Understand long-term engagement by segmenting users and analyzing behavioral patterns over time.
  • Strategic Dashboarding: Provide actionable, hierarchical reporting for stakeholders at every level.

By integrating product analytics into the development workflow, teams enhance their ability to diagnose issues, validate hypotheses, and accelerate product-market fit.

How to Get Started

Implementing product analytics with the Claude Code "Product Analytics" skill involves a repeatable workflow:

  1. Select a Metric Framework: Choose from AARRR, North Star, or HEART based on product goals.
  2. Define Stage-Appropriate KPIs: Tailor metrics to the current product lifecycle stage.
  3. Design Dashboard Layers: Organize metrics into executive, product health, and feature-specific views.
  4. Run Cohort and Retention Analysis: Segment users to reveal longitudinal trends.
  5. Interpret and Act: Connect data movement to product hypotheses and interventions.

Example: Framework Selection in Python

## Example: Framework selection for a SaaS product
def select_metric_framework(product_stage):
    if product_stage == 'pre-PMF':
        return 'HEART'
    elif product_stage == 'growth':
        return 'AARRR'
    elif product_stage == 'mature':
        return 'North Star'
    else:
        raise ValueError('Unknown product stage')
        
framework = select_metric_framework('growth')
print(f"Recommended framework: {framework}")
## Output: Recommended framework: AARRR

Key Features

The "Product Analytics" skill offers comprehensive capabilities for product teams:

1. Metric Framework Selection

  • AARRR (Acquisition, Activation, Retention, Referral, Revenue): Ideal for growth-focused products tracking funnel progression.
  • North Star: Aligns teams around a single metric representing long-term value.
  • HEART (Happiness, Engagement, Adoption, Retention, Task Success): Measures holistic user experience, especially in early or UX-centric products.

2. KPI Definition by Stage

  • Pre-PMF: Focus on activation rates, early retention, and qualitative signals of product fit.
  • Growth: Optimize acquisition efficiency, user expansion, and conversion velocity.
  • Mature: Prioritize retention depth, revenue quality, and operational efficiency.

3. Dashboard Design & Metric Hierarchy

  • Executive Layer: 5-7 high-level metrics for quick health checks.
  • Product Health Layer: Metrics on acquisition, activation, retention, engagement.
  • Feature Layer: Tracks adoption rates, depth of usage, repeat interactions, and outcome correlations.

4. Cohort & Retention Analysis

  • Segment users by signup date or feature exposure.
  • Analyze full retention curves instead of single time-point metrics.
  • Identify onboarding and activation inflection points.

Example: Cohort Retention Calculation with Pandas

import pandas as pd

## Example user event data
df = pd.DataFrame({
    'user_id': [1, 1, 2, 2, 3, 3, 3],
    'signup_date': ['2023-01-01', '2023-01-01', '2023-01-01', '2023-01-01', '2023-01-02', '2023-01-02', '2023-01-02'],
    'event_date': ['2023-01-01', '2023-01-03', '2023-01-01', '2023-01-05', '2023-01-02', '2023-01-03', '2023-01-09']
})

df['signup_date'] = pd.to_datetime(df['signup_date'])
df['event_date'] = pd.to_datetime(df['event_date'])
df['retention_day'] = (df['event_date'] - df['signup_date']).dt.days

cohort_pivot = df.pivot_table(index='signup_date', columns='retention_day', values='user_id', aggfunc='nunique')
print(cohort_pivot.fillna(0))

5. Feature Adoption and Funnel Interpretation

  • Track feature adoption rates and depth.
  • Analyze conversion rates through critical customer journey stages.
  • Correlate feature usage with desired outcomes.

Best Practices

  • Align Metrics to Objectives: Select frameworks and KPIs that reflect your business and product goals.
  • Layer Dashboards: Separate executive, product health, and feature metrics for clarity.
  • Analyze Trends, Not Snapshots: Use cohort and retention curves to avoid misleading single-point data.
  • Prioritize Actionability: Focus on metrics you can influence directly through product or go-to-market levers.
  • Document Metric Definitions: Ensure consistency and avoid ambiguity across teams.

Important Notes

  • Product analytics is iterative; regularly revisit frameworks and KPIs as your product evolves.
  • Data quality is paramount: ensure clean instrumentation and validation before analysis.
  • Contextualize metrics with qualitative insights (e.g., user interviews) for a holistic understanding.
  • Avoid overfitting to metrics; always test changes with experiments or A/B tests where feasible.
  • The "Product Analytics" skill is open source and can be customized to your team’s specific needs (source).