Module 1: Understanding Change

Why Change Efforts Fail

Organisations change constantly: new software, restructures, mergers, new products, new regulations, new leaders. Yet many change efforts deliver far less than promised. A new system goes live but staff keep using spreadsheets; a restructure is announced but old habits continue; a new sales process is launched and quietly abandoned. Understanding why change fails is the first step to leading change that succeeds. Most failures are not technical. They are human and organisational, and they are largely predictable.

Change management versus project management

Project management delivers the solution: the new system is configured, the new office is ready, the new structure is designed. Change management makes sure people actually adopt it and use it so that the benefits are realised. A project can finish on time and within budget and still fail to deliver value if people do not change how they work. The two disciplines must work together from the start.

Common reasons change fails

• No clear, shared reason for the change. If people do not understand why, they see the change as arbitrary and resist or ignore it.
• Weak or absent sponsorship. Leaders announce the change and then disappear. Employees watch what leaders do, not what they say.
• Underestimating the people side. Plans focus on technology and process and allocate little time or money to communication, training and support.
• Too much change at once. Multiple initiatives hit the same people simultaneously, causing overload and fatigue.
• Poor communication. Messages are vague, one-way, too late or delivered by the wrong people.
• Inadequate training and support. People are expected to work in a new way without the skills or help to do it.
• Systems and incentives that contradict the change. Old targets, reports or reward schemes keep rewarding the old behaviour.
• Declaring victory too soon. Attention moves on after go-live, and people drift back to old ways.

Worked example: a failed system rollout

Imagine a hypothetical savings and credit cooperative (SACCO) in Nyeri that introduces a new core banking system to replace manual ledgers and an old database. The board approves the budget, the vendor installs the system and the IT officer trains staff in a single one-day session the week before go-live.

Three months later, problems are everywhere. Tellers still record transactions in exercise books "just in case" and enter them into the system at the end of the day, causing errors and delays. Loan officers say the new loan module is too slow and keep approving loans on paper. Members complain about long queues. The general manager is frustrated: "We spent all this money and nothing has improved."

Looking back, the failure had clear causes:

1. Staff were never told why the old system had to go, so many saw the new one as an unnecessary burden.
2. The general manager approved the project but left everything to IT, so staff assumed it was not a real priority.
3. One day of classroom training was not enough to build confidence, and there was no support after go-live.
4. Branch performance was still measured on the number of loans issued, so loan officers kept using the faster paper process.
5. Nobody measured whether people were actually using the system correctly.

None of these were technical problems. Each could have been prevented with deliberate change management.

What successful change has in common

Successful change efforts tend to share a few features: a compelling and well-understood reason for change; visible, active leadership from start to finish; early and ongoing involvement of the people affected; enough training, coaching and support; alignment of systems, measures and rewards with the new way of working; and sustained attention after implementation. The rest of this course shows you how to build each of these.

Common mistakes to avoid

• Treating change as an announcement rather than a process that takes months.
• Assuming people will adapt because the new way is obviously better to you.
• Starting change management at go-live instead of at the start of the project.
• Blaming resistance on people's attitudes without examining what the organisation did to cause it.
• Measuring project completion instead of adoption and benefits.