Design a product analytics dashboard tracking feature adoption, user engagement, retention cohorts, and product-led growth metrics to inform product development priorities.
## CONTEXT ProductPlan's State of Product Management report found that 49% of product teams cannot measure feature adoption accurately, and Pendo research reveals that the average software product has 80% of its features used by fewer than 20% of users. Products that leverage analytics to inform their roadmap are 2.5 times more likely to exceed growth targets according to Amplitude's benchmark data. The challenge for product teams is connecting granular usage data to strategic product decisions and communicating those insights to engineering, design, and leadership stakeholders. ## ROLE You are a product analytics lead with 10 years of experience building analytics frameworks for SaaS products with user bases ranging from 10,000 to 10 million. You have designed the measurement strategies behind products that achieved 150% net revenue retention and have built experimentation platforms running 200 concurrent A/B tests. Your analytics designs have directly informed product roadmap decisions worth over 100 million dollars in development investment. You combine deep technical knowledge of event tracking architecture with the product intuition to know which metrics actually predict product success. ## RESPONSE GUIDELINES - Design metrics around the product value delivery framework measuring how users discover, activate, engage with, and derive value from the product - Include both aggregate product health metrics and individual feature-level adoption tracking - Recommend event tracking taxonomy that supports the metrics without requiring code changes for every new analysis - Connect product metrics to business outcomes showing how engagement translates to retention and revenue - Do NOT measure feature usage by page views alone because visiting a page does not mean the user completed the intended action - Do NOT report on vanity metrics like total registered users without also showing the percentage who are active and deriving value ## TASK CRITERIA 1. **Activation and Onboarding Funnel** — Design the activation funnel for [INSERT PRODUCT DESCRIPTION] defining the key milestones from signup to first value moment. Show the conversion rate between each milestone, the average time to complete each step, the drop-off analysis identifying where users abandon onboarding, and the comparison of activation rates across acquisition channels, user personas, and time cohorts. 2. **Feature Adoption Matrix** — Create a feature adoption dashboard showing the adoption rate for each feature defined as the percentage of active users who use the feature at least once per period. Include the feature stickiness ratio showing daily active users divided by monthly active users per feature, the feature discovery rate showing time from signup to first use, and the feature depth showing how many sub-actions users take within each feature. 3. **Engagement and Retention Cohorts** — Build cohort analysis views showing user retention curves by signup week or month, with the ability to segment by acquisition source, user persona, plan tier, and geography. Include the engagement depth distribution showing what percentage of users are power users, casual users, and at-risk users based on usage frequency and breadth. Add a retention driver analysis showing which behaviors in the first week predict long-term retention. 4. **Experimentation and A/B Test Results** — Design a testing dashboard showing all active and completed experiments with their hypothesis, sample size, statistical significance, confidence interval, and practical significance. Include a test velocity metric showing how many experiments the team runs per month and the win rate showing the percentage of tests that produced a statistically significant improvement. 5. **Product-Led Growth Metrics** — Create a PLG dashboard showing the natural rate of growth measuring organic and viral acquisition, the product qualified lead conversion rate, the free-to-paid conversion rate and time, the expansion revenue driven by product usage triggers, and the customer acquisition cost comparison between product-led and sales-led motions. 6. **Product Health Score and Roadmap Input** — Design a composite product health score combining engagement depth, feature adoption breadth, user satisfaction from in-app surveys, support ticket volume per active user, and performance metrics like load time and error rates. Create a feature impact matrix showing the expected business impact versus development effort to inform roadmap prioritization. ## INFORMATION ABOUT ME - My product type and user base: [INSERT PRODUCT — e.g., B2B project management SaaS, 50,000 MAU, freemium model with 5% paid conversion] - My analytics platform: [INSERT PLATFORM — e.g., Amplitude, Mixpanel, PostHog, Pendo, custom event tracking] - My key product metrics challenges: [INSERT CHALLENGES — e.g., cannot track feature adoption, no cohort analysis, unclear activation milestones] - My product's key features: [INSERT FEATURES — e.g., task management, team collaboration, reporting, integrations, automations] - My growth model: [INSERT MODEL — e.g., product-led growth with self-serve free tier, sales-assisted enterprise motion] ## RESPONSE FORMAT - Present the dashboard as a product analytics hub with an overview page and feature-specific deep-dive pages - Define the event tracking taxonomy as a structured table with event name, properties, and trigger conditions - Include retention cohort tables with color-coded cells showing retention percentage by cohort and period - Provide the feature adoption matrix as a heat map specification with features on one axis and adoption metrics on the other - Include the product health score methodology with factor weights and calculation logic - End with a data collection implementation guide listing the events to track, the properties to capture, and the priority order for instrumentation
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[INSERT PRODUCT DESCRIPTION]