Before we begin looking at Change Management topics in detail, it's important to understand what exactly we're here to discuss. What is Change Management?
First, if you're reading this because you think "Change Management" and "Change Control" are the same thing, you're in the wrong place. As a Change Manager, I am not the person who decides what changes can be made to a system after design freeze. Sorry, tech. guys. That's a different blog.
I also do not define Change Management as "that touchy-feely stuff" or "the team that arranges parties."
Some people will define Change Management by listing its most common components: Communications, Training, Executive Sponsorship, Stakeholder Management, Organizational Design, and, in some cases, Project Management, and Continuous Improvement. That's the equivalent, however, of defining a car as four tires, a steering wheel, and a motor.
If you read books and articles on Change Management, each one will provide a slightly different definition. They are interesting and well worth reading, but for the purposes of this blog, here is the official Emily Carr definition, "Change Management is the set of processes and activities used to help organizations, teams, and individuals accept, adopt, and master a change to behaviors, processes, and/or technology."
Do you agree? What's your definition of Change Management? Post your definition in the comments section below this post.
Ask 100 people to define Change Management, and you'll get 100 different definitions. At the end of the day, the definition is just semantics. What really matters is whether you can implement a Change Management program in a practical way that allows you to support your organization in successfully achieving its goals. Whether you're a Change Manager, a consultant, or the tech. guy who was told to "figure out some Change Management stuff," this blog will help address common issues and topics you're likely to run into along the way.