Sources of data:
As I cull over job listings for change management positions, it seems the job market is similarly confused. At times it looks like project manager, a person implementing technology, one who helps others use a new technology, etc.
Here is a friendly Wikipedia definition:
Change management is the process during which the changes of a system are implemented in a controlled manner by following a pre-defined framework/model with, to some extent, reasonable modifications [1].
This definition helped add the concept of using a model or process. Unfortunately that too is pretty generic. This definition does not mention two primary components I find on the job boards - people and technology.
My personal understanding is that change management is the experience of working with the people in an organization through a transition or change process. This implies that there is a structure or framework to change. Since we live in a technology age, often I would assume that a change would impact existing or require a new tech system.
Here is what I found after looking at some colleagues' blogs (from Garrett Gitchell's blog on Vision Work).
He suggest that when doing Change Management - begin with the end in mind. This is similar to any team process, one needs to be clear on their purpose or goal. In doing so, keep in mind the final state any project or piece of work has in mind. Then similar to project management map back the process. Garrett emphasizes the difference between Change Management and Project Management (PM). PM is a necessary component of Change Management, but Change Management is more strategic in nature.
Therefore, change managers need to be involved in the formulation of a widespread process and its change implications on a larger system. For example a new technology often has change impacts on more than just the people who use the platform. Organizations are systems and therefore, should one implement a new technology in one department or office its impact goes beyond that entity. A change manager would be aware of this and ideally raise it as a consideration to clients, versus a PM would may be more tactical for that office/department.
In the end we are talking about a change agent that is a partner and support function to the existing system. This person's role is to help facilitate the change and improve the system towards healthier and more efficient states. The bottom line is fundamental component driving decisions. Why go through change? What is the purpose of it? Who can help you devise a system and process? Is it worth slowing down to stratagize and consider the various impacts of a change? I say yes - this can make all the difference to future change efforts.
And still in the end organizations are dynamic and ever changing. Therefore, a long term consideration would be for organizations to invest in build change capabilities. That is what ultimately will make the organization last and adapt to the ever changing environment and unforeseen variables. So how does one do such a thing? One starting point that has been a nice guide for me is to reference Chris Worley's book, "Built to Change.
In the end there are various understandings and interpretations of the concept of change management. One thing seems certain this term is about change from one state to another - and organizations are constantly involved in this process.
