Outcomes of changes - what do you do?

[Berto2002]

I'm moving away from the classic "failed/success" change outcomes and have planned these five. Any comments from other SM users or perhaps feedback on what you guys do and what works in your environments?

Binary 'values' for each and required one-line explanation for any '0' answers

Implementation
- Fully implemented as planned - 1
- Partial implementation or back-out - 0
Impacts on Services / Users
- Impacts as defined and communicated - 1
- Greater or lesser impacts - 0
Detail of steps
- As defined in the CR or procedures - 1
- Fewer, more or amended steps - 0
Scheduling and timing
- Timing went to plan and in window - 1
- The planned timings didn't work out - 0
Purpose / aim
- Fully achieved (fixed/delivered) - 1
- Not fully achieved - 0

These sum into change "Levels" 1-5 in the change board (a kind of gamification) and anything with either the Implementation as '0' or if it has two or more '0' gets pushed in Workflow for a post-implementation review (PIR).

 

In addition, a short written statement representing each positive or negative answer is compiled into an automatic paragraph of the outcome and posted to the resolution and our teams channel such as:

[Berto2002]

We've altered the last one from purpose/aim to:

Validation
- All steps taken and results documented - 1
- Some steps incomplete or results not captured - 0