Dashboard Requirements Planner

When to use it

Use before dashboard design to prevent a collection of charts that lacks ownership or decision value.

What Claude needs

• client-context.md for business background
• Named users, decisions and meeting cadence
• Candidate metrics and current reports
• Data availability, access rules and refresh constraints

Method

1. Interview user groups around decisions, triggers, questions and required actions.
2. Convert needs into user stories with measurable acceptance criteria.
3. Prioritise metrics using decision value, actionability and data readiness.
4. Define views, filters, drill paths, alerts and comparison baselines.
5. Map every element to a governed definition, source and refresh schedule.
6. Create a wireframe brief, validation plan and phased delivery scope.

Output format

Deliver a requirements table with user, decision, question, metric, view, source, cadence and acceptance test. Add page-level wireframe notes and scope boundaries.

Quality checks

• Every visual element supports a named decision or action.
• Metric definitions and source readiness are confirmed.
• Accessibility, permissions and small-screen needs are addressed.