Change Management Doesn't Replace PRINCE2, MSP or PMQ. It Sits Somewhere They Don't Reach

A project manager on one of our courses put it plainly recently. She'd been through PRINCE2 Practitioner two years earlier, ran a tight stage-gated programme since, and had just been told by her L&D team that she was booked onto Change Management Foundation next quarter. Her first question wasn't about the syllabus. It was whether anyone had checked this wasn't just PRINCE2 again with different branding.

It's a fair question, and a common one. PRINCE2, MSP and PMQ all claim to cover stakeholder engagement in some form. PRINCE2 has a communication management strategy. MSP talks about benefits realisation and organisational change. PMQ's syllabus touches stakeholder management directly. So it would be reasonable to assume that a dedicated Change Management qualification duplicates ground already covered, just with a different logo on the certificate.

That assumption holds up right up until you look at what actually goes wrong on projects that are governed well.

We worked with a case, generalised here rather than tied to any one organisation, that's fairly typical. A mid-sized utilities company ran a systems migration under a properly resourced PRINCE2 environment. Stage boundaries were respected. The highlight reports were accurate. The project board signed off each gate on schedule, and by the project's own governance measures, it delivered on time and within tolerance. Six months after go-live, adoption of the new system sat at around forty percent. Staff had reverted to workarounds and shadow spreadsheets almost as soon as the training sessions ended. The project had been managed correctly. It had not been adopted.

That gap is what a Change Management qualification actually addresses, and it's a narrower, more specific thing than "stakeholder engagement" as a syllabus line item suggests. PRINCE2's communication strategy tells you who needs to be told what, and when. It does not tell you how to structure a change so that the people affected by it move through denial, resistance and adoption in a way that sticks. MSP's benefits realisation plan tells you what value you're expecting and how you'll measure it. It does not tell you how to build the coalition of sponsorship that makes people actually change their behaviour once the technical delivery is finished. PMQ's stakeholder management content is broader still, closer to an awareness layer than an operating method.

Change Management Foundation and Practitioner exist because none of that is incidental detail. It's a discipline with its own models, for reading where an organisation actually sits in a change curve, for building sponsorship that survives contact with a sceptical middle-management layer, and for designing communication that changes behaviour rather than simply informing people of a decision that's already been made. None of the governance frameworks teach this because none of them were built to. They were built to control scope, schedule, risk and assurance. Change Management was built to control something else: whether the change actually takes, once the project itself has closed.

This is also why the two don't compete for the same slot in a career. A PRINCE2 Practitioner who adds Change Management isn't collecting a second certificate that says the same thing twice. They're closing the specific failure mode that governance frameworks are structurally unable to close, because it was never their job. The utilities case above wasn't a PRINCE2 failure. Every stage gate had been cleared correctly. It was a gap sitting exactly where PRINCE2's remit ends and something else needed to begin.

The same logic applies whether you're coming from MSP or PMQ rather than PRINCE2. Programme-level benefits realisation and PMQ's broader competency framework both assume, rather than build, the specific capability to move a group of resistant humans from their current state to the new one. Change Management doesn't ask you to abandon governance discipline. It asks you to add the one layer governance was never designed to hold.

So the honest answer, for anyone weighing this the way that PM was, is that these qualifications sit alongside PRINCE2, MSP and PMQ, not underneath them and not in competition with them. They cover a different failure mode entirely, one that shows up after the stage gates have all been passed and the project has technically succeeded by every measure the governance framework was built to track. If you want to talk through where that gap sits in your own delivery environment, get in touch about your training options.

Andre Malowney is a project management trainer accredited across PMI, APMG, APM and PeopleCert frameworks, working with both traditional plan-driven practitioners and Agile delivery teams. Find him on LinkedIn: www.linkedin.com/in/andremalowney.