dashboard-redesignlisted

# Dashboard Redesign Design a decision instrument, not a wall of metrics. Preserve useful density, expose the comparisons that matter, and make data quality and scope legible. ## 1. Establish the decision model Identify: - primary role, expertise, frequency, and environment; - decisions and actions the dashboard must support; - monitoring cadence and acceptable time to notice; - metric definitions, owners, source, freshness, and latency; - required comparisons, targets, thresholds, and segments; - downstream workflow from signal to investigation to action; - devices, display duration, accessibility needs, and export requirements. If these are unknown, state assumptions and mark metric semantics for owner validation. Never infer that a visible number is a KPI. Do not invent viewport baselines, breakpoints, refresh thresholds, metric cutoffs, targets, card counts, or density values. Define the decision or content condition first; map it to an existing product constraint only when supplied or inspected. Classify the surface using [references/dashboard-models.md](references/dashboard-models.md). A monitoring board, executive scorecard, operational queue, and analytical workspace need different density and interaction. ## 2. Inventory decisions before widgets Build a compact matrix: `Decision | Signal | Comparison | Grain | Freshness | Action | Failure cost` Remove or demote data that does not support a scoped decision, diagnosis, or required reporting obligation. Ident