measure-dashboard-requirements

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Dashboard Requirements
3 
4A dashboard requirements document specifies what questions a dashboard should answer, what metrics it displays, and how data should be visualized. Clear requirements help data teams build dashboards that actually inform decisions rather than just displaying numbers.
5 
6## When to Use
7 
8- When requesting a new dashboard from data/analytics teams
9- To define KPI tracking for a product, feature, or team
10- When formalizing ad-hoc reporting into a persistent dashboard
11- Before quarterly planning to specify what visibility you need
12- When onboarding stakeholders who need self-serve analytics
13 
14## When NOT to Use
15 
16- You need the event tracking that feeds dashboards -> use `measure-instrumentation-spec`; instrument first, visualize second
17- You are designing an experiment readout, not a standing dashboard -> use `measure-experiment-design` and `measure-experiment-results`
18- You want OKR progress scored at cycle close -> use `measure-okr-grader`
19- The questions the dashboard should answer are not yet agreed -> frame outcomes first with `foundation-okr-writer` or `define-problem-statement`
20 
21## Instructions
22 
23When asked to specify dashboard requirements, follow these steps:
24 
251. **Define the Purpose**
26…