Two New Completion Reasons for Changes

Change managers now have two more options at their disposal in the Completion reason field of their completed changes. The options ‘Failed’ and ‘Disruptive’ have been added. These additional completion reasons fill a gap in the options that were already available before.
The ‘Failed’ option can be selected when the implementation of a change has completely failed and it did not need to be rolled back.
The option ‘Disruptive’ is perhaps the more interesting one. It can be used for changes that were originally completed automatically with the reason ‘Complete’, but were subsequently found to have caused incidents. In such cases, the incidents that were caused by the change can be referenced in the Note field of the change.
Together, these completion reasons can be used by organizations to track the effectiveness of their change management process.