Measuring progress (KPIs)
What you'll learn
Track the findings burndown, the percent of code cloud-ready, and the count of eliminated unreleased (C2) interface uses — and make that last number visible.
- Findings burndown against the baseline is the primary trend KPI.
- Percentage of code that is cloud-ready shows overall readiness.
- Count of eliminated unreleased (C2) interface uses tracks the riskiest dependencies.
A Clean Core programme needs a small set of metrics leadership can read at a glance. The most important is the findings burndown: how the count of issues is falling against the baseline over time. A burndown that flattens or climbs is an early warning that new debt is being created faster than old debt is cleared.
Two more metrics matter. The percentage of code that is 'cloud-ready' shows how much of the estate would survive the strictest checks today. And the count of eliminated uses of unreleased (C2) interfaces tracks the riskiest dependencies being removed — these are the connections most likely to break on an upgrade.
There is a behavioural lesson worth applying: making 'C2 references eliminated' a visible team metric — a number on a wall, a leaderboard — drives adoption far more than a policy memo. People move what gets measured and celebrated.
Key points
- Findings burndown against the baseline is the primary trend KPI.
- Percentage of code that is cloud-ready shows overall readiness.
- Count of eliminated unreleased (C2) interface uses tracks the riskiest dependencies.
- Making 'C2 references eliminated' visible drives adoption better than a memo.
Examples
Three tiles: findings vs baseline (trending down), percent cloud-ready (rising), and C2 references eliminated this quarter (a celebrated running total). Leadership reads progress in ten seconds.
Source notes: clean-core-curriculum (business synthesis)
Ask Claude
Build a prompt from this lesson + your question and open a fresh Claude chat with it pre-filled — handy for adapting a before/after pattern to your own object.