Designing a Feature Health Dashboard and the Metrics That Prove It Works

You are the product manager who owns a feature in a product, and the interviewer does not say which feature. Describe the dashboard you would build to monitor whether the feature is effective, name the metrics it would include, and explain why each one belongs there. ```hint Effective at what? Before choosing any chart, write down what the feature is supposed to change for users and for the business. Usage counts alone cannot tell you whether that change happened, so ask what else the dashboard must show. ``` ### Clarifying Questions - Will you name the feature, or should I choose one and use it as a worked example? - Who will read the dashboard and how often: the feature team checking it daily during a rollout, or leaders reviewing it monthly? - Is the feature still rolling out, so that the dashboard can compare users who have it with users who do not? - Which decision should the dashboard support: expand the feature, keep iterating on it, or roll it back? ### What a Strong Answer Covers - A stated purpose for the feature that every metric traces back to, instead of a generic list of usage counts. - A layered metric set: one primary success measure, the adoption funnel that leads to it, and guardrails against harm to the rest of the product. - Precise definitions: denominators, time windows, segments, and a way to separate the feature's effect from seasonality or other launches. - Operational design: audience, refresh cadence, alert thresholds and the action each section is meant to trigger. - Data quality checks, so that a broken tracking event is not mistaken for a real change. ### Follow-up Questions - Adoption climbs every week, but the primary success metric stays flat. What would you check first? - A leader asks you to replace the dashboard with a single number. Which would you choose, and what would you lose? - How should the dashboard change once the feature is mature and fully launched?