Project Smart ~ Exploring trends and developments in project management today

Calendar iconNot recorded
Adobe PDF icon

Change Management in Practice: Why Does Change Fail?

~ By Jonathan Palmer

White king stands next to defeated black king in a game of chess

Resistance to change may be active or passive, overt or covert, individual or organised, aggressive or timid and on occasions totally justified.

Sadly most significant change fails to meet the expectations and targets of the proposers. The failure is given the catchall name resistance, yet resistance can be principled and creative as well as from vested interest. Top management is frequently unreasonable in its expectations and time scale, forgetting the process it went through when it decided to make the change.

An effective change manager will prepare an organisation for change in the early stages of project definition and stakeholder review, by taking managers through a similar sales process and responding to their apparent resistance: the creative conflict.

This process is likely to improve the project definition and buy in. It will also ensure that it is clear the moment resistance becomes vested interest.

It is unrealistic to expect an independent change manager to tackle vested interest resistance but the change director can use his or her intervention as a signal to the organisation - such interventions should be few but telling.

An independent change manager is a cross between a foil and a lightning conductor - the foil ensuring that positive energy is deflected to the right place, the lightening conductor removing negative energy from the organisation.

Avoiding Failure: Managing Resistance

Resistance is a key element in why change fails. A recent informal UK survey of 120 government transformation programmes identified that:

  • 15% achieved their objectives
  • A further 20% failed to achieve their objectives but were nevertheless regarded as satisfactory
  • 65% were unsatisfactory

A subsequent discussion forum on ecademy.com identified seven key reasons why change fails. (The list is virtually identical to one made by Kotter at Harvard 20 years ago):

  1. The organisation had not been clear about the reasons for the change and the overall objectives. This plays into the hands of any vested interests.
  2. They had failed to move from talking to action quickly enough. This leads to mixed messages and gives resistance a better opportunity to focus.
  3. The leaders had not been prepared for the change of management style required to manage a changed business or one where change is the norm. "Change programmes" fail in that they are seen as just that: "programmers". The mentality of "now we're going to do change and then we'll get back to normal" causes the failure. Change as the cliché goes is a constant; so a one off programme, which presumably has a start and a finish, doesn't address the long-term change in management style.
  4. They had chosen a change methodology or approach that did not suit the business. Or worse still had piled methodology upon methodology, programme upon programme. One organisation had Six Sigma, balanced scorecard and IIP methodology all at the same time.
  5. The organisation had not been prepared and the internal culture had 'pushed back' against the change.
  6. The business had 'ram raided' certain functions with little regard to the overall business (i.e. they had changed one part of the process and not considered the impact up or downstream) In short they had panicked and were looking for a quick win or to declare victory too soon.
  7. They had set the strategic direction for the change and then the leaders had remained remote from the change (sometimes called 'Distance Transformation') leaving the actual change to less motivated people. Success has many parents; failure is an orphan.

Very few organisations will manage all seven! However, any one in isolation will make the change programme inconsistent and aggravate resistance. Advance planning and stakeholder management will avoid some of these pitfalls. Furthermore the list is an invaluable diagnostic tool for identifying why (and where) resistance is taking place, giving an opportunity to defuse resistance by correcting the mistake.

Conclusion

  • Resistance can be healthy (a pearl can result)
  • Unknown, unanticipated, unquantified, unaddressed resistance will always be dangerous
  • A badly thought out process and implementation will always result in resistance
  • An independent change manager can bring the independence, experience, and objectivity to manage resistance
  • A successful change is essential in creating a change culture

Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
Enter the word foot backwards.
Notify me of new comments via email.
Remember my form inputs on this computer.

Building a Business Case for Your Project

Ball of business documents

To get stakeholders or management to approve your project, you will need to build a solid business case. Here are the basic steps for creating a business case.

Managing The Project Time

Man pointing at an alarm clock

Project managers should know the iron triangle of project management, sometimes called the triple constraints of project management, because all projects are constrained by these elements.

PMP vs. PRINCE2 Certificates

Senior lecturer in front of his class

What's the difference between the PMP and PRINCE2 certifications? Which one should I choose? Which one's better for my career?

How Agile Practices Reduce Requirements Risks

Road warning sign - Risks Ahead

Every software project carries some risk, but many of these risks can be mitigated. That's true of problems related to product requirements.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Deb McCarthy commented on…
The Role of the Project Manager
- Fri 4 October 5:57am

Ed Rushman commented on…
MoSCoW Method
- Mon 30 September 5:11pm

Shawn Robert Vance commented on…
Better Coaching Using the GROW Model
- Sat 28 September 6:41pm

Latest tweets

General Project Management • Re: Building a UK Community https://t.co/v3vt0mYyE7 about 8 days ago

General Project Management • Dissertation Survey - Please help https://t.co/XwtF8pERkX about 18 days ago

MOSCOW Method https://t.co/uctlvoR733 some questions to ask the user and then the users will decide themselves if M, S or C. #projectsmart about 20 days ago