The Value Dashboard That Measured Nothing
Helios Manufacturing spends $41 million a year on IT, about 4.1% of revenue, above its sector median of 3.2%. Eighteen months ago the CIO launched a value dashboard reporting uptime (99.95%), project on-time delivery (82%), ticket resolution (within SLA 91%), and budget variance (2% under). The board technology committee reviews it quarterly and has grown restless: the metrics are all green, yet inventory turns have fallen, the sales team says quoting takes nine days, and the CFO cannot say what the $41 million buys. Project on-time delivery is measured against baselines reset at each stage gate, and 'on time' includes projects whose scope was cut to hit the date. The CIO's bonus is tied to uptime and budget variance.
1. Critique the dashboard as a value-delivery instrument. Why can it be all green while business outcomes deteriorate?
Read the worked answer
The dashboard measures supply-side activity, not value delivered, and several metrics are constructed to flatter.
- No outcome linkage. Uptime, ticket SLA, and budget variance describe how well IT runs itself. None connects to inventory turns or quote cycle time, the outcomes the business actually cares about. A perfectly available system that supports a nine-day quote process is still a failing service.
- Baseline manipulation. On-time delivery measured against baselines reset at each stage gate means the target moves to meet performance. This is a classic gaming pattern: the metric is true by construction and therefore uninformative.
- Scope-cut tolerance. Counting projects as on time when scope was reduced to hit the date hides the value loss. Delivery of less, later, is recorded as success.
- Incentive distortion. The CIO's bonus on uptime and budget variance rewards stability and underspending, which discourages the investment and change needed to fix quoting and inventory. The incentive and the outcome are in conflict.
- No cost transparency. The CFO cannot say what $41 million buys because spend is reported as a total, not by service and value. Benchmarking at 4.1% versus 3.2% raises a question the dashboard cannot answer.
Conclusion: the dashboard provides assurance about IT operations, not evidence of value. Green here means 'IT is not visibly broken', which is not the question the board is asking.
2. Redesign the measurement approach. Specify what the board should see, how the gaming risks are controlled, and how incentives should change.
Read the worked answer
What the board should see - a two-layer view:
Layer 1: Business outcomes enabled by IT. A small set of measures agreed with business owners, e.g., quote cycle time (target reduced from nine days), inventory turns, order-to-cash duration, and revenue per employee in digital channels. Each has a business owner, not just an IT owner.
Layer 2: Cost and service transparency. Spend by service (run, change, grow) with unit costs where meaningful, benchmarked against the sector median with an explanation of the gap. This answers the CFO's question directly.
Operational metrics remain, but as a supporting appendix for assurance, not the headline.
Controlling gaming:
- Freeze baselines at business-case approval; changes require committee approval and are logged.
- Report scope delivered alongside date, so a scope cut is visible as a variance, not a success.
- Add independent validation of a sample of reported metrics each year.
- Track benefit realisation after go-live against the business case, not just delivery on the day.
Incentives: replace uptime and budget-variance bonuses with a balanced scorecard: a subset of business outcome measures, delivery predictability (with scope integrity), and cost transparency. Underspending should not be rewarded when it defers necessary investment.
Governance: the committee should approve the measures and targets, receive a narrative explaining variances, and challenge any metric that has been green for four consecutive quarters without independent evidence.