How would you decide which metrics to include on a company-wide product dashboard?
Model answer
Model answerA company-wide dashboard should answer one question: is the business healthy? That means fewer metrics, not more. I'd start by asking each stakeholder group what decision they need the dashboard to help them make — and then ruthlessly cut anything that doesn't serve a decision. I'd organize around three levels: company health (1–2 metrics), product health (3–5 per area), and early warning signals. Every metric has an owner and a freshness date.
Framework · Dashboard Design
- DDecision-first design
What decisions should this dashboard enable? Start there, not with data - LLevels of detail
Company / product area / early warning — three tiers, clear separation - OOwnership and freshness
Every metric has an owner and a freshness indicator — stale data misleads - CCut ruthlessly
If a metric doesn't drive a decision, remove it — more metrics = less clarity
Related questions
- How would you build a metrics framework for a newly launched product with no historical data?
- How do you prevent metric gaming in your team?
- How would you present mixed results to a board when some metrics improved and some didn't?
- How do you set up a metrics culture in a team that doesn't trust data?
- How would you build the business case for a new analytics tool your team needs?