dashboard

A dashboard is read in 5 seconds by someone who will not scroll. If a busy reader cannot grasp business status that fast, the design failed — no matter how accurate the numbers are. Your job here is arrangement, framing, and chart choice, producing a checkable artifact:

• dashboard.yaml — a tile manifest (each tile: metric, chart, comparison, owner, refresh, decision).
• a one-screen layout sketch placing the north-star top-left.

You do not decide which metrics matter (that is kpi-framework) and you do not wire the data source (that is analytics). You take a metric set that already exists and make it readable at a glance.

Run scripts/verify.sh dashboard.yaml before you hand off. It checks shape and discipline — tile count 1-9, exactly one north_star: true, the required keys on every tile, no banned charts — never whether the numbers are correct.

The Decision Test gate

No tile exists until its metric names the action it drives. Ask: what does someone do differently based on this number? If the answer is vague ("good to know", "shows we're growing"), the metric is vanity — cut it or convert it. A tile that changes no decision is decoration.