IT dashboards drift toward metrics that are easy to collect rather than ones that change decisions. The test for every metric here is simple: if it moved, would anyone do anything differently?
Keep it to around a dozen metrics. A dashboard with forty metrics gets skimmed. Choose the ones where a change would trigger a decision, and keep the rest available on request rather than on the page.
Set thresholds as well as targets. Define what counts as amber and red. Without thresholds, every discussion restarts the argument about whether a number is acceptable.
Write commentary for anything off-target. A red cell with no explanation invites the wrong question. One sentence on cause and action converts the review from interrogation into a decision meeting.
Here's a preview. Unlock the free download to get all 4 sections (3 more below).
| Metric | This month | Last month | Target | Amber | Red | Trend | Commentary |
|---|---|---|---|---|---|---|---|
| P1 incidents | 2 | 1 | ≤2 | 3 | 4+ | ↑ | Both from the same storage fault; fix deployed 14 Oct |
| Mean time to restore (P1) | 3h 10m | 4h 40m | ≤4h | 4-6h | >6h | ↓ improving | Runbook rewrite paying off |
More free templates IT teams use alongside this one.
Service desk reporting usually optimises for speed, which is measurable, rather than for demand reduction, which is valuable. The most useful number on this sheet is which ticket categories keep recurring.
An IT budget presented as a list of line items invites line-by-line cuts. Split into run, grow, and transform, it becomes a conversation about what the business is choosing to fund, which is a far better conversation to be in.
IT roadmaps become wish lists because they list initiatives without capacity. Showing what the team can actually deliver alongside what has been requested is what turns the roadmap into a prioritisation conversation.
Ones where a change would trigger a decision: time to restore service, SLA attainment, critical vulnerabilities past remediation SLA, patch and MFA coverage, change success rate, and cost per ticket. Metrics nobody would act on belong in the appendix.
Around a dozen on the page, grouped into service, security, delivery, and cost. Longer dashboards get skimmed, which means the important movements are missed alongside the trivial ones.
Because a red cell without explanation prompts the wrong conversation. One sentence naming the cause and the action already underway turns the review into a decision meeting rather than an interrogation.
