Why change approval stalls after go live
It rarely stops all at once. It decays, and the decay has a shape.
The usual failure: Approval happens verbally in a weekly meeting and is written down nowhere. The first time it matters is an audit or an outage, and there is nothing to show.
It is worth being precise about the difference between not started and decayed. A practice that never began needs a decision. A practice that began and slid back needs to know which week it slid, and who noticed.
What it should look like instead: Changes carry a record of who approved them and when, approval happens before the change rather than after, and standard changes are pre approved so the process is not routinely bypassed.
The measurable version of this is a score that falls between two rounds in one area while the rest hold. That is specific enough to ask three people about directly, which is how it gets fixed.
Do this with Adoption Evidence
One engagement free. Curate the questions, baseline the team, and generate a report where every number traces to a response or a file. No card.
Already have a The Art of Service account? Sign in.
Related
- Why incident categorisation stalls after go live
- Why incident prioritisation stalls after go live
- Why incident ownership stalls after go live
- Why service level targets stalls after go live
- How to measure change approval adoption after an implementation
- Reconstructing a change approval baseline from records you already have