Mastering IT Change Management Step Two: Moving from Ignorant Anarchy to Informed Anarchy

Mastering IT Change Management Step Two:Moving from Ignorant Anarchy to Informed Anarchy

Its been a while, right interesting article -  a description how a IT support Organisations beginning steps into implementing a change management process.

I like the way the author likens the first steps of setting something like this up to Ignorant Anarchy,

I can see the Authors descriptions very clearly and liken them to a few things I have seen first hand.

With systems having changes implemented and no one being informed and going through a troubleshooting process only to find some one form down the back has changed a setting and not told any one and is the cause of the incident.

Then this morphs into everyone being informed some people caring when it doesn't even affect them tying up the help desk with unneeded queries, but on the other hand in the past they have been affected by changes that weren't meant to affect them but did, it puts you in a  interesting position when you have to reassure them it wont affect them.

I cant imagine working in a large business with 60-75 changes going on in a month it must be anarchy as the authors describes when there is none or trying to implement change management process.

Then bliss once reaching step four "Mastering IT Change management".