Change Delivery Scorecard

A change delivery scorecard is a one-page view of how a change is landing, refreshed at a set rhythm and reviewed by the people who can act on it.

The word "balanced" matters. Robert Kaplan and David Norton argued in 1992 that financial results alone report the past too late to steer by, and proposed a balanced set of measures alongside them. A change scorecard applies the same logic: benefits arrive last, so the scorecard also tracks the readiness and adoption measures that predict them, and the risks that threaten them.

Without a scorecard, change progress tends to be reported as activity: briefings held, people trained.

A change delivery scorecard therefore shifts reporting from what the team did to what is happening in the organization.

A common structure groups measures into four areas. It is a generic structure, not the layout used in the APMG course text.

Benefit measures come from the business case. In benefits management practice, such as John Ward and Elizabeth Daniel's approach, each benefit has a named owner and a way of measuring it.

For each measure, the scorecard shows the target, the current value, the trend since the last report, a status and an owner for any action.

A change scorecard that covers all four areas lets sponsors see early warnings and confirmed results side by side.

Harbourside Council is merging three local offices into one service centre.

1. Start from the objectives. The business case expects shorter waiting times and fewer repeat visits.
2. Pick one to three measures per area. For example: staff confident with the new case process (readiness), share of cases logged in the new system (adoption), average waiting time (benefits).
3. Take a baseline before the change, and agree targets.
4. Break results down by the groups identified in the impact assessment.
5. Set a rhythm, such as every two weeks before go-live and monthly afterwards.
6. Agree triggers: what result leads to what action, and who acts.

The change delivery scorecard is then reviewed at each steering meeting, with the change manager explaining what the figures mean.

• Too many measures. A scorecard nobody can read in five minutes is not a scorecard.
• Activity only. Counting emails and workshops says little about whether people are changing.
• Averages that hide groups. An overall adoption figure can conceal a team that has not started.
• Status without trend. A green rating that has been falling for three periods deserves attention.
• Measures that invite gaming. When a number becomes a target, people may improve the number instead of the behavior.
• No owner. A red status with no named owner rarely changes.

Validated instruments can strengthen the readiness area, such as the readiness scale developed by Daniel Holt and colleagues.

A change delivery scorecard works best when it is small, broken down by group and tied to decisions.