IT operations KPIs that fit on one page

There's a particular kind of document that exists in almost every IT organisation: the monthly service report. Forty slides. Every metric the ITSM tool can export, graphed. Assembled over two days by someone who dreads it, sent to leadership, opened by half of them, absorbed by none.

And then, in the meeting, the CFO asks a question the deck technically answers on slide 31, nobody can find it, and a follow-up email goes out. The report exists to prove work happened. It doesn't exist to help anyone decide anything.

The fix is not better graphs. It's a harder question: which numbers, if they moved, would change what we do next month? That list is short. For most IT operations it's seven or eight numbers, and they fit on one page.

Choosing the numbers

A KPI earns its place on the page by passing three tests. Someone owns it. It would trigger a different decision if it crossed a line. And it measures an outcome someone outside IT cares about, not an internal activity.

"Number of tickets closed" fails the second test; nobody decides anything differently at 1,400 versus 1,500. "Percentage of tickets resolved within SLA, by priority" passes, because a slide below target triggers staffing or process conversations. Activity metrics describe effort. Outcome metrics describe whether the effort worked.

A balanced one-pager usually draws from four areas. Service health: SLA attainment, major incident count, and time to restore. Customer experience: satisfaction score and, more telling, response rate to the survey. Workload and capacity: incoming volume trend and backlog age, which together predict next quarter's pain. And improvement: repeat-incident rate, or percentage of changes that caused an incident. That last group is the one most reports omit, and it's the one that shows whether the operation is getting better or just staying afloat.

Whatever you choose, cap it. Eight numbers with meaning beat thirty with coverage. The discipline of the cap is the point: every number you cut makes the remaining ones louder.

Leading versus lagging, or: report the smoke, not just the fire

Most service reports are entirely lagging: they describe last month, which nobody can change. The valuable page mixes in the early-warning numbers. Backlog age is next month's SLA miss. Falling survey response rate is next quarter's churn conversation. A rising percentage of "unknown" categorised tickets is your knowledge management fraying quietly.

One of each pair on the page, cause next to effect, and the report shifts from history lesson to steering instrument. That shift is what makes leadership start reading it.

The layout that gets read

One page, four zones. Top left, the headline in words: two sentences a busy executive can repeat in their next meeting. "Service levels held despite 12 percent volume growth. Backlog age is rising in networking and is the number to watch." Writing these two sentences is the hardest part of the whole report, which is exactly why they're valuable.

Then the numbers, each with three elements: current value, trend arrow against last quarter, and a threshold so the reader knows if the number is fine without asking. A number without a reference line is trivia. Green, amber, red sparingly, and only against those stated thresholds; colour without definition is decoration.

Bottom: one short block of "what we're doing about the ambers and reds," with owners. This is the section that converts reporting into management, because it closes the loop between the number and the action in the same field of view.

Assembling this used to be the two-day job that made everyone hate reporting. It's now largely an extraction task: the numbers live in your ITSM tool, and an AI assistant with a fixed template can draft the page, trends, thresholds, and a first pass at the headline sentences, in minutes. The executive-report template set and quality checklist in the Opstimio library exist for exactly this workflow; the manager's job shrinks to verifying the numbers and rewriting the two headline sentences with actual judgement. That's the part that was never automatable anyway.

The quarterly prune

Last habit, quietly the most important one: once a quarter, ask which number on the page nobody has discussed in three months. Remove it. Something is always trying to creep on; the page only stays powerful if it stays one page.

A report that fits on a page, leads with two honest sentences, and pairs every warning with an owner does something 40 slides never did. It gets read, and then it gets acted on. That's the entire purpose of reporting, and it's available to any team willing to delete 32 slides.