Guides · Measure

IT KPIs for the board: the measures that matter

Most IT scorecards measure a great deal and change little. This guide helps you choose the five to seven measures a board will read and the eight to twelve the executive committee needs, define them so nobody argues, judge them against a path to target, and avoid the measures that look green while users see red.

Why most IT scorecards change nothing

Most IT functions measure a great deal and learn little from it. The monthly report runs to forty pages, the service levels are green, and the executives are still unhappy. The problem is rarely a shortage of data. The measures describe what IT does instead of what the business gets, nobody acts when they move, and everyone knows how to make them look good.

A scorecard executives read is short (eight to twelve measures for the executive committee, five to seven for the board), balanced (it answers every question executives ask, not only the ones IT is comfortable with), owned (one name per measure) and honest (defined so that it cannot be improved without improving reality).

Start from the questions, not the data

Before choosing any measure, write down the questions the scorecard must answer. For most boards and executive committees they are these seven:

  1. Is technology helping the business reach its objectives?
  2. Do we deliver what we promise, when we promise it?
  3. Are our services reliable, and do people find them easy to use?
  4. Could we keep operating through an attack or an outage?
  5. Is the money well spent?
  6. Do we have the people and skills we need?
  7. Are we getting value from data and AI, safely?

Pick one or two measures per question. Then apply one test to every candidate: who would act differently if this number moved? If the answer is nobody, it is a statistic, not a KPI.

A starter shortlist: seventeen measures to choose from

Choose from this list, adapt the definitions, and keep the rest for team-level reporting. The last column is the most useful: how each measure gets gamed.

AreaMeasureTypeHow it gets gamed
Business valueBenefits realised against approved business casesLaggingBenefits re-baselined downwards after approval
Business valueShare of change spend on the top business prioritiesLeadingProjects relabelled to fit a priority
Business valueStrategic roadmap milestones delivered on timeLaggingMilestones redefined after the fact
DeliveryMajor projects on track, with status set by rules on cost, schedule and benefitsLeadingStatus set by the project manager's judgement instead of rules
DeliveryTime from approval to first release used by the businessLaggingReleasing something small and calling it a release
Service and experienceAvailability of critical services, measured as users experience itLaggingExcluding "planned" downtime taken in business hours
Service and experienceMajor incidents, and how many are repeatsLaggingDowngrading incident severity
Service and experienceUser experience score for the critical servicesLaggingSurveying only closed tickets, or only happy users
Security and resilienceCritical vulnerabilities fixed within the target timeLeadingAccepting risks instead of fixing them
Security and resilienceCritical systems with recovery tested in the last 12 monthsLeadingTesting the easy systems, or a partial recovery
Security and resilienceCritical applications on supported versionsLeadingCounting minor applications to dilute the share
FinancialForecast accuracy: full-year forecast against actual spendLaggingPadding the forecast
FinancialUnit cost trend: cost per employee served, per application or per serviceLaggingMoving costs between units or out of scope
PeopleRegretted attrition in ITLaggingReclassifying leavers as non-regretted
PeopleCritical roles with a ready successor or a second personLeadingNaming successors who are not ready
Data and AIKey data domains with a named owner and measured qualityLeadingOwners named but never active
Data and AIAI systems in use that are registered and risk-assessedLeadingNarrow definition of "AI system"

Aim for at least a third of leading indicators, which move early enough to act on. A scorecard made only of lagging indicators is a rear-view mirror.

Board page or executive scorecard?

The board and the executive committee need different depths. The board page has five to seven measures, weighted to value, major programmes, security, resilience and risk. The executive committee scorecard has eight to twelve and adds delivery, service, money and people. The IT leadership team works from more again. A new CIO often starts with five to eight measures in the first 90 days and grows the set as the data becomes reliable.

Judge each measure against a path, not a single target

Annual targets hide trouble until the year is nearly over. Set a path to target instead: where the measure should be each month or quarter to land on the target. Status then comes from the gap to the path, with a margin agreed in advance, for example green within the margin, amber just outside it, red beyond it. A measure that is behind its path in March is a conversation in March, not a surprise in November.

Define each KPI so that nobody argues

Every measure on the board scorecard deserves a one-page definition card. Arguments about numbers are usually arguments about definitions.

FieldWhat to write
Name and questionThe measure, and which board question it answers
Definition and calculationExactly what is counted, what is excluded, and the formula
Source and frequencyWhere the data comes from, who extracts it and how often
OwnerOne person who explains its movements and proposes action
Baseline, target and pathToday's value, the target and date, and the path to it
ThresholdsThe margins for green, amber and red
Gaming risk and paired measureHow it could be improved without improving reality, and the measure that guards against it

Watch for watermelons

A "watermelon" service is green on its service levels and red in the experience of the people who use it. Classic service levels measure what is easy for the provider to count: availability at the server, response time, tickets closed. Users judge something else: did I get what I needed, how much effort did it cost me, did it stay fixed? Pair every operational measure with an experience measure, and measure availability as users see it, not as the infrastructure reports it.

The same applies when a measure becomes a target. Ask a service desk to close tickets within four hours and tickets will be closed within four hours, solved or not. Pair measures that pull against each other: speed with quality, closure with reopening, cost with satisfaction.

Reporting to the board

  • Two pages, read before the meeting. One page of measures with their path and status; one page of commentary: what moved, why, and what you are doing.
  • Exceptions first. Spend the board's time on the measures off their path, each with an action, an owner and a date.
  • One set of numbers. The CEO, the CFO and the board each need a different view, but from the same measures and the same data, so that nobody receives a different number. The CIO Dashboard Kit builds those views from one set of 38 measures.
  • Stable definitions. Change a definition only once a year, and restate the history when you do.
  • A rhythm. Teams review their measures weekly, the IT leadership team monthly, the executive committee or board quarterly.

Questions

How many KPIs should a CIO report to the board?

Five to seven on the board page, and eight to twelve on the executive committee scorecard. With thirty measures, the three that matter are lost among the twenty-seven that do not. Teams keep their own measures below; they do not all belong on the board page.

What is the difference between a KPI and a metric?

A metric is any number you can measure. A KPI is a metric someone acts on: it answers a question the business asks, has an owner and a target, and changes decisions when it moves.

Should IT KPIs be tied to bonuses?

Use measures to learn before you use them to judge. A measure tied to a bonus quickly stops being a source of information. If you must link them, use a balanced set with paired measures, and keep the definitions out of the owner's control.

How often should IT KPIs be reported?

Monthly to the CIO and the IT leadership team, quarterly to the executive committee or board. Some leading indicators, such as security vulnerabilities, are worth watching weekly inside IT.

Toolkits on this topic

Related