Change closure codes

[LesleyMills]

We have the standard codes:
Backed Out
Failed
Rejected
Successful
Withdrawn

But I'm wanting to add a code that covers successful changes (ie they fix what they're supposed to or do what they're supposed to) but also cause incidents. ie they weren't properly tested or planned. I was thinking of a code 'successful but caused issues' or similar and didn't know if anyone has implemented something like this?

Making staff choose between 'failed' and 'successful' they're going to pick 'successful' every time, ignoring the ripple effect their change caused as by their recogning it was a success. Having this new code is more likely to be used if it has successful in it.

[Diarmid]

Your additional code will allow your staff greater accuracy but the crucial point is what you use the information for. You need a set of codes that will help you to improve your processes.

There are some other threads on this topic:
Definition of Partial Success vs Failure from 2008
Conducting Post-Implementation Review from 2011
Successful change: definition? from 2011
Change failure from 2012

There may be more and I only looked in the Change Management section.
Using "failed" as a code does not do much for proper analysis. For a start do you mean that the implementation failed or that the change did not deliver on its purpose?

Also a change that takes longer and more resources than planned, is still a success by other criteria but you would want to look at the reasons for going over budget and behind the plan.

The same with changes that cause incidents.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718