Change Management documentation covers a lot of areas where it is applicable. There is the 'know how's' and the 'know whats' that is clearly documented. People are trained on phase-wise approaches and the organization is all set for anything from a business transformation and re-engineering to new technology adoption.
Process documentation and training manuals have the ability to give users the confidence that all avenues are covered and that there are no exceptions to the process. I would really like to see process documentation or CM documentation have caveats spelled out for the user. Like recipes have allergy alerts spelled out.
A robust change management initiative is not just one that has all the do's in place. Its one that has all the dont's listed as well.
Change management does not work in spaces that have bad managers. Change management does not work in spaces where the team is still in the storm phase of the forming. It would not work where leaders are not sure about the change themselves. It would never work if the employees have lost their 'trust' about what the company would do for them. This list can go on. The important take-away however, is the fact that, Change management needs to have the management of the areas we cannot change done before we manage the areas we can change. That would be good change management!
