The discipline of moving people from current ways of working to new ones, so that the change an organisation paid for actually happens. Routinely budgeted last and cut first.
Systems go live on schedule far more often than behaviour changes on schedule. Change management is the work that closes that gap, and the line item most likely to be trimmed to make a business case fit.
Last reviewed 3 July 2026 · Free and ungated
Operators who have carried comparable changes through to adoption can pressure-test whether your plan survives contact with real teams.
Review this before committingChange management is the structured work of preparing, supporting and equipping people to adopt new processes, systems or structures: understanding who is affected and how, building genuine sponsorship, redesigning roles and incentives, and sustaining the change past the initial push. Frameworks such as ADKAR and Kotter's model formalise the sequence, but the substance is behavioural, not procedural.
Most transformation business cases assume adoption. The benefits column, faster processes, fewer errors, consolidated systems, depends entirely on people working differently, yet the cost of making that happen is usually a token percentage, negotiated down whenever the case needs to look leaner. This is where approved programmes fail: the system is live, the vendor is paid, the go-live announcement has gone out, and eighteen months later the old spreadsheets are still running underneath. Nothing dramatic went wrong. The benefits simply never arrived.
Change management reduced to a communications plan, as if awareness were adoption. The workstream starting after design is finished, when the decisions that determine resistance have already been taken. And success measured by training completion rates, a metric that tracks attendance, not whether anyone works differently on a Tuesday afternoon under deadline pressure.