Why Organisational Change Sometimes Fails

Organisational change is often presented as a plan: introduce a new system, restructure a department, merge teams or adopt a different way of serving customers. In practice, change is less like installing a machine and more like redirecting a moving vehicle. People must understand the destination, trust the driver, learn new routines and believe that the journey is worth the disruption.

When change fails, the visible problem is usually the final outcome: a project is delayed, a digital platform is poorly adopted, talented employees leave or an old way of working quietly returns. The deeper causes often appeared much earlier. Leaders may have underestimated the human impact, failed to involve the right people or treated communication as an announcement rather than an ongoing process.

What does organisational change failure look like?

Change does not always fail dramatically. Sometimes a programme is formally completed but produces little practical improvement. A new customer relationship system may be launched, for example, but staff continue using spreadsheets because the system is slow, confusing or disconnected from their daily work.

Common signs of failed or weakening change include:

• Employees comply publicly but continue old practices privately.
• Managers give inconsistent instructions about priorities.
• Targets are changed without providing the skills, tools or authority needed to meet them.
• Project milestones are celebrated even though customer or operational results remain unchanged.
• Employees become cynical about new initiatives and refer to them as temporary management fashions.
• Informal leaders resist the change or influence colleagues against it.
• After initial enthusiasm, performance returns to the previous pattern.

These signs matter because implementation is not the same as adoption. Implementation means that a new process, structure or technology has been introduced. Adoption means that people use it consistently and that it improves the organisation’s results.

1. The purpose is unclear or unconvincing

People are more likely to support difficult change when they understand the problem it is intended to solve. A statement such as “we need to modernise” is too vague to guide decisions. Employees need to know what is changing, why it matters, what success will look like and what may happen if the organisation does nothing.

A convincing case for change connects the organisation’s circumstances to the everyday experience of employees, customers or other stakeholders. For instance, a Kenyan retail business introducing inventory software might explain that the aim is not simply to digitise records. The purpose may be to reduce stock-outs, improve ordering decisions and give branch teams more reliable information.

Leaders should also acknowledge the costs. If a change requires additional learning, temporary disruption or changes in authority, pretending otherwise damages credibility. A realistic explanation is usually more persuasive than excessive optimism.

How to improve the case for change

1. Describe the current problem using clear, relevant evidence.
2. Explain who is affected and how.
3. Set out the intended benefits in operational terms.
4. Identify the main risks and constraints honestly.
5. Show what will remain stable, not only what will change.

2. Leaders announce change but do not model it

Senior leaders can approve a strategy without creating the conditions needed for it to succeed. Employees observe behaviour more closely than slogans. If leaders ask teams to collaborate but reward individual competition, or promote customer focus while measuring only internal speed, the organisation receives conflicting messages.

Leadership modelling includes visible decisions, resource allocation and personal conduct. A director who expects staff to use a new reporting platform should use it consistently, attend the relevant training and ask informed questions about its limitations. A manager who wants open feedback must respond to difficult feedback without punishing the person who raised it.

Middle managers are particularly important. They translate broad decisions into work schedules, performance conversations and practical choices. If they receive information late, lack authority or disagree with the direction, they may unintentionally block progress. Treating middle managers as messengers only is a common mistake; they are also implementers, interpreters and sources of operational intelligence.

3. Communication is treated as a single event

An email, town-hall meeting or launch presentation can announce change, but it cannot complete the communication process. People need repeated opportunities to understand the change, ask questions, express concerns and see how the plan is evolving.

Communication fails when it is one-way, overly technical or disconnected from employees’ actual responsibilities. Staff in finance, sales, production and customer service may experience the same change differently. A useful communication plan therefore combines a consistent central message with local explanation.

Good change communication answers practical questions:

• Why is the organisation changing now?
• What specifically will change in my work?
• When will the change happen?
• What support and training will be available?
• How will performance be assessed during the transition?
• Where can I report problems or suggest improvements?
• What decisions have not yet been made?

Leaders should also distinguish between information and influence. Sharing facts is necessary, but people may still resist if they feel ignored, threatened or unconvinced. Listening is therefore not a public-relations exercise. It is a way to identify genuine implementation risks and improve the plan.

4. The organisation underestimates resistance

Resistance is often described as stubbornness, but it can have several causes. Employees may fear job loss, reduced status, loss of competence, heavier workloads or failure in front of colleagues. They may also have experienced previous initiatives that were poorly executed. In that situation, scepticism may reflect organisational memory rather than unwillingness to improve.

Resistance can be useful when it reveals a weakness in the proposed change. A frontline employee may know that a new process adds unnecessary approval steps, while a customer-service agent may identify a risk that was missed during design. Leaders should separate valid concerns from behaviour that deliberately undermines agreed responsibilities.

A constructive response to resistance

1. Listen for the specific concern instead of labelling the person.
2. Check whether the concern is supported by facts or reflects an unresolved fear.
3. Explain which elements can be adjusted and which cannot.
4. Provide training, coaching or practical support where capability is the issue.
5. Set clear expectations when resistance becomes deliberate non-compliance.

Involving employees early can reduce avoidable resistance. Participation does not mean every suggestion will be accepted. It means people have a meaningful opportunity to improve the design and understand the reasoning behind final decisions.

5. The change is too large, too fast or poorly sequenced

Organisations sometimes launch several major initiatives at once: a restructuring, new technology, revised targets and a culture programme. Each may appear reasonable in isolation, but the combined burden can exceed people’s capacity to absorb change while maintaining normal operations.

Change fatigue is not simply a negative attitude. It can result from prolonged uncertainty, competing priorities and insufficient recovery time. When employees hear that everything is urgent, they cannot tell what deserves attention first.

Effective sequencing begins with dependencies. A new performance system may need clear job responsibilities before it can be used fairly. A digital platform may require reliable data, training and technical support before leaders can expect accurate reporting. Pilots and staged implementation can expose problems before the entire organisation is affected.

A practical sequence might be:

1. Define the outcome and the people affected.
2. Prepare leaders, processes and essential infrastructure.
3. Test the approach with a representative group.
4. Collect evidence and correct problems.
5. Scale the change in manageable stages.
6. Review whether the new practice is producing the intended benefit.

6. Training is provided, but capability is not built

Attendance at a training session does not prove competence. People may understand a demonstration but struggle when they must apply the skill under real working conditions. A one-off workshop is especially weak when the change involves judgement, collaboration or new habits rather than simple procedures.

Capability building should include practice, feedback and access to help. A new system might require short demonstrations, guided exercises, job aids, peer support and a clear route for reporting technical issues. Managers should allow time for learning rather than expecting employees to master new work after hours while maintaining full output.

Training should also be role-specific. Senior managers may need to interpret new dashboards, supervisors may need to coach staff, and frontline employees may need to complete new transactions. Giving everyone identical training can leave important gaps.

7. Measures and rewards contradict the change

Employees pay attention to what the organisation measures and rewards. If leaders promote teamwork but bonuses depend entirely on individual results, collaboration may remain a slogan. If a company asks staff to spend more time helping customers but evaluates them mainly by the number of calls completed, the measurement system will shape behaviour in the opposite direction.

Before launching change, leaders should review targets, reporting routines, budgets and recognition systems. Ask whether these mechanisms reinforce the desired behaviour. If not, employees may be responding rationally to the system they have been given.

Measures should cover both progress and outcomes. Early indicators might include training completion, use of a new process or resolution of implementation issues. Later indicators should examine quality, customer experience, productivity, financial performance or another relevant result. Counting activity alone can create a false sense of success.

8. The organisation does not sustain the new way of working

Initial adoption can disappear when attention moves to another priority. This happens when the new practice depends on a small project team, a charismatic sponsor or temporary incentives. Sustainable change becomes part of ordinary management.

To reinforce it, organisations can update procedures, role descriptions, induction materials, meeting agendas and performance conversations. Managers should discuss the change during regular reviews, not only at special project meetings. New employees need to learn the expected way of working from the beginning.

Leaders should also make room for refinement. Sustaining change does not mean preserving every original detail. It means protecting the intended outcome while improving the method in response to evidence. A feedback loop helps distinguish necessary adjustment from a return to the old system.

Technical change and adaptive change

One reason change programmes fail is that leaders treat an adaptive challenge as a technical problem. A technical problem can often be addressed through expertise, a defined procedure or a new tool. An adaptive challenge requires people to alter assumptions, relationships, responsibilities or habits.

Replacing outdated accounting software may be mainly technical, although adoption still has a human element. Moving from a command-and-control culture to greater delegation is adaptive because managers and employees must renegotiate authority and accountability. Buying software will not solve a trust problem, and issuing a new policy will not automatically change behaviour.

When a change is adaptive, leaders need to create space for dialogue, experimentation and learning. They must be prepared for disagreement because old interests and identities may be affected. This does not mean avoiding decisions; it means recognising that instruction alone cannot produce the required adjustment.

Applying This in Practice

Before starting or restarting a change initiative, use the following review:

1. Clarify the outcome: What problem are we solving, and how will we know that it has improved?
2. Map the stakeholders: Who gains, who loses influence, who performs the new work and who can accelerate or obstruct adoption?
3. Check readiness: Do people have the time, skills, information, tools and authority required?
4. Test the message: Can an employee explain why the change matters and what it means for their role?
5. Identify contradictions: Do targets, budgets, structures and rewards support the new behaviour?
6. Plan the transition: What will happen first, what depends on it and how will normal operations be protected?
7. Create feedback channels: How will concerns, failures and improvement ideas reach decision-makers?
8. Define reinforcement: Which routines, measures and leadership behaviours will keep the change in place?

For a small organisation, this review might be completed in a focused planning session with staff and managers. For a larger organisation, it may require stakeholder interviews, pilot groups and formal governance. The principle is the same: do not confuse approval of a plan with readiness to implement it.

Conclusion

Organisational change fails when leaders focus on the visible intervention and neglect the system around it. A new structure, policy or technology can be necessary, but it will not succeed without a credible purpose, consistent leadership, practical capability, aligned measures and sustained attention.

The most effective change leaders treat implementation as a learning process. They communicate repeatedly, listen without surrendering direction, use resistance as information, sequence work realistically and adjust the plan when evidence demands it. Change then becomes more than a launch event: it becomes a managed transition from one way of working to another that people can understand, practise and sustain.