Overview
Most dashboards are built backwards: someone lists every metric they can think of, arranges them in a grid, and calls it a dashboard. The result is a wall of numbers that requires the viewer to do the analytical work the dashboard was supposed to do for them. The decision-maker opens it, scans it, closes it, and asks someone for a summary.
A dashboard that gets used is built around a decision: what question does the viewer need to answer, and what is the fastest path from opening the dashboard to answering it? Every metric, every chart, every filter is justified by its contribution to that path. Metrics that don't contribute to the decision get removed, not added.
The Dashboard Design System Prompt generates a complete dashboard specification: decision-driven metric selection, layout hierarchy, filter and drill-down architecture, alert logic, and a usability validation framework that tests whether the dashboard actually answers the question it was built for.
What you get: - Decision-driven metric selection and prioritization - Layout hierarchy with visual weight allocation - Filter and drill-down architecture - Alert and threshold configuration - Usability validation protocol
Built for: BI developers, data analysts, and product managers designing dashboards that drive decisions rather than display data.