The hardest part of leading through change is not the change itself. It is maintaining team functioning when the ground is shifting — keeping people oriented and effective when the destination keeps moving.
I've led organizations through platform migrations, team restructures, strategic pivots, and leadership transitions at companies including AMC, EnergySage, Spark Networks, and EverQuote. The failure pattern is almost always the same: leaders communicate the what and the why, and skip the 'what this means for you specifically.'
Change that requires an agile transformation is particularly prone to leadership failure: the organization says it wants agile behavior but rewards waterfall behavior, and the teams respond to the actual incentives rather than the stated ones.
When I joined Spark Networks as interim CGO, the company was in the middle of multiple simultaneous changes: platform consolidation, go-to-market restructuring, and a cost reduction initiative. Each of those changes had been announced with clear business rationale. What they lacked was specificity about impact at the individual level. Engineers didn't know whether their product was being sunset. Marketing managers didn't know whether their team was being absorbed or eliminated. The ambiguity was generating more disruption than the changes themselves.
The intervention wasn't to slow down the changes. It was to get more specific faster. For each workstream, we identified who was affected, what was changing for them, what they should stop doing, and what success looked like in 90 days. That specificity - uncomfortable to produce because it required making decisions that leadership had been deferring - is what reduces the anxiety that derails execution.
The leaders who navigate change best have invested early in building trust with their leadership team — because trust is the only thing that survives the disruption of a significant organizational change.
The Three Things Leaders Get Wrong
1. Communicating change as an announcement rather than a conversation
A change announcement tells people what is happening. A change conversation tells people what is happening, what it means for them specifically, what they should do differently starting Monday, and what questions they're expected to have. Most leaders stop at the announcement. The questions that follow - in hallways, in Slack, in 1:1s - are the signal that the announcement was incomplete.
At AMC, during a major membership platform migration, a vendor ran a requirements session with 15 people in the room - business leads, technical leads, and senior executives. The meeting became unproductive because the HIPPO effect (highest paid person's opinion) redirected a business conversation into a technical one. Two weeks of alignment work unraveled in 90 minutes. The fix was to separate the audiences: business requirements with business leads only, technical requirements with technical leads only, and executive alignment separately. Same information, different room composition, completely different outcome.
2. Misreading resistance
Resistance to change is information. It's not always correct information, but it's always worth understanding before dismissing. The leaders who handle resistance well treat it as a diagnostic signal: what does this resistance tell me about gaps in my communication, concerns I haven't addressed, or legitimate operational issues I haven't considered?
At Capsule, a high-growth AI startup, I was coaching a Head of Product navigating a conflict between two executives who had fundamentally different views on how fast to move and how much complexity to accept. The engineering team was showing resistance to the roadmap - not because they didn't want to execute, but because the conflicting signals from leadership made it impossible to know what 'done' looked like. The resistance wasn't to the work. It was to the ambiguity. Recognizing that distinction is what allowed us to address the actual problem.
Resistance to change is information. The question isn't how to overcome it - it's what it's telling you about gaps in your communication, your planning, or your read of the organization.
3. Declaring victory too early
Change isn't complete when the announcement is made, when the new system goes live, or when the reorg is implemented. Change is complete when the new behavior is the default behavior - when people don't have to think about doing it the new way. That transition takes longer than most leaders plan for, and it requires active maintenance: reinforcing the new behavior, catching and correcting backsliding, and keeping the 'why' visible long after the initial communication.
The warning signs I watch for: people reverting to old workflows under pressure, the new process being treated as optional in meetings, and metrics that looked good for two weeks starting to drift. These are signals that the change stuck at the announcement layer but not at the behavior layer.
What Effective Change Communication Actually Looks Like
The communication principle I use: be more specific than feels comfortable about who is affected and how. Not 'this will require some adjustments to how we work' but 'the marketing team will stop running separate email campaigns by March 1, and the growth team will take over all campaign execution starting that date.'
That level of specificity is uncomfortable to produce because it requires decisions to be made before leaders feel ready to make them. But the cost of that discomfort is much lower than the cost of a team operating on speculation for three weeks. Specificity is kindness during change.
Specificity is kindness during change. Vague change communications aren't protecting people from difficult news - they're creating an environment where the speculation is usually worse than the reality.
The Skills That Matter Most in Change Leadership
| Competency | Importance Level | Key Behaviors | Development Strategy |
|---|---|---|---|
| Adaptive Thinking | High | Flexibility, Problem-solving, Learning Agility | Scenario planning, Agile methodologies, Mentorship |
| Stakeholder Engagement | High | Communication, Empathy, Collaboration | Active listening training, Stakeholder analysis, Relationship building workshops |
| Resilience | High | Emotional Intelligence, Stress Management, Optimism | Mindfulness practices, Coaching, Team-building activities |
| Decision-Making | High | Data analysis, Critical Thinking, Risk Assessment | Decision-making frameworks, Data literacy training, Case studies |
| Systems Thinking | High | Strategic Planning, Big-picture perspective, Interdependency awareness | Systems thinking workshops, Cross-functional collaboration, Organizational modeling |
Handling Resistance: A Practical Framework
| Type of Resistance | Common Indicators | Root Causes | Leadership Response Strategy |
|---|---|---|---|
| Emotional | Anxiety, fear, grief, rumors, low morale | Uncertainty about the future, perceived loss of control, lack of trust | Empathetic communication, open forums for discussion, addressing concerns directly, providing emotional support |
| Logical | Critical questions, data analysis, alternative proposals, skepticism | Concerns about practicality, efficiency, or effectiveness of the change | Data-driven justifications, pilot programs, involving resisters in solution finding, demonstrating positive impacts |
| Socio-Political | Formation of coalitions, lobbying, power struggles, hidden agendas | Threats to established power structures, perceived inequities, competing interests | Collaborative decision-making, stakeholder engagement, negotiation and compromise, building consensus and buy-in |
Building Real Buy-In vs Surface Compliance
There's a difference between people who say they're on board and people who are actually on board. Surface compliance looks like buy-in in meetings and breaks down in execution. You get it when people don't feel heard during the change process - when they've been told what's happening rather than invited into the conversation about how it happens.
The approach I use to build genuine buy-in: identify the five or six people whose active support makes execution possible (not just management approval), and invest disproportionate time in understanding their specific concerns before the change is announced. This is different from consensus-building - you're not asking for permission. You're making sure the people who will carry the change know their concerns have been considered, even if the decision is already made.
Measuring Whether Change Is Actually Working
The metrics that tell you a change is succeeding are behavioral, not transactional. Not 'did we communicate the change' but 'are people using the new system without being prompted.' Not 'did the reorg happen' but 'are the new reporting relationships producing better decisions.'
Behavioral metrics are harder to track than process metrics, which is why most change management scorecards measure the wrong things. A project that shipped on time and under budget but left the organization operating the same way it did before is not a successful change initiative. It's a completed project with no lasting impact.
Measure behavior, not announcements. The question isn't whether you communicated the change. It's whether the organization is doing something different three months later.
Leading Your Organization Through a Transition?
Change management is one of the highest-leverage moments for leadership intervention. I work with executives and product leaders who are navigating organizational transitions - platform migrations, team restructures, strategic pivots - and need a sharp outside perspective on what's working and what's likely to break. If that's where you are, let's talk.
