How to measure change approval adoption after an implementation

Whether change approval is actually happening now, expressed as a number you can put in front of management.

What good looks like, so there is something to measure against: 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.

Ask the people doing the work, not the system. A tool reports what was typed into it, which is a claim about the tool. Whether change approval is followed is a fact about the team, and the team is the only source for it.

Ask the same question again a month later. One measurement is an opinion with a decimal point. Two measurements taken the same way is the first thing anyone can act on.

Where the records help: an approval, authorisation or change advisory column with a name and a date, on the change record itself. That is what a reconstruction reads, and it is also the cheapest ongoing check that the survey answers and the system agree with each other.

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.

How to measure change approval adoption after an implementation

Do this with Adoption Evidence

Related