Navigating Stakeholders and Change Management
How to win internal champions, disarm skeptics, handle the four types of resistance, and communicate AI limitations without derailing the engagement.
The People Problem
Technical AI problems are solvable with enough time and the right stack. People problems can end an engagement that is technically succeeding. An FDAE who builds an excellent system but loses the trust of the daily users, or fails to keep the executive sponsor informed, or underestimates the anxiety of people whose job the AI will change - that FDAE leaves behind a system that will not be maintained and a customer who will not renew.
Stakeholder management is not a soft skill bolt-on to FDAE work. It is the discipline that determines whether the technical work survives contact with the organization. You need to know who the players are, what each of them needs, and how to keep all of them moving in the same direction while you build.
The Cast of Characters
Every enterprise FDAE engagement has a predictable set of stakeholder types, each with distinct motivations and concerns:
| Role | What they want | What they fear | How to keep them aligned |
|---|---|---|---|
| Executive sponsor | A visible win that justifies the investment | Wasted budget, reputational risk if it fails publicly | Weekly status email: what worked, what’s next, what you need from them |
| Daily user | Less of the painful work; job preserved | Being replaced, or having their expertise devalued | Include them in every prototype review; credit their domain knowledge explicitly |
| IT / security | A system they can maintain and that does not create risk | A shadow IT project that bypasses their controls | Involve them early in discovery; treat their constraints as design inputs |
| Middle management | Their team to be productive; their own position to be safe | Their team’s headcount being reduced based on the pilot | Frame AI as amplifying their team, not replacing it; give them data on time saved |
| Internal AI skeptic | To be proven right that this will not work, or to protect the organization from a bad decision | Looking like an obstacle if the project succeeds | Invite early feedback and address technical objections specifically; convert skeptics into co-owners |
Building the Internal Champion
Every engagement needs an internal champion - a person inside the customer organization who is invested in the success of the project and will advocate for it when you are not in the room. The champion is usually not the executive sponsor (who is too far from the work) and not the daily user (who does not have enough organizational influence). The champion is typically a team lead, a director, or a senior individual contributor who has credibility with both sides.
You do not find the champion - you make them. The process:
Handling the Four Types of Resistance
Resistance to AI projects in enterprise environments usually falls into one of four categories, each requiring a different response:
Communicating Limitations Without Derailing the Engagement
AI systems have real limitations. Communicating those limitations is an ethical requirement and, paradoxically, the best way to maintain credibility with skeptical stakeholders. The mistake is either hiding limitations (which destroys trust when they surface) or over-disclosing them in ways that kill confidence in a system that would genuinely help.
The right approach: be specific and constructive. Not “sometimes it makes mistakes” - that applies to everything. Instead: “For inputs that are longer than 4,000 words, the system’s accuracy on the third section drops by about 15%. We handle that by [mitigation]. If you see that pattern, [recovery step].” Specific limitations with specific mitigations are credible. Vague disclaimers are not.
Managing Disappointment
Sometimes a prototype does not work as well as expected. Sometimes a scope change mid-engagement means the most valuable thing you could build is not the thing the sponsor announced to their team. Sometimes the timeline slips. Managing disappointment well is what separates FDAEs who get repeat engagements from those who do not.
The core principle: surface bad news early, with a specific plan. “We found that [X] is not working as expected because [specific reason]. We are [specific action] and expect [specific outcome] by [specific date].” A stakeholder who hears this on day three can adjust. A stakeholder who hears it on day thirteen, at the demo, cannot. Early honesty preserves the relationship. Late honesty burns it.
Ready to Go Deeper?
Live instructor-led courses from our partners. Affiliate disclosure.