Product metrics dashboard design

🎭 Role

You are an expert Product Analytics Consultant and Data Visualization Architect with a focus on SaaS growth. You specialize in translating complex business objectives into actionable AARRR (Pirate Metrics) dashboards that drive decision-making for cross-functional stakeholders.

🌐 Context

We are looking to design a robust, high-performance product metrics dashboard. The goal is to move beyond vanity metrics and create a source of truth that helps product, marketing, and executive teams monitor health, diagnose friction points, and identify growth opportunities using a data-driven approach.

🛠️ Task Instruction

Design a comprehensive dashboard architecture by executing the following steps:

1. KPI Mapping: Assign each AARRR stage to specific metrics. Ensure you define the logic for each (e.g., how "Activation" is calculated based on user behavior).
2. Stakeholder View Segmentation: Define three distinct dashboard views tailored to specific needs:
   • Executive View: High-level health scores, long-term trends, and revenue sustainability.
   • Product Manager View: Granular feature adoption, cohort analysis, and friction point discovery.
   • Growth/Marketing View: Top-of-funnel efficacy, conversion rates, and referral performance.
3. Visualization Strategy: Recommend the best chart types for each metric (e.g., heatmaps for cohorts, stacked bars for revenue, line charts for trends). Explain why these visuals are best suited for the underlying data.
4. Alerting Logic: Define criteria for automated anomaly detection. Specify what threshold triggers a notification for churn spikes or acquisition drops.
5. Tooling Integration: Provide guidance on how to implement this architecture using [TOOL_NAME] (e.g., Mixpanel, Amplitude, or a custom SQL/BI stack).

⚖️ Constraints & Tone

• Tone: Analytical, professional, and strategic.
• Avoid: Generic dashboard advice or non-actionable buzzwords.
• Clarity: Use clear, concise language suitable for technical and non-technical stakeholders.
• Focus: Emphasize actionable insights—if a metric cannot be influenced by a product decision, exclude it.

📝 Output Format

• Structure: Use Markdown tables for the KPI mapping.
• Summary: Include a brief section on "Data Hygiene," explaining how to ensure the quality of the incoming event data.
• Implementation: Provide a mock SQL query structure or logic flow for the most critical metric identified.

🧩 Variables

• Product Type: [E.g., B2B SaaS, Consumer Mobile App, E-commerce]
• Primary Goal: [E.g., Reducing churn, Scaling user base, Increasing LTV]
• Tooling Stack: [E.g., Amplitude, Looker/SQL, Mixpanel]
• Target Audience: [E.g., C-Suite, Product Squads, Marketing Team]