Story points completed is a measure of how busy the theatre company was, not whether the play was any good. Transformation needs outcome measures. Activity metrics are how you decorate a stall.
Outcomes, not agile theatre
Vanity set: number of teams 'now Agile,' story points burned, ceremony attendance, training seats filled, a maturity score someone invented in a spreadsheet. Those can rise while customers wait longer, defects escape, and the budget process remains annual and fictional.
Outcome set, pick a few: lead time from idea to customer-usable increment, change fail rate, time to restore, customer outcome measures you already claim to care about, employee retention in the affected streams, and the time it takes to make a funding decision. If those are flat, the transformation is a costume.
Do not drown the board in twenty new charts. Two or three outcome measures plus a short list of systemic impediments is enough. A transformation dashboard that needs a narrator and a legend the size of a novella is not transparency. It is camouflage.
Baseline before you celebrate
Measure the old system first. If you do not know last quarter's lead time, you cannot claim this quarter improved it. 'It feels faster' is how coaches keep contracts and how cynics stockpile jokes. Instrument the path. Ugly data is still data.
Separate team-level flow metrics from enterprise transformation metrics. A team can improve its cycle time inside a system that still takes nine months to fund the next slice. Both views are useful. Only one of them tells you whether the company changed. Do not let local improvement launder a global stall.
Targets that punish honesty will recreate the old RAG fiction. If amber is a career event, everything will be green until it is a press incident. Prefer ranges, trends, and narrative about what you are trying next. Leadership does not need a made-up agility percentage. Leadership needs to know whether the constraint moved.
What to stop reporting — and what to do with the truth
Stop reporting transformation progress as a percentage complete of a Gantt called 'Agile Journey.' A culture and a funding model are not a tunnel you bore to 100%. Report decisions made: envelopes shifted, gates retired, value streams named, incentives rewritten. Decisions are the increment of a transformation.
When the measures say nothing moved, the next action is not a louder town hall. Return to the stall points: funding, design, culture. Measure the constraint. If Finance still needs a predictive case for every slice, that cycle time is your metric. If a silo still owns a mandatory queue, that wait time is your metric.
Close the loop with the portfolio. A transformation that cannot stop a workstream that contradicts the new model is not a transformation. It is a parallel universe with a Slack channel. Use the selection verbs. Then keep measuring. This course does not end with a certificate that the organisation is now Agile. It ends with a habit of telling the truth about whether value got faster, cheaper, or more honest.
Course complete — what's next
Measure customer and system outcomes, not ceremony theatre. Baseline first. Report decisions and constraint movement. Story points are not transformation.
You now have a working view of why enterprise agile change stalls and how to start, fund, design, and measure without buying another logo. Use one outcome measure and one constraint on a live change. Advanced scenario work is next if you want to pressure-test the judgement.