For as critical as good change management is, it seems to be criminally mishandled when it actually needs to be put into practice. Geoffrey Bowman aims to correct lackadaisical attitudes in a post at his blog, where he outlines how things go wrong and how they can be set right again.
Make the Change, Make it Right
Disruptions of all kinds must be considered when deciding whether to make a leap into new processes. The days where a few IT workers eyeballed a new solution, decided, “Yeah, sounds good,” and went full speed ahead without considering consequences are long over. IT engineers implementing change management these days need to understand the following things:
- The business impact of the change
- Any application functionality impacted
- The rollback plan (if it fails or breaks)
- Who from the business will approve the change
Whether you make use of in-house IT or you outsource, the same best practices apply, along with the same good common sense. Bowman says you should ask for a Current Management Process and an RFC template. When you have IT walk you through their process of change management, you can ensure they know what they are doing and that the business will be (relatively) protected should problems arise. If the answers you receive are unsatisfactory, then you know your change management needs to, uh, change.
Bowman recommends you ask the following questions of IT:
- Who in our business is your primary Change Authorizer?
- Can you show me the most recent RFC for our organization and tell me who approved it?
- For the last change implemented, what was the roll back plan?
- Who in IT has accountability for Change Management?
- Can you show me your internal approval process in the event a roll back is necessary?
You can read Bowman’s full post here: http://geoffreybowman.com.au/2014/07/19/in-focus-it-change-management/