ITSM dashboard for small teams: what to measure

IT Service Management is often presented as something for large organisations: an ITIL programme, a project group, an implementation partner. But the need in a smaller organisation is exactly the same — resolve outages quickly, carry out changes in a controlled way, meet your commitments — only without the budget and headcount to turn it into a programme.

The good news: you do not need that programme to get a grip. What you need is a small number of figures that you look at regularly and actually act on.

Start with the question, not with the chart

Most dashboards that end up gathering dust were built from "what can we display" rather than "what do we want to know". The result is a screen full of gauges nobody opens, because no decision hangs on any of them.

A useful figure meets three conditions: somebody is responsible for it, there is a norm or an expectation, and an action follows when it deviates. If it fails those, it is trivia, not management information.

Seven figures that say something

1. Inflow per period

The number of new incidents per week or month, with the trend alongside. This is your base volume. If it rises steadily, that is either a capacity question or a signal that something underneath is broken.

2. Open incidents, and how old they are

Not just how many are open, but how long the oldest has been open. A single incident sitting at 298 days says more about your process than the average across everything.

3. SLA compliance per priority

Broken down, not as one percentage. The question is not "do we hit 80%", but "on which priority do we not".

4. Resolution time, and where it goes

Total time from creation to closure is the starting point. More interesting is the split: how much of it was waiting on the customer, how much waiting on another group, and how much was actual work.

5. Number of handovers per incident

How often does an incident move from one operator group to another? Every handover costs time and context. A category that is consistently forwarded three times is a routing problem, not a capacity problem.

6. First-line resolution

What share is resolved without escalation? This is the figure that responds fastest to better knowledge articles and better intake — and therefore shows clearly whether an improvement is working.

7. Distribution across operators

To spot imbalance, not to rank people. If one person consistently carries double the load, that is a continuity risk long before it becomes a performance conversation.

Three figures that mostly add noise

• Average handling time across everything. Incidents differ too much. Putting a password reset and a network outage into one average produces a number that never moves anywhere.
• Tickets resolved per employee, as a performance measure. The moment people are judged on this, tickets get split up. You end up measuring your measurement method.
• Customer satisfaction with a 4% response rate. A score of 8.7 based on seventeen responses out of four hundred incidents mostly tells you who bothered to reply.

Starting small works

You do not need a full ITIL programme to benefit from this. An order that works in practice:

1. Register consistently. As long as half the work arrives via a corridor conversation or a chat message, you are measuring part of reality. This is dull and it is the most important step.
2. Create categories you will later want to filter on. Better eight usable categories everyone fills in properly than forty that are half used.
3. Automate the repetitive work. Password resets, standard requests, recurring reports about the same system. This buys time immediately and makes your figures cleaner.
4. Look at the same figures every month. The value is in the repetition: a figure you look at once is trivia, a figure you look at twelve times is a trend.

What a dashboard adds to this

A dashboard turns these seven figures into something you can glance at in passing, rather than something you have to produce monthly. That sounds like a small difference, but it changes the conversation: from looking back to steering.

What matters is that the figures are drillable. The moment somebody in a meeting asks "which incidents are those, then?", you have to be able to show it on the spot. If you cannot, the discussion stays stuck on whether the number is even right.