Change management is of no value – is that true? I know as a PM that you see change managers as a burden on your project. I know that you see that they are additional cost and resourcing that you don’t really need on your project. You don’t really get what this ‘change management’ is really about which is why you don’t see the value in it.
Do you see yourself as a ‘Project Manager’ or a ‘Change Manager’ or a ‘Project Manager managing change’?
It is interesting considering the context of these titles. Project Managers are seen as people who manage projects, whilst Change Managers are seen as people who manage change related to projects, or as the outcome of projects. But on a number of projects there is only the Project Manager managing change.
This week I have seen the real value of communicating. By explaining to the team “Why communicate change?” they have come on board fully for the project.
What is change management?
Change management is one of those terms that most people know very little about. Some people would tell you there is some framework, others would be able to tell you about the steps involved from the famous text by Kotter on managing change, but my instinct from working with project managers and the business alike is that they don’t really understand it.
Change management is a project responsibility because every project involves some form of change. I haven’t yet found a project that doesn’t.
Most projects are done to address something, be it a system or process, that isn’t working and needs to be changed. Projects either (a) look at the change from the system or process perspective and forget about the people aspect of it, or (b) they forget about the change aspect altogether and think that by making the change to the system or process and dropping it back into the business that it will work fine.