Even with excellent stakeholder management and a compelling problem framing, you will encounter resistance. Understanding why people resist is the first step to addressing it effectively.
The Four Root Causes of Resistance
1. Rational disagreement.
The person genuinely believes your approach is technically wrong or that the trade-offs are unfavorable. This is the healthiest form of resistance. Engage it directly with data, prototypes, and honest trade-off analysis. Sometimes they are right, and incorporating their feedback makes your solution better.
2. Loss of autonomy.
Engineers and architects often resist platform mandates because they feel their professional judgment is being overridden. The remedy is co-design: involve them in shaping the solution before it is finalized. People rarely resist something they helped build.
3. Capacity constraints.
"We agree this is a good idea, but we have no bandwidth right now." This is often genuine, not an excuse. The remedy is to reduce the cost of adoption — better documentation, migration scripts, dedicated support during the transition, or a phased timeline that fits their roadmap.
4. Political or territorial concerns.
Sometimes resistance is about power, not technology. A team that currently owns a critical piece of infrastructure may resist your platform because it reduces their organizational importance. This is the hardest resistance to address directly. The most effective approach is to reframe their role — from "owners of the old thing" to "experts and contributors to the new thing."
When to Escalate
Influence should be your primary tool, but there are situations where escalation is appropriate:
- A team's resistance is creating a security or compliance risk for the entire organization.
- You have exhausted good-faith engagement and the blocker is purely political.
- The timeline is externally constrained (a regulatory deadline, for example).
When you escalate, do it transparently. Tell the team you are escalating and why. Surprise escalations destroy trust and make future influence much harder. Frame the escalation to leadership not as "this team is being difficult" but as "we have a genuine disagreement about priorities that needs a decision at a higher level."