数据与研究

measure-dashboard-requirements

product-on-purpose/pm-skills

Specifies what questions a dashboard must answer and the metrics, visualizations, filters, and data sources it needs, so data teams build something that informs decisions rather than displaying numbers. Use when requesting a dashboard or formalizing ad-hoc reporting. For the event tracking that feeds the dashboard, use measure-instrumentation-spec instead; instrument first, visualize second.

  • 767 次安装
  • 770 星标
  • 收录于

安装命令

npx skills add https://github.com/product-on-purpose/pm-skills --skill measure-dashboard-requirements

SKILL.md

Dashboard Requirements

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.

When to Use

  • When requesting a new dashboard from data/analytics teams
  • To define KPI tracking for a product, feature, or team
  • When formalizing ad-hoc reporting into a persistent dashboard
  • Before quarterly planning to specify what visibility you need
  • When onboarding stakeholders who need self-serve analytics

When NOT to Use

  • You need the event tracking that feeds dashboards -> use measure-instrumentation-spec; instrument first, visualize second
  • You are designing an experiment readout, not a standing dashboard -> use measure-experiment-design and measure-experiment-results
  • You want OKR progress scored at cycle close -> use measure-okr-grader
  • The questions the dashboard should answer are not yet agreed -> frame outcomes first with foundation-okr-writer or define-problem-statement