<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
A 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.
-
Define the Purpose
Start with the questions this dashboard should answer, not the charts it should show. What decisions will this dashboard inform? A dashboard without clear purpose becomes a vanity metrics display.
-
Identify the Audience
Specify who will use this dashboard, how often, and in what context. An executive weekly review has different needs than a team's daily standup board.
-
Specify Key Metrics
For each metric, document: name, business definition (in plain language), calculation formula, data source, and baseline/target values. Ambiguous metrics lead to misaligned dashboards.
-
Design Visualizations
Recommend chart types based on what the data should communicate. Time trends need line charts; comparisons need bar charts; compositions need pie/treemaps. Include dimension breakdowns.
-
Define Filters and Segments
Specify what drill-downs users need: date ranges, user segments, product areas, geographic regions. Anticipate the "slice and dice" questions users will ask.
-
Document Data Sources
Identify where data comes from and any known data quality issues. Note latency requirements.does the dashboard need real-time data or is daily refresh sufficient?
-
Set Permissions and Access
Determine who can view what. Some metrics may need restricted access. Consider both security requirements and organizational politics.