All posts
The Isthmus View

Change Management Needs Change Management

Why the current approach to change management is like riding a bike with training wheels

Andrea Barnes
Share LinkedIn Email

Our approach to change management needs to change. As the popular saying goes, the things that got us here will not get us there.

In the past, change came at a much slower and steady pace. Today, we are navigating multiple complex changes at the same time, in hyper speed.

Many of the change management playbooks we use today were built for change of the past, and the change we are living through today looks nothing like that. McKinsey recently put a number on it in Change is changing: How to meet the challenge of radical reinvention: "The average employee now experiences ten planned change programs a year, a fivefold increase from a decade ago." Ten a year. The authors also say "the pace of change is not going to slow down; in fact, it is likely to accelerate." Ten changes a year can be scheduled, tracked, and staffed, and the people still have to live through every one of them. That's where methodology runs out. It tells us what step comes next, not how to bring people along.

Many organizations struggle with how to fix this, and frankly don't know where to start. Often, the fix looks like sending your project managers, change management team, PMO, or transformation office to a certification course. If this is the solution, I'd argue that you just gave your team a set of training wheels and expect them to bike the Tour de France. To be super clear, I am not diminishing change management or the people who practice it, my career has been rooted in navigating change in organizations. The established, step-by-step change models are good and useful, and the people who are certified in them have real and valuable skills that are incredibly necessary in our organizations. The good frameworks reference behaviors, but the difference is how we use them. In most playbooks, behaviors are tactically deployed to roles for a project. The sponsor sends the message, the manager holds the coaching conversation, someone "manages resistance." We pull those behaviors out for the change at hand, deploy them like a step in the project plan, and often they get put back on the shelf when the project closes. The behaviors I'm talking about are different. They aren't something leaders do to people to get the change over the line, they're how a team works every day, whether a change is happening or not. When behaviors only show up for the project, they never get the chance to become habits. This means that when the next change comes along, the team starts from scratch, and with ten changes a year that's a lot of starting from scratch.

Back to my training wheels analogy: training wheels are a tool that hold the bike up for you so you never have to find your own balance. Balance is the whole point of riding a bike. Frameworks work the same way. They hold the process up with steps and tools to deploy during change, but they don't build the foundational behaviors that keep a change upright when the road gets bumpy. Back in the day (you know, when change only came at us one by one) training wheels used to be a given. The way you learned to ride a bike was with training wheels and everyone used them. These days a lot of kids never use training wheels because they learn on these newfangled things called balance bikes which come with no pedals and no training wheels, just feet on the ground and a lot of wobbling. The child doesn't need the tool, they need to learn balance. Once they have figured out balance, adding pedals is the easy part. Our kids' way of learning to ride has evolved, and I'd argue the way we teach people to ride out change should too. The methodology is still useful, it's just the second thing, not the first. Balance first, which is the behaviors, and then the framework on top.

Now to those behaviors I keep referencing. What actually carries a change is a handful of behaviors, and the research on them is stronger than most of us realize. I'm going to focus on five behaviors that help us ride out change like a champ and give you one simple thing you can try today to build these behaviors on your teams.

Invite

Make it safe to speak up and learn out loud. In Psychological Safety and Learning Behavior in Work Teams, Harvard's Amy Edmondson found that team psychological safety drove learning behavior, and learning behavior drove team performance. Change is a learning problem first. If people can't say "I don't understand this" or "this isn't working" out loud, you will find out in the results instead of in the room, and that's an incredibly expensive and inefficient way to figure that out.

Try this: At the end of your next change update, swap "Any questions?" for "What's one thing about this that doesn't make sense yet?" Then wait longer than feels comfortable. That pause is the invitation.

Co-create

Build the change with people, not for them. In This New Strategy Could Be Your Ticket to Change Management Success, Gartner's Jordan Turner writes that organizations that use what Gartner calls open-source change "are 14x times more likely to achieve change success," that letting employees own implementation planning raises success by 24%, and that involving them in decisions raises it by 15%. "74% of employees were willing to support organizational change in 2016; today, only 38% say the same." That is a consultancy's research, so read it as a strong signal and not a law of physics, but it matches what I see. People are tired of having change done to them.

Try this: Before the plan is final, pick three people who will actually live with the change and ask them one question: "What's going to get in the way of this working for you?" Then show them where their answer landed in the plan.

Commit and care

Hold commitment and care at the same time. In Emotional Balancing of Organizational Continuity and Radical Change: The Contribution of Middle Managers, Quy Huy followed a radical change at a large firm for three years and found that middle managers who stayed committed to the change and also attended to the emotions of the people affected helped their groups adapt. Commitment without attention to emotions produced chaos, and low commitment produced inertia. Same facts, three very different outcomes, and the only variable was how the managers showed up. This is the "name the loss" idea I keep returning to, because you can't skip the grief and still get the adoption.

Try this: Don't make people choose between understanding the change and feeling the loss. Pair the why with the grief. "Here's why we're doing this, and I know some of what we're changing mattered to you. It's okay to miss it."

Equip

Frame the change and build capacity, instead of steering everything from the center. In What Does It Take to Implement Change Successfully? A Study of the Behaviors of Successful Change Leaders, Malcolm Higgs and Deborah Rowland found that leader-centric "shaping" behaviors were negatively related to change success, while framing the change and creating capacity in others were positive. They also found more success when change was approached as complex rather than linear or step-by-step. Higgs said as much himself, in a Q&A with Social Science Space: "the essence of this finding seems to be that leader centric behaviour gets in the way of implementing change successfully." It is not the leader's job to hold the handlebars tighter. A leader's job is to make the road clear and the riders strong.

Try this: Hand someone on your team a piece of the change to own, like the rollout plan for their team or the FAQ. Give them the why and the guardrails, then let them figure out the how.

Practice

Treat change like a skill you build, not an event you get through. Nobody learns balance from a lecture on balance. We learn it by a lot of wobbling, and ideally in a space where the stakes are low. Change works the same way. If the average employee faces ten planned changes a year, the big ones can't be the first time anyone has practiced. Practice on small ones, and practice on purpose.

Try this: Once a month, ask your team "What's one small thing we could try differently for two weeks?" Pick one, try it, and talk about it at the end. Normalize change practice and when the big change lands, your team has already done the reps.

I'm not saying throw out the playbook. The frameworks stay, and so do the project plans, the communications calendars, and the governance. What changes is what we treat as the foundation. The behaviors are the foundation and the framework becomes a tool you pick up when and where it fits.

Pause and reflect

  1. 01Think of the last change you were part of. Who was asked for their input before the plan was final, and who found out after? What is one person you could ask for input on the next one?
  2. 02When someone on your team said "I don't get this" or "this isn't working" recently, what happened next? What would you do differently to make it a little safer?
  3. 03Count the changes landing on your team right now, then ask your team to name how many they're carrying, both personally and professionally. What does that number tell you about how you approach change and how you view change fatigue/resistance?

I'll leave you with this -

"The pace of change is not going to slow down; in fact, it is likely to accelerate."
Aaron De Smet, Arne Gast, Erik Mandersloot, and Richard Steele, with Carmen James, Change is changing: How to meet the challenge of radical reinvention, McKinsey

Take care of yourselves and each other, 

Andrea

At Isthmus Advisory, I start with the behaviors, because that's the part that teaches balance, and then we pick up the framework that fits the ride. If this resonates and your team could use support learning the balance piece, I'd love to connect.  

Thanks for reading!
Subscribe to receive new posts

Thanks. You'll get an email when a new post goes up.

ANYTHING RESONATE?

Let's continue the conversation

Grab a time that fits your schedule in a few clicks.

Book time on my calendar

Prefer email? Andrea.Barnes@IsthmusAdvisory.com