How Change Management, Managing Benefits and Better Business Cases Fit Together

Most people who come across these three qualifications treat them as a shortlist. Change Management, Managing Benefits, Better Business Cases. Pick the one whose title sounds closest to your job title, do the course, move on. It is a reasonable instinct. Nothing in how they are marketed suggests otherwise.

It is also the wrong way to think about them.

I see the confusion most clearly in conversations with people who already hold one of the three and are trying to work out whether they need another. A programme office lead with Managing Benefits keeps being asked to write a business case and assumes Better Business Cases must be the more senior version of what they already know. A change manager assumes Managing Benefits is just their discipline with a different acronym stapled on. Both assumptions are understandable. Both are wrong in a specific, useful way that takes a bit of unpacking.

Start with what a business case actually has to survive. It gets written before anything is spent, when the argument is still speculative. If it clears that hurdle, money and people get committed, and the organisation now has to make good on a claim it made on paper. Time passes. The delivery happens, or partly happens, or gets delayed, or gets descoped. At some point somebody has to answer a question the original business case didn't need to answer at the time it was written: did the thing we said would happen, actually happen. That is three distinct moments, not one long process wearing different hats, and each moment has produced its own qualification because each moment fails in its own particular way.

Better Business Cases lives at the first moment. Its job is to stop an investment being approved on the strength of enthusiasm rather than evidence, which is why the Five Case Model insists on testing strategic fit, value for money, commercial viability, affordability and achievability as five separate questions rather than one combined pitch. A case can be commercially elegant and financially indefensible. It can be affordable and strategically pointless. Treating those as one blended judgement is exactly how weak investments get approved by people who genuinely believed they were being rigorous.

Managing Benefits sits at the third moment, the one most organisations quietly skip. A business case forecasts benefits to get approved. Managing Benefits exists because forecasting and delivering are not the same act, and very few organisations have a disciplined way of checking, months or years later, whether the benefits actually landed. Without that discipline, the business case becomes a one-off performance rather than a commitment anyone is held to. I have sat in enough post-implementation reviews to know how often the honest answer to "did we get what we said we'd get" is a shrug, because nobody owned the tracking once the delivery team moved on to the next thing.

Change Management is different again, and this is the point most people miss entirely, because it isn't really about the investment case at all. It's about the fact that benefits are rarely delivered by a system or a process on its own. They're delivered by people changing what they do, which system they log into, which report they trust, which meeting they now attend that didn't exist before. A perfectly forecast, perfectly tracked benefit still fails to materialise if nobody adjusts their behaviour to actually realise it. Change Management is the discipline of making that adjustment happen deliberately rather than hoping it happens on its own, which is why its APMG syllabus, refreshed substantially in its March 2024 overhaul, leans so heavily on stakeholder engagement and sustained adoption rather than communications planning alone.

Put the three together and the shape becomes obvious. Better Business Cases decides whether the investment deserves to happen and on what terms. Change Management is the mechanism by which the organisation actually earns the benefits it promised, by getting people to work differently. Managing Benefits is the discipline that checks, honestly and after the fact, whether that promise was kept. Remove any one of the three and a predictable failure shows up. Skip Better Business Cases and you fund things on optimism. Skip Change Management and you fund the right things but nobody changes how they work, so nothing lands. Skip Managing Benefits and you never find out either way, and the next business case gets written with exactly the same blind confidence as the last one.

This is why I don't teach these as three alternatives to choose between. A programme office that only has Better Business Cases can approve good investments and still watch them fail quietly, because nobody was accountable for the human side of delivery or the honest count afterwards. A change manager who has never sat inside a Five Case Model conversation will keep being handed business cases that were never stress tested, and will spend their energy managing adoption of something that was underfunded or badly scoped from the start. The gap isn't a training gap. It's a lifecycle gap, and it shows up as the same project succeeding on paper and disappointing in practice.

None of this means everyone needs all three. A sponsor accountable for signing off investment decisions needs Better Business Cases fluency more than the other two. A delivery lead responsible for landing adoption in a resistant business unit needs Change Management. Someone running a benefits realisation function across a portfolio needs Managing Benefits specifically, and probably needs to understand the other two well enough to challenge them. What changes the outcome isn't holding every qualification. It's understanding which moment in the lifecycle you're actually operating in, and recognising when the failure you're looking at didn't originate there at all.

If you're trying to work out where you actually sit in that lifecycle, or which of the three would close the specific gap you keep running into, get in touch and we'll talk through what fits.

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.