Related Posts
About that time 🤝

Additional Posts in Change Management
Any open OCM roles within this network?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
About that time 🤝

Any open OCM roles within this network?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

In my experience, change control has be at a technical level (e.g., we are changing a technical design component / process) which needs to be reviewed and approved by a design review board.
Change management is different but related, and would include accounting for the mitigation strategies required (comms, training, role / org design, etc.) and is more “people facing”
Change control is for deploying changes to technology solutions (applications, infrastructure, etc). It's meant to be a way of reporting a change, confirming testing was complete, and verify the deployment will not impact business operations across the enterprise (think of blackout windows). Technology focus.
Change management is how people will respond to the change. It's the art of developing communications to describe changes to get buy-in and to inform. Organizational focus.
While the answers above are correct, I'd also add that Change Control usually requires an ITIL certification and understanding of cybersecurity implications. It's a completely different process to approve technical changes, but can sometimes be referred to as change management in technology teams. I've seen some companies trying to conflate the two lately or get someone to do both. Though it's possible to have change management on change control, you obviously need to be sure the organization knows the difference and that you're trained in both if you decide to take on such a situation as it's two different roles.
This is one of the biggest misconceptions about OCM versus change control. If you work with IT, you will likely need to clarify your role (perhaps several times) because many people just don't understand what we do.
I have learned that when I go to a new project, I have to roadshow what my role is and what I need from the tech folks. You will also need to embed yourself in the tech/pmo meetings so that you have a seat at the table to hear what's happening and advocate for end users. Good luck and fight the good fight. Educate the tech folks; they can be your biggest allies once they understand what value you bring to support adoption.