apply-change-leadership

Apply Change Leadership

Lead your team through organizational change by acknowledging what is ending, providing genuine clarity where it exists (and honesty where it doesn't), engaging the team in what they can control, and maintaining psychological safety and momentum through the transition.

Why This Is Best Practice

Adopted by: Kotter's 8-step "Leading Change" framework is the most widely cited change management model globally, used in change programs at IBM, GE, and the US Army; Bridges's "Transitions" model is the standard framework in organizational psychology for understanding the human side of change; the Prosci ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) is used in 80% of Fortune 500 change programs and is the basis for change management certification; McKinsey's change research (2009, 3,000 executives) is the most rigorous large-scale study of what drives change success or failure Impact: McKinsey (2009) found that 70% of organizational changes fail to achieve their intended impact — and that the primary cause of failure is not strategy or planning, but human factors: insufficient communication, unmanaged resistance, lack of leadership alignment; the same research found that change success rates more than doubled when frontline managers actively communicated the change to their teams; Bridges's research (adapted across 30+ years of consulting) found that the "neutral zone" — the ambiguous in-between period when the old way is gone but the new hasn't arrived — is where most change failures occur, and that structured leader behavior during this period determines whether the change produces improvement or dysfunction Why best: Organizational change is typically designed and announced at the executive level, but experienced and navigated at the team level; the gap between the announcement and the lived experience falls entirely on the frontline manager to bridge; managers who wait for complete clarity before communicating leave their teams in information vacuums that fill with rumor; managers who pretend change is simpler than it is lose credibility the moment complexity appears; the manager's specific role in change is neither to design it nor to simply comply with it, but to translate it for the team and maintain stability and engagement during the transition

Sources: Kotter "Leading Change" (HBS Press, 1996); Bridges "Managing Transitions: Making the Most of Change" (Da Capo Press, 2009); McKinsey "The Irrational Side of Change Management" (McKinsey Quarterly, 2009); Prosci ADKAR Model (prosci.com)

Steps

1. Understand the change before communicating it

Before telling your team anything, understand it yourself:

• What exactly is changing, and what is not?
• Why is this change happening? (The real reason, not the PR version)
• What will your team specifically be affected by?
• What decisions have been made, and what is still open?
• What can you commit to, and what is genuinely uncertain?

If you don't understand the change well enough to answer these questions honestly, get clarification from your own manager before communicating downward. A manager who communicates what they don't fully understand passes along confusion wrapped in authority.

2. Acknowledge the ending before promoting the beginning

Bridges's insight: every change involves something ending before something new begins. Managers who immediately jump to selling the new state without acknowledging the loss of the old one damage trust — because the team experiences loss, and a manager who is performatively enthusiastic about change while the team is grieving feels dishonest.

Name the loss explicitly and with genuine acknowledgment:

"I want to start by acknowledging that this change is disrupting something 
that was working well for us. [Name what's ending] — and I know some of 
you have invested significantly in building that. It's reasonable to feel 
[uncertain/disappointed/frustrated] about it."

This does not mean leading with pessimism. It means validating reality before pivoting to what comes next. Teams who feel their experience is acknowledged are more receptive to forward momentum than teams who feel their experience is being dismissed.

3. Communicate what you know — and name what you don't

The most trust-damaging communication pattern during change: certainty that turns out to be wrong. The second most trust-damaging: silence while the team generates its own narratives.

A useful principle: tell people what you know, when you know it, and be explicit about what remains uncertain.

"Here's what I know as of today: [specifics].
Here's what I don't know yet: [specifics about what's still being decided].
Here's when I expect to have more clarity: [date or condition].
I will update you the moment I learn anything relevant — I won't make you ask."

This positions you as a reliable, honest information source rather than someone who filters communication through political calculation. Teams navigate uncertainty better when they trust that their manager is giving them everything they actually have.

4. Create a "what we control" map

During periods of organizational change, the team's sense of agency often collapses — everything feels like it's happening to them rather than with them. A "what we control" exercise restores agency:

In a team meeting:
"Let's map this change together. On one side: what we cannot influence. 
On the other: what is within our control or influence to shape.
[List both together]
For everything in our control column — let's talk about how we want to 
handle it."

This exercise doesn't minimize the parts outside their control. It creates a legitimate sense of agency over the parts that are within scope. Teams that focus primarily on what they cannot control become demoralized; teams that identify and act on what they can control build momentum.

5. Increase the communication frequency — not the certainty

During change, the need for communication increases even when there is little new information to share. Silence is interpreted as bad news being withheld.

If you have nothing new to report: say that directly.

"I know you're waiting for news on [topic]. I don't have anything new 
since last week. As soon as I do, I'll tell you immediately. 
I'd rather check in with nothing to report than leave you wondering."

Increase the cadence of communication during change. Daily brief updates (even "no new news") are more stabilizing than weekly comprehensive updates during high-uncertainty periods.

6. Protect the team's core during the transition

During change, teams are at risk of two failure modes: (1) everyone focuses on the change instead of the core work, and productivity collapses; (2) everyone ignores the change and proceeds as before, producing misalignment when the new state arrives.

The manager's role is to protect core work while integrating necessary change:

• Be explicit about what priorities are stable: "Our core work [X, Y, Z] does not change. We're still responsible for delivering [outcomes] on schedule."
• Be explicit about what IS changing: "The new thing we need to build into our workflow is [specific change]."
• Protect the team from change overload: if multiple changes are hitting simultaneously, push back upward if the volume is unsustainable and advocate for sequencing.

Rules

• Acknowledge the ending before selling the beginning — teams who feel their loss is dismissed disengage from the change; validate reality first
• Name what you don't know as explicitly as what you do — false certainty that later unravels destroys trust more than honest uncertainty
• Increase communication frequency during change — silence is interpreted as concealment; regular contact even with "no new information" is more stabilizing than periodic updates
• Create agency by mapping what the team can control — demoralization comes from feeling powerless; agency comes from identifying what is within scope to influence
• Protect core work and prioritize explicitly — change without clarity on what stays the same produces paralysis; name both what's changing and what isn't

Common Mistakes

• Performative enthusiasm for a change you have mixed feelings about: teams read their manager's genuine emotional state, and inauthenticity erodes trust; it is acceptable to say "this is hard, and I think it's the right direction because [reason]" — this is more credible than pretending there are no costs.
• Waiting for complete clarity before communicating: by the time everything is fully decided, the team has generated their own narratives for weeks; communicate what you know early and update as you learn more.
• One announcement, then silence: change requires sustained communication across weeks or months, not a single announcement; the manager who sends one email and assumes the team is aligned has not led the change.
• Skipping the "what we control" exercise: teams who feel entirely at the mercy of organizational forces disengage; establishing what the team can influence restores agency.
• Underestimating the length of the neutral zone: the period between ending and new beginning is always longer than planned; expect 2–4x longer than the organization estimates, and plan accordingly.

When NOT to Use

• When the change is confidential and cannot be communicated yet — if you know something your team doesn't because of confidentiality requirements, you cannot communicate it; focus on maintaining stability and signaling that you will share information as soon as you are able.
• As a substitute for advocating for your team when the change is genuinely harmful — if the change is damaging to the team in ways that could be mitigated with organizational adjustments, use apply-upward-influence to advocate before simply implementing.