Leaders, Treat Resistance to Change as Valuable Data

Carucci — Leaders, Treat Resistance to Change as Valuable Data

TL;DR

A practitioner HBR.org Digital article (20 April 2026) by Ron Carucci (cofounder and managing partner at Navalent; author of To Be Honest: Lead with the Power of Trust, Justice and Purpose, Kogan Page 2021). Carucci argues that the question “how do you tell legitimate concerns from kneejerk resistance?” is the wrong question — the framing assumes some resistance is invalid, which licences leaders to dismiss what they’re seeing.

Central reframing: all resistance is meaningful data. The leader’s job isn’t to determine whether pushback is valid; it’s to diagnose what it’s signalling.

The piece is opinion / consulting wisdom, not empirical research. No data points, no studies. Useful as a practitioner framework for interpreting human reactions during AI- or other transformation-driven change — adjacent to but distinct from the enterprise-ai-adoption frameworks that prescribe what to deploy.

Three traps when leaders misread resistance

When a team member questions a decision, drags their feet, or shows visible frustration, leaders feel challenged, undermined, slowed down. Under delivery pressure they default to interpretation instead of diagnosis. Three predictable traps:

1. Personalizing the pushback. Resistance gets read as a reaction to the leader, not to the change. Curiosity gets misread as disrespect.
2. Moralizing the pushback. Resistance becomes a question of attitude or loyalty (“Are you a team player?”). This shuts down the dialogue that could improve the change.
3. Rushing to resolution. Under pressure, leaders try to “solve” resistance by persuading harder or escalating authority. Speed compromises understanding.

The irony: the more leaders push to eliminate resistance, the more they amplify it or drive it underground. People stop speaking up but that doesn’t mean they’ve aligned — it means it’s no longer safe or useful to tell the leader what they really think.

Four signal categories

If resistance is data, what is it actually telling you? Carucci’s typology — most resistance falls into one of four categories, often more than one at a time:

1. Loss — “What am I losing?”

Every change involves an ending. People may be losing authority, expertise, relationships, or identity. A high-performing manager may no longer be the decision-maker; a tenured employee may no longer be the expert; a trusted process may disappear overnight. Behavioural signals: defending the old way, undermining the new approach, clinging to previous decision rights, overemphasizing risks of the new system.

Leader response:

• Name the loss directly — don’t euphemize or rush past it.
• Honor what the old way represented — pride and identity are tied up in what’s being replaced; acknowledge contribution before positioning what’s next.
• Re-anchor their value in the future — help them locate themselves in the future state.

2. Anxiety — “What does this mean for me?”

Uncertainty is one of the brain’s most powerful stress triggers. People fill in the gaps with worst-case scenarios. When anxiety is high, they don’t process information well. Leaders typically overestimate the clarity of their message: they explained it once and assume it landed. Anxious people need repetition, consistency, space.

Leader response:

• Communicate consistently, not just clearly — repeat across forums, check for understanding, assume people need to hear things multiple times.
• Normalize the uncertainty — false certainty breaks trust faster than admitting “I don’t have every answer yet.”
• Create space for questions and processing — listening is itself stabilizing.

3. Lack of control — “Why is this being done to me?”

People resist feeling powerless or excluded more than they resist change itself. Behavioural signals: passive compliance, minimal effort, retreating to old habits, lack of initiative. Carucci names a common organizational pathology: faux-inclusion — asking for input after key decisions have already been made. Employees learn their voice doesn’t matter and stop offering it.

Leader response:

• Be explicit about where people can influence the outcome — ambiguity erodes trust faster than restriction.
• Involve people early enough to shape, not just react.
• Turn participation into co-creation — give people real problems to solve within the change.

4. Flaws in the change — “This doesn’t actually work.”

Sometimes resistance is purely about execution. Employees see practical issues leaders have missed: unrealistic timelines, processes that don’t match how work actually gets done, conflicts with other initiatives. The “legitimate concern” vs “resistance” distinction is most dangerous here because it encourages leaders to filter feedback rather than listen to it.

Leader response:

• Get curious before you get corrective — treat pushback as potential insight.
• Separate the signal from the delivery — feedback may come wrapped in frustration, but tone shouldn’t disqualify content.
• Be willing to adapt the plan — the strongest change efforts evolve.

Holding the line

Once leaders have done the diagnostic work, behavioural patterns that persist shift from being a personal reaction to a leadership issue: consistent undermining, disengagement that affects others, tone that prevents the team from moving forward. Effective leaders here:

1. Name the behavior and its impact clearly, without judgment. Specific observations, not vague feedback. Grounded in facts, not assumptions.
2. Separate the person from the expectation. “You don’t have to agree with every part of this. But I do need you to engage in a way that helps the team.”
3. Follow through consistently. Don’t escalate emotion; escalate clarity. Silence sends a signal as clearly as words.

Recurring failure modes Carucci flags: leaders either crack down too early (shutting down valuable input, damaging trust) or wait too long (hoping behaviour resolves itself). Neither works. Accountability framed as care, not control: “I respect you enough to listen, and I respect this team enough to expect more.”

Cross-source positioning (descriptive only)

Carucci’s framework operates at a decision layer not previously surfaced by the wiki’s organizational-frameworks-for-ai-adoption cluster. The synthesis maps frameworks for prescribing AI deployment (org-design / readiness / capability progression / transformation playbook / trap escape / task deployment / diagnostic / firm-boundary). Carucci adds a human-reaction layer: how to interpret what people do when leaders deploy.

Direct overlaps with existing wiki sources:

• Reinforces micro-productivity-trap category #4 (“Flaws in the change”). Carucci is explicit: “the very people resisting the change are the ones closest to the risks that could derail it.” This is the same pattern Bain/OpenAI flagged (“operators see problems leaders dismiss”) and Nishar/Nohria warned about (“data architecture and process redesign as load-bearing”). Three independent sources now converge on this point.
• Complements Werner-Le-Brun’s Octopus / Tin-Man framing. Tin-Man orgs handle resistance via the three traps (personalize / moralize / rush). Octopus orgs use Carucci’s diagnostic posture (signal interpretation; co-creation).
• Operationalizes MIT CISR’s “Synchronization” pillar. Synchronization is about creating AI-ready people, roles, and teams; Carucci provides the conversational mechanics of how to engage people during that process.
• Adjacent to Reitz & Higgins on leadership attention modes. Both pieces target leader behavior under pressure. Reitz/Higgins focus on the leader’s internal mode (doing-mode vs spacious-mode); Carucci focuses on the interpretive frame leaders apply to others.

Source-quality flag

This is practitioner opinion writing, not empirical research. Carucci has decades of consulting experience but the article cites no studies, no data, no surveys. The four-category typology and the holding-the-line steps are useful working frameworks but should be marked as single-source heuristics, not validated taxonomies. Confidence boost from this source is +0.05 per the §Lifecycle “additional supporting source” rule, with no peer-review or empirical-study bonus. Resistance-categories framework deferred from concept-page promotion until a 2nd corroborating source arrives.

Linked entities and concepts

Entities (this wiki): Ron Carucci (new), Harvard Business Review (publisher; bumps source_count). Dangling (single-source mention, deferred): Navalent (Carucci’s firm).

Concepts: enterprise-ai-adoption (human-reaction lens addition), micro-productivity-trap (Carucci’s category #4 reinforces the operators-see-problems-leaders-dismiss pattern). Adjacent (existing): automation-vs-augmentation, ai-employment-effects, responsible-ai — all touch the workforce-disruption side that change resistance plays into, but no direct edits.

Threads/syntheses: organizational-frameworks-for-ai-adoption — flagged in concept pages as a reaction-layer addendum to the synthesis’s deployment-layer analysis.

Source

• Raw PDF (~8 pages): article file
• Publisher: Harvard Business Review
• Section: Managing Yourself
• Date: April 20, 2026
• Author: Ron Carucci