Skip to content

OrganizationBeginner2 min read

Which indicators should leadership see?

Five indicators, three colors, a systematic comparison and a path down to the technical detail: an executive committee dashboard to explore, on fictional data.

For: team managers · executives and CIOsPrerequisites: None.

Reading mode

An illustrative scenario: at the executive committee, the IT department puts forty charts on the screen. CPU usage, latencies, queues. Ten minutes in, the CEO asks: “So, do we have a problem? What do you need from us?” Nobody can answer in one sentence.

An executive committee thinks in euros, customers and risks. What it needs is the equivalent of a car dashboard: a few dials, a color that says whether to pull over and, when a warning light comes on, the option to open the hood. The dashboard below applies that idea to the fictional data of Helinord Précision, the company used as a running case across the site. It follows the five principles of the steering lesson of the CIO path: five indicators at most, three colors, always a comparison (with the target or the previous month), a path down to the technical detail plus a question to ask in the review.

Fictional data: Helinord Précision, June 2026.

Technical detail: Order intake availability, as customers see it

Technical measureValueStatus
Order success rate (SLI)99.62%On target
Error budget left over 30 days24%On target
One-hour burn rate0.4On target
Synthetic tests of the order journey100% successOn target
Owner
Sales director, accountable for the SLO
Question to ask in the review
Is the SLO phrased in the customers’ words?

Pick an indicator to drill down to the technical measures behind it.

  1. Start with the red indicator, orders entered without errors. Drill down into the technical detail and you land on the 3 June portal release. That is exactly the question the committee will ask.
  2. Open the cost per order. The curve shows the winter peak, when the bill had nearly doubled, as told in the journal of the FinOps lesson, then the return below target.
  3. Compare the time to restore service after an incident with its target. It is amber despite a strong improvement: an indicator is judged against its target, not just its trend.
  4. Navigate with the left and right arrow keys. A review is often run on a projector, with no mouse at hand.

An executive dashboard does not show everything you measure. It shows what needs deciding and every figure must be explainable by going down one level. The data updates continuously, but the dashboard is reviewed once a month, with a comment.

Going further: the bridges, the dictionary between technical signals and business indicators, plus the error budget simulator, where the remaining budget comes from along with the speed at which it is being used up (the burn rate).