

Most project owners and managers by now have recognised good Change Management as a crucial success factor for any systems implementation project. People talk a lot about it. However, looking around, I can’t see very much done about it, let alone done successfully. Why is that so?
I found that one reason is most people are aiming to high, when thinking “Change Management” and then quietly abandon a task that’s beyond their capabilities and budget, but they can’t admit it. In other cases, “Change Management” is seen as a fluffy intangible exercise for the weak at heart that mustn’t be allowed to take resources away from designing processes or programming reports and web dynpros. These people give it about the same priority as exhibiting pieces of art in the project room.
In both cases, “Change Management” is only seen as the really big thing few people actually are able to get right: engaging the whole workforce, big communication programmes, changing people’s mindsets, changing values, cultural change. This is all very important and may be necessary for some projects. However, this is usually the wrong level to attack change management for the average IT project, because:
Then use the information collected to

1