All changes, even positive ones, create a certain level of fatigue because they disrupt known routines, require new considerations or add new responsibilities. Not knowing that a change is coming, how big it will be or how long it will last magnifies the intensity of that fatigue.
Bertolt Brecht said “Because things are the way they are, things will not stay the way they are.” We need to accept that change is inevitable – that change itself is in fact unchanging. It’s an essential part of the life of any organization. Those businesses that don’t or won’t change will die.
So what can turn a needed, positive change into something demoralizing or destructive?
Many organizations are very purpose driven with a focus on short term goals. They often restructure processes or deploy the latest technology in the hope of making measurable improvements to the operation. Plans are created, put into motion and mechanically managed in terms of objectives being met and schedules being kept. Beyond providing “training” little consideration is given to the impact a change has on those who need to adapt to it. Very few project plans include a section devoted to a Change Management strategy that limits the amount of Change Fatigue felt by those who are affected. Why? Read more
One of the biggest reasons is that the need to purposely manage change isn’t understood or accepted. The classic focus on implementation, evaluation and adjustment is limited to the processes that are being impacted and the technology (new or improved) that is being introduced.
And it’s not just the deployment of technology that creates problems. Organizational re-structuring creates a tremendous amount of stress in the environment. All too often the re-structuring is driven by issues (existing, new or imagined) before other options to address a problem can be explored. So now you have a new team addressing an issue that involves processes with which they are not fully acquainted. The team that is gelled and understands the operation is dismembered. Team members are re-assigned, leaders are swapped out or the mission is redefined.
Some organizations – and parts of organizations within an organization – are better at re-organizing then they are at solving problems. The result is the illusion of something being achieved – of progress being made toward an ever-redefined objective – when there is no progress at all. The problem still exits along with the stress it creates. This stress is compounded by confusion which leads to anxiety which results in fatigue.
Winston Churchill said: “There is nothing wrong with change as long as it is in the right direction.” This statement provides a subtle instruction for successfully managing change.
The purpose for a change needs to be completely driven by the vision of where you’re taking your organization. The vision of what will exist after the change is made.
Once the vision has been painted, leaders need to present the vision in a way that addresses their staff’s basic, selfish concern which is: “What is my new world going to look like?”
When people don’t have this answer, stress starts with the accompanying worry that begins to create change fatigue. (Think of the never-ending saga that is COVID). Those who champion the change shouldn’t try to “sell” or provide assurance that everything will better. Paint an honest picture of what is to come with as much detail as possible. Be careful to keep it direct and simple. Many words will create different understandings about what will occur.
Communication is the key to successfully managing change and avoiding change fatigue. Explain the conceptbehind the change first. If a person doesn’t understand the concept no amount of conversation or training or advertising or PowerPoint presentations will help. And the idea that “Everyone will see how much better things are if they just accept it” isn’t true. This goes for internal changes and changes that affect external clients or customers.
A large part of communication always revolves around the questions that will be asked. So be prepared for questions on a wide variety of related topics. Welcome these questions because they provide a wonderful opportunity to maintain a dialogue and build consensus about the vision. Don’t rely solely on FAQ sheets. Many people use FAQ sheets to “check a box.” They compile the questions, arrange them by topics and provide as much of an explanation as possible in three to five lines. Remember, nothing beats face to face dialogue.
Face to face does not necessarily mean one on one. The use of small lunch and learn meetings or larger town hall style groups can be very effective. Provide an opening statement and then open it up to a question and answer session. Invite suggestions about what can be done better. Listening to these recommendations creates a sense of ownership (especially if you can implement some of the suggestions). And go for ownership not “buy in.” When people “buy in” it is often situational with no commitment implied. When people have a sense of ownership they have a greater desire to see the change succeed.
Be direct with your answers even if you say “I don’t know.” Use these meetings to build their trust in you and acceptance of the change by being candid. People can sniff out duplicity. Don’t assume they’ve accepted your answers even if they don’t challenge you on them. Your people are smart and they will know when things don’t add up.
Just like “success doesn’t happen it’s planned” so is “change doesn’t just happen, it’s managed.” A project plan for introducing a new technology is focused on, well, implementing that technology from testing through “go live” with training for the end users typically included. Put it into place, show them how to use it, declare victory and walk away. That doesn’t always work out. A change management plan that parallels the project plan needs to be implemented too. It lays the groundwork for acceptance and enhances the chance of success. It should address concerns and provide feedback to the technical team. Most important it should eliminate surprises by presenting information about the coming attractions in the following categories:
- What? Clearly communicate what changes are being made. Too many people in a leadership position don’t understand that knowing all of the “whats” makes it easier for people to put the change into motion. Some leaders choose not to disclose this information because of a fear that it will raise other, complicated or uncomfortable questions. Damaged trust in the project leadership can result because of this. Information given after the fact can create cynicism when other “whats” are introduced. These are often times interpreted as intentional “oh by the way” additions.
- Why? Always provide the reason why a change is being made. Not everyone will like it, agree it’s necessary or want to do it, but understanding why will help the change to take root. Speak with complete candor. Few people are good enough at using a turn of a phrase to state something out of context and not be found out. The old excuse of “that was your interpretation and not my intent” won’t hold up. Never mislead your staff. For example, intimating that a delayed start is due to an unexpected event when it was due to a planning oversight only damages your credibility. Just about anything can and will be fact checked.
- When? Everyone who will be affected, even peripherally, needs to know that the change is coming and when it will occur. Let people know of the timeline and objectives, and make sure they understand that the timing may be altered if unforeseen circumstances occur. This isn’t due to poor planning but rather the need to be adaptable and flexible. (Sometimes your project plan will need to be adjusted before the project begins). The questions and issues raised by people who are unaware of the timing – even if they accept the need for the change – will delay your project.
Think ahead. In the first post on this subject I talked about Change Resistance and how it magnifies change fatigue. Make sure you understand where resistance maybe encountered, the impact it could have and the way it could put your efforts at risk. Pre-empt these possibilities by evaluating what may be said or done and addressing that in your communications before it happens.
Demonstrate confident leadership. If people don’t feel you believe in the benefits of the change they certainly won’t. Acknowledge issues and provide the steps that will be taken to correct them.
Be open to comments. Remember that your staff has the line level view of the effectiveness of the change. They will be the first to identify issues because they’re the closest to the process. You need to rely on their feedback to truly know what’s happening. Don’t be quick to discount their comments as criticisms. Solicit their ideas and do not rely solely on the “experts.” They can tell you how things are designed to operate – in theory – and may be inclined to identify most issues as “operator error.” (This struggle between operations and technical people started long before the digital age.). The benefit of the doubt should always be first given to the line staff.
Exercise good judgement. There is no need to dogmatically stick to the original plan if it isn’t working. Be creative and adaptable when you encounter obstacles. Remember every plan is perfect until it’s put into motion because reality has a nasty habit of making a mess of the best plans. Remember the USMC motto “improvise, adapt and overcome.”
Change can be good if it has a clearly stated purpose, a defined outcome and a realistically aggressive timetable. Good leadership from planning through execution is necessary to avoid change fatigue and to position your organization to continue to access new opportunities. The real question is, do you provide the leadership necessary to guarantee success?
You can reach us at: contact@catherinemainsworth.net