Dashboard Design Brief for On-Call Use
Build dashboards that answer questions quickly during an incident.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design a dashboard for on-call engineers. The service and its architecture: [SERVICE_ARCHITECTURE]. Metrics and logs available: [AVAILABLE_SIGNALS]. The questions engineers ask during incidents: [INCIDENT_QUESTIONS]. Specify a layout from top to bottom: a row of health indicators tied to SLOs, a row for the four golden signals (latency, traffic, errors, saturation), a dependency health row, and a recent-changes row (deploys, config changes, feature flags). For each panel give the title, query concept, unit, time window, threshold lines, and the question it answers. Include rules for readability: consistent colours, no more than six panels per row, annotations for deploys. Add a second view for capacity planning. Provide a review checklist to test the dashboard by simulating three past incidents and asking whether it would have shown the problem within five minutes. After the layout, write the five incident questions the dashboard must answer in the first minute (is it down, who is affected, what changed, where is the bottleneck, is it getting better) and mark which panel answers each. Flag any question the available signals cannot answer, and propose the smallest new metric or log field that would close that gap.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.