As companies grow and become successful, they build up large amounts of momentum – they hire people with particular skill sets and attitudes, they develop formal processes for sustaining a particular way of working, and they often focus on a fairly narrow set of measures of performance. But the competencies they build up over time can quickly become liabilities when there are major shifts in the business environment. In cases of mighty companies falling from grace, such as Nokia, Kodak, or Blockbuster, the story is always about executives failing to achieve the scale of change that was required. Typically, there is a good level of awareness of what is happening (for example, Kodak actually invented the digital camera and Nokia had touchscreen phones in prototype before the Apple iPhone was launched), but the challenge of fundamentally changing the structures, processes, and people in a large company is often too difficult.
The ability to manage change is, therefore, hugely important – and not just at senior executive levels. Midlevel managers have to be able to lead change programs within their areas of responsibility, and they also have to take an active role in large-scale change efforts. Most of the techniques in this book have been about working within a fairly clearly defined framework – even the techniques for creativity and innovation assumed a certain level of stability in the company as a whole. But in this chapter, we take a different approach and look at the various techniques needed to make major change happen. By major change, we mean the sort of thing that makes many people uncomfortable, that has losers and winners, and that requires real leadership to help people make sense of it.
The starting point is to understand the stakeholders of your change program – who they are and what their needs are (#91). Then we discuss the key steps needed in a change process (#92) using Kotter's well-known eight-step guide. We describe a technique for understanding the emotional reactions of people as they go through a change process (#93). We also look at the tactics for persuading and influencing people effectively (#94).
These four techniques all assume you have a reasonable level of seniority and some formal authority over the people you are trying to take with you on a change process. The final technique is different – it is for managers at lower levels who are trying to lead change when they lack formal authority (#95).
We have all seen projects fail because of people issues. Money and energy are expended to make change happen, only for key people to reject it or for end-users to avoid using new tools given to them.
This often happens because the right individuals have not been consulted or informed about what is happening or they have not “bought in” to the need for the project. This is why stakeholder management is a vital part of change projects; and the larger the project and the more people it affects, the more important it is likely to be.
Stakeholders are the people who have an interest in the success or failure of a project and an ability to affect its outcome. They can be obvious groups such as employees and managers, but they can also be less obvious such as investors, governmental organizations, trade associations, trades unions, pressure groups, or the press.
To maximize the chance of success for your change project, it is wise to start managing stakeholders from the outset. To do this, follow these steps:
Plot this analysis on a power/interest grid like in Figure 17.2. This helps make it clear where you need to focus your communication and your influencing efforts. It also shows you what approach you should use with different people.
Find out more about stakeholder analysis, including using an interactive power/interest grid tool: | http://mnd.tools/91-1 |
Learn how to manage stakeholders, including downloading a stakeholder management template: | http://mnd.tools/91-2 |
Source: Adapted from Mendelow 1981.
Once you've identified the most important stakeholders in your project, the next step is to communicate with them and “manage” them so that they support it enthusiastically. This is where John Kotter's eight-step change model can help you. Published in 1995, this model is based on lessons from more than 100 change projects. To use it, follow these steps:
Learn more about Kotter's eight-step change process: | http://mnd.tools/92 |
Source: Adapted from Kotter 1995. Reproduced with permission of Harvard Business Publishing.
Kotter's eight-step change model is great for initiating and inspiring change, but it doesn't describe the emotions that people experience if they're affected by change but are not in control of it. These emotions can be intensely negative, and they can seriously undermine or stop a change project if you're not prepared for them.
This is where it helps to know about the change curve and to understand how to help the people affected by change through its stages. Often attributed to psychiatrist Elisabeth Kübler-Ross, it draws parallels with her work on personal transitions in grief. You can see an example of it in Figure 17.3.
Many people go through a predictable pattern of emotions as they experience unexpected change. In stage 1, they react with shock to the challenge to the status quo, and they may deny that the change is happening. In stage 2, as people start to experience the impact of change, they react with fear and anger, they may actively resist the change, and the organization may experience serious disruption to its performance as a result.
If people successfully navigate stage 2, they may move to stage 3. Here, people let go and accept change, and they start exploring what it may mean to them and how they can adapt to it. Finally, in stage 4, they embrace change, and everyone reaps its benefits.
The trick with managing these stages is to anticipate them and help people adjust – this allows you to reduce the downside risks, shorten the length of time it takes to settle in, and increase your chances of success.
In stage 1, focus on providing information and answering questions without overwhelming people with details (if they're seriously upset, they may only be able to take a small amount of information in at any one time).
In stage 2, you need to be prepared to deal with anger. Anticipate objections and concerns, and do what you can to address issues honestly so that you can win people over. (We look at a useful tool for doing this next, in #94.)
In stage 3, provide plenty of training and support for people to try out new approaches and explore the opportunities that change will bring. And in stage 4, celebrate the success of the project, and make sure that everyone's contribution is fairly and properly recognized.
Learn more about using the change curve: | http://mnd.tools/93 |
It's all very well and good for us to talk about persuading people to support your change project, but this can be very hard to do, particularly if people feel threatened by it and become angry as a result.
This is where the influence model can help you. Published in 2006 by researchers Allan Cohen and David Bradford, it draws on the principle of reciprocity – i.e., fair exchange – to win people over. It's particularly useful where they don't support you, where you have a poor or nonexistent relationship with them, or where you've run out of other ways of trying to persuade them to help you. To use it, follow these steps:
Learn more about the influence model, including seeing an example of it in action: | http://mnd.tools/94 |
Source: Adapted from Cohen and Bradford 2005. Reproduced with permission of John Wiley & Sons, Inc.
It's not just people affected by change you need to persuade – sometimes you need to win over conservative senior managers who may not be prepared to fund the work needed to prove an idea. One way of doing this is to develop your idea quietly, behind the scenes, and prove success early on without getting prior approval.
This is particularly useful where ideas are radical and potentially disruptive internally, where they need more work to be fully shaped, and where they might end up being shot down by senior managers before they have a chance to prove themselves. (This is important because once an idea has been rejected by busy senior stakeholders, it can easily stay rejected, even if problems have been overcome and the idea has been significantly improved.)
This is where the notion of stealth innovation, as described by Paddy Miller and Thomas Wedell-Wedellsborg in a 2013 Harvard Business Review article, is useful. According to these researchers, to do this well, you need to:
At some point, your stealth project will need to be put forward in a formal way for senior management buy-in and funding, but if you have taken the steps above, your chances of success will be significantly greater.
Learn more about stealth innovation: | http://mnd.tools/95 |
Source: Adapted from Miller and Wedell-Wedellsborg 2013. Reproduced with permission of Harvard Business Publishing.