Leading Digital Change: A Playbook for Mid-Level Managers

Ask a CEO why a transformation stalled and you will hear about budget, timeline or the wrong software. Ask the people actually doing the work and you will hear about their manager: did she explain why, did he show up to the first meeting, did anyone check in after week one.

Among the transformations covered in its global survey, McKinsey found that among companies whose transformation failed to engage both line managers and frontline employees, only 3% of respondents reported success. Engage line managers and the success rate climbs to 26%. Engage frontline employees too, and it reaches 28%. The gap between those numbers is not a budget line. It is a manager.

Most change management writing is aimed at the executive sponsor: the person setting strategy, funding the initiative, and standing on stage at the kickoff. Almost none of it is written for the manager one or two levels down, who does not control the budget or the timeline but controls almost everything that determines whether the change actually happens on a given team. This is that playbook.

Why the middle decides whether a change survives contact with the team

The odds are not in your favour to begin with. McKinsey's research on organizational transformations has consistently found that fewer than 30% succeed at improving performance and sustaining the gain. Digital transformations do worse: just 16% of respondents say theirs both improved performance and equipped the organization to sustain it, and another 7% saw improvement that did not last. That leaves roughly three-quarters of digital transformations failing to deliver a lasting result.

A separate McKinsey survey of more than 1,700 executives found that the average digital transformation has a 45% chance of delivering less profit than expected, and only about a one-in-ten chance of beating expectations. But companies that followed a defined set of transformation practices more than doubled their odds of exceeding expectations, roughly five times better than those that followed none. Executives choose whether to adopt those practices. Managers decide whether their team experiences them at all.

That is the honest starting point: the strategy can be right, the technology can be right, and the change can still die at the level of a single team because no one there explained why, listened to the objections, or made the new way easier than the old one. That job belongs to the manager in the room, not the executive in the deck.

You are the local sponsor, whether anyone told you or not

Executive sponsorship gets most of the attention in change research, and for good reason. Prosci's benchmarking studies have named active and visible sponsorship the number one contributor to change success in every study since 1998, and an effective sponsor can raise a change's odds of hitting its intended business benefits from 25% to 85%. But that research also finds employees have preferred senders of change messages: the person they report to, and a leader at the top. If the top leader speaks and the direct manager stays silent or simply forwards the memo, half of that channel is broken.

Whether your title says it or not, you are the sponsor your team actually experiences. The executive sponsor sets direction once, from a distance. You translate that direction into what changes for this team, this week, and you do it in person, repeatedly, which is exactly the behaviour the research says correlates with success: active, visible, direct.

Run ADKAR at team scale

You do not need an enterprise change function to use a real framework. Prosci's ADKAR Model was built after studying change patterns in more than 700 organizations, and unlike frameworks designed for enterprise programs, it operates at exactly the level a manager works at: the individual. It breaks change into five sequential outcomes a person needs to reach for a change to stick.

1. Awareness. people need to understand why the change is happening before anything else lands. Explain it in your own words, with your team's specifics, not by forwarding the company-wide announcement and hoping it translates.
2. Desire. awareness does not create willingness. Address what is actually in it for each role on your team, and be honest about what is ending, not just what is starting. Vague enthusiasm from you reads as spin.
3. Knowledge. make sure people know how to do the new thing, specifically, not generally. A single training session rarely produces working knowledge. Plan for people to ask the same question twice.
4. Ability. knowing how and being able to do it under real deadlines are different. Build in practice time and let people be visibly slow or clumsy at the new way for a few weeks without penalty.
5. Reinforcement. the block managers skip most often, because the rollout feels finished at go-live. Without deliberate reinforcement, teams drift back to the old way within weeks, and the change quietly fails after appearing to succeed.

Borrow three moves from Kotter, skip the rest

John Kotter's eight-step change model was built for enterprise-scale transformation: creating urgency across a whole organization, forming a guiding coalition of senior leaders, anchoring change in the culture. Most of that is not a manager's job to run. Three steps translate directly to a single team, though.

• Build a small coalition. you do not need a company-wide guiding coalition, you need two or three people on your team who genuinely back the change and say so out loud. Peers carry more credibility with peers than a manager's title does.
• Manufacture a short-term win. Kotter's research treats wins as "the molecules of results": they need to be recognised and communicated early, not left to accumulate on their own. Engineer something visible and clearly attributable to the new way within the first month.
• Sustain acceleration. the common failure mode is declaring victory after the first win and moving on. Kotter's model calls for pressing harder after early successes, precisely because that is when teams are most tempted to relax and slide back.

A 90-day playbook for your team

Enterprise transformations run on multi-year roadmaps. A single team does not need one. Here is how the ADKAR blocks and Kotter's three moves compress into a quarter.

1. Weeks 1 to 2: awareness and coalition. hold a real conversation, not a broadcast. Say why now, name what is ending, and take questions you cannot fully answer yet. Identify your two or three coalition members before you need them.
2. Weeks 3 to 6: desire and knowledge. address what is in it for each role specifically. Run hands-on practice rather than a single training session, and expect to repeat the same explanation more than once.
3. Weeks 7 to 9: ability and the first win. give people room to be openly bad at the new way for a while. Engineer and publicise a first visible win that is clearly tied to the change, not a coincidence.
4. Weeks 10 to 13: reinforcement. build the new behaviour into how you review work and what you recognise publicly. Watch for reversion to the old way, especially once attention has moved to the next priority.

The mistakes that quietly kill change at the team level

• Forwarding the memo instead of explaining it. this breaks the one channel research shows employees actually trust: hearing it, in person, from the manager they report to.
• Declaring victory after the first win. exactly the failure mode Kotter's model warns against. One good week is a start, not proof the change has stuck.
• Skipping reinforcement because the rollout felt done. the ADKAR block managers drop most often, and the reason changes that looked successful at go-live quietly revert weeks later.
• Letting the loudest skeptic go unaddressed. ignoring resistance does not remove it, it drives it underground. A direct conversation, or a role in the coalition, usually beats silence.

None of this requires a seat on the transformation steering committee or a formal change management function. It requires the manager between the strategy and the team to do the job the data says usually gets skipped: explain why, show up in person, build a small coalition, manufacture a first win, and keep it alive after go-live. That is a meaningful share of the gap between the 3% and the 28%.

If you are leading a team through change and want a second set of eyes on the plan, that is exactly the kind of work we do at Gaveau Strategy.