1.3 Change Management, Benefits and Dis-benefits

The reason we need change is to achieve some kind of improvement. CM3 makes that link explicit at the very start of the syllabus, and the exam tests the definitions word by word — so learn them precisely rather than approximately.

The two definitions

Benefit: "the measurable improvement from change, which is perceived as positive by one or more stakeholders, and which contributes to organizational (including strategic) objectives".

Dis-benefit: "the measurable result of a change, perceived as negative by one or more stakeholders, and which detracts from one or more organizational objectives".

Three features of these definitions repay attention:

1. Measurable. Both benefits and dis-benefits must be measurable. "Improved morale" is not a benefit until you can say how it will be evidenced. This is why benefits work and change analytics are connected.
2. Perceived by one or more stakeholders. Perception is part of the definition. The same outcome can be a benefit to one group and a dis-benefit to another. A new automated approval process is a benefit to the finance director and a dis-benefit to the team of approvers whose role shrinks.
3. Contributes to or detracts from organisational objectives. A change that produces measurable improvements nobody in the strategy cares about has not delivered a benefit in this sense.

A dis-benefit is not a risk and not a cost. A risk might happen; a dis-benefit is a consequence you expect. A cost is what you spend to make the change; a dis-benefit is a negative result of the change having happened. Exam questions sometimes offer all three as options.

The outputs, outcomes, benefits chain

CM3 presents a simple chain, and co-design is the process that starts it:

The critical insight is the gap between output and outcome. Projects deliver outputs. Change management delivers outcomes. Installing a system is a project deliverable; people actually using it in preference to the old way is a change management deliverable. Benefits only arrive if the outcome does, which is precisely why organisations that fund only the project half routinely fail to realise the business case.

Who is accountable

This is a favourite exam point. The change manager is rarely ultimately accountable for the benefits — that accountability lies with business leadership. The change manager works with business leaders to help realise the benefits.

That does not make benefits someone else's problem. A good understanding of the intended benefits gives the change manager four practical advantages:

• It helps structure the change approach, because you know what the change is ultimately for and can prioritise accordingly
• It allows better cooperation with business leaders, who care about benefits and often care very little about change methodology
• It supports cooperation with project or programme leaders, whose outputs you depend on
• It helps gain the buy-in of all stakeholders, because "here is what this is for" is a far stronger message than "here is what we are installing"

Working with dis-benefits honestly

Most change communication fails at the dis-benefit. Change teams announce benefits enthusiastically and stay silent about the group whose job gets smaller, whose team gets split, or whose specialist skill becomes redundant. Those people know anyway, and the silence tells them their loss is not acknowledged.

The practical discipline is to identify dis-benefits by stakeholder group during impact assessment, state them plainly in communication, and pair each with what is being done about it. This is not weakness — it is the foundation of the credibility you will need when you ask the same people to change how they work. It also connects directly to the change curve, where refusing to minimise the losses people experience is explicit guidance.

Benefits and the change manager's daily work

In practice, benefits thinking shows up in three routine decisions. When prioritising, you ask which change activities most directly protect the benefit. When negotiating scope with a project manager, you ask which output the benefit actually depends on. And when a sponsor asks why the change budget cannot be cut, you answer in benefits language rather than activity language — "cutting the change budget puts £2m of the £3m benefit case at risk" lands where "we would have to reduce our engagement plan" does not.