Change management is the process of guiding an organisation from a current state to a desired future state while minimising the risks and disruption of the transition. The textbook distinguishes two kinds:
- Project change management — handling changes within a project’s lifecycle (scope changes, requirement updates, team shifts).
- Organisational change management — the broader transformation of how the firm operates. This is the focus.
The goals of organisational change management:
- Understand the changes and their implementation risks.
- Implement the desired change.
- Ensure transition from current to future state.
- Minimise unplanned operational disruptions.
- Achieve the desired performance improvements.
- Sustain change over the long term.
The framing that matters most: change is made by people, not systems. Implementing new software, processes, or policies is the easy part; getting people to adopt the new way is the hard part. A change project that delivers the new system but doesn’t shift behaviour has failed.
Types of change
Three categories by scope:
Transformational change. Organisation-wide, major shift in corporate vision. A new CEO introduces a strategic pivot to boost performance. Affects everyone.
Bounded change. Departmental, limited to one group. A manager restructures their team for efficiency. Affects a handful of people.
Deliverable-led change. Project-centric, focus on the deliverable rather than the change itself. Launching a new product or process. Affects whoever interacts with the deliverable.
Four outcomes of change
Four things that can happen:
-
The disaster. Irreversible change, incompatible with the wider business, devastating performance loss, possibly bankruptcy. (New Coke, 1985, though that one was reversible.)
-
The lost investment. Initial improvement, then performance declines as people revert to old ways. The change wasn’t sustained.
-
The partial success. Sustained improvement, but full potential not realised. Maybe people adopted 60% of the new way and kept 40% of the old. Common.
-
The ideal. Change implemented and sustained, full potential realised, minimal short-term disruption. Rare. Most successful change programs hit category 3 and call it a win.
Costs and benefits
Costs of change:
- Direct cost of the change team (consultants, project staff, advisers).
- Time away from the rest of the organisation (productivity diverted to change activities).
- Investments to support the change (new tools, training, infrastructure).
- Longer-term ongoing costs (maintaining the new way).
Benefits:
- Big rewards available, if the change works.
- The benefits have to be managed and measured throughout to validate the investment.
Why change?
External drivers: economic shifts, competitive pressure, new product opportunities, shareholder demands, mergers and acquisitions.
Internal drivers: new leadership, restructuring, changing technology, evolving culture.
The bigger argument: organisations have to constantly assess their position within their environment (using tools like SWOT analysis) and adapt. Not changing is itself a decision, one that often leads to slow decline.
Effective change management
Change management requires vision, persistence, and empathy. Humans resist change, and that resistance is the central management challenge. Programs that work:
- Articulate a clear vision of the future state.
- Communicate it relentlessly.
- Recognise and address concerns (psychological, practical, political).
- Persist through the inevitable difficulties.
Where failures come from:
- Lack of initiative — the change is announced but not pushed through.
- Unforeseen operational problems — the new state has problems nobody anticipated.
- Cost overruns — change is more expensive than budgeted.
- Failure to embed — the new tools/systems aren’t integrated into how work actually gets done. Common with IT-driven changes.
- Benefits fall short of true costs — the change doesn’t deliver what was promised once full cost is counted.
See also Organizational culture, Risk management.