Organization
The executive dashboard
For: team managers · executives and CIOsPrerequisites: None.
An executive committee thinks in euros, customers and risks. This dashboard applies the five principles of the steering lesson of the CIO path to the fictional data of Helinord Précision, the company of the running case. The principles: five indicators at most, three colors, a systematic comparison, a path to the detail, and a question to ask in the review.
Fictional data: Helinord Précision, June 2026.
Technical detail: Order intake availability, as customers see it
| Technical measure | Value | Status |
|---|---|---|
| Order success rate (SLI) | 99.62% | On target |
| Error budget left over 30 days | 24% | On target |
| One-hour burn rate | 0.4 | On target |
| Synthetic tests of the order journey | 100% success | On target |
- Owner
- Sales director, accountable for the SLO
- Question to ask in the review
- Is the SLO phrased in the customers’ words?
Technical detail: Median time to restore major incidents
| Technical measure | Value | Status |
|---|---|---|
| Median time to detect (MTTD) | 6 min | On target |
| Time to acknowledge (MTTA) | 4 min | On target |
| Incidents with a usable trace | 71% | Watch |
| Up-to-date runbooks for critical services | 8 of 12 | Watch |
- Owner
- Platform lead
- Question to ask in the review
- What still slows down diagnosis?
Technical detail: Demonstrable NIS2 measures
| Technical measure | Value | Status |
|---|---|---|
| Critical logs in immutable storage | 92% | Watch |
| Proven time from detection to early warning (drill) | 5 h 40 | On target |
| Privileged accounts reviewed this quarter | 100% | On target |
| Critical suppliers covered by security clauses | 3 of 5 | Off target |
- Owner
- CISO
- Question to ask in the review
- Where do the contractual plans stand for the two measures that depend on suppliers?
Technical detail: Observability cost per order
| Technical measure | Value | Status |
|---|---|---|
| Logs ingested per day | 41 GB | On target |
| Traces kept after tail sampling | 12% | On target |
| Active metric series | 1.9 million | Watch |
| Share of the bill outside production | 14% | On target |
- Owner
- CIO, with the CFO
- Question to ask in the review
- Does cost follow activity, or outgrow it?
Technical detail: Orders entered without errors by customers
| Technical measure | Value | Status |
|---|---|---|
| Customer portal errors measured in the browser | 2.1% | Off target |
| p95 latency of order validation | 3.4 s | Off target |
| Drop-offs at the payment step | 9% | Watch |
| Portal release of 3 June | correlated with the drop | Off target |
- Owner
- Sales director
- Question to ask in the review
- Does the portal release of 3 June explain the drop?
Pick an indicator to drill down to the technical measures behind it.
Try this
Section titled “Try this”- Start with the red indicator, orders entered without errors: the technical detail points to the 3 June portal release. That is the question the committee will ask.
- Open the cost per order: the curve shows the winter peak, the bill that had nearly doubled in the journal of the FinOps lesson, then the return below target.
- Compare the time to restore with its target: amber despite a strong improvement. An indicator is judged against its target, not just its trend.
- Navigate with the keyboard using the left and right arrows: a review is often run on a projector, without a mouse.
What to remember
Section titled “What to remember”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 dashboard is updated continuously, but it is reviewed once a month, with a commentary.
Going further: the bridges, the dictionary between technical signals and business indicators, and the error budget simulator, where the remaining budget and the burn rate come from.