Change management approaches
The two approaches the exam uses
- The externals have repeatedly set this as a straight comparison between a top-down and an inclusive change management approach. Know both, and be able to argue for either.
Top-down change management
- Management decides the change, announces it, and directs staff to implement it. Authority is used openly, usually with an autocratic leadership style.
- Advantages:
- Fast. No consultation period, so the business gets to the new state sooner.
- Decisive. One clear direction, no competing versions of the plan.
- Cheap to run. No meetings, workshops or consultation time taken out of production.
- Necessary in a crisis. When the business is losing money weekly, there may not be time to consult.
- Right when the decision is not negotiable. A legal requirement or a head-office directive cannot be voted on, and pretending otherwise is worse than being direct.
- Disadvantages:
- Resistance is not removed, only suppressed, so it reappears as slow compliance or workarounds.
- Good ideas are lost. The people doing the job know things management does not, and are not asked.
- Motivation falls. Staff who are told rather than consulted feel undervalued.
- Staff turnover rises, and the people who leave first are usually the most employable.
Inclusive change management
- Staff are consulted, involved in designing the change and given a real influence over how it is implemented.
- Advantages:
- A wider range of ideas, including practical objections that would otherwise have surfaced only after implementation.
- Acceptance. People support what they helped design, so resistance falls.
- Fewer implementation errors, because the plan has been tested against how the work is really done.
- Motivation rises. Being consulted signals that the employee is valued.
- The change sticks. Staff who understand the reason keep applying it under pressure.
- Disadvantages:
- Slow. Consultation takes weeks or months, during which the problem the change addresses is still costing money.
- Expensive. Meeting time is production time.
- Expectations are raised. If staff are consulted and then overruled, trust falls further than if they had never been asked.
- It can stall. A group asked to agree may reach a weaker compromise than the change needed.
What management does either way
- Explain the reason. People accept difficult changes when they understand what the business is facing. The reason must be specific — a named competitor, a lost contract, a regulation — not "we need to modernise".
- Communicate early and repeatedly. Rumour fills any silence, and rumour is always worse than the truth.
- Train before the change, not after. Fear of not coping is a leading cause of resistance, and training removes it.
- Use the influential staff. Every workplace has people whose opinion others follow; convincing them is worth more than convincing the org chart.
- Give a timeline. Uncertainty about when is as damaging as uncertainty about what.
- Be honest about losses. Where jobs will change or go, saying so early is better than being found out later.
- Pilot it. Running the change in one site or team first surfaces the problems cheaply and provides internal evidence that it works.
- Resource it. Change on top of an unchanged workload is the most common reason change fails.