The Stakeholder Juggling Act
You have five stakeholders. Marketing wants the feature yesterday. Engineering says it needs three more sprints. The VP wants a status update every week. The product owner keeps changing requirements. And the customer success team is promising things to clients that don't exist yet.
Each stakeholder has legitimate priorities. The problem isn't that they disagree — it's that they disagree privately, and you're the one who has to reconcile their conflicting expectations through email without any of them losing face.
Stakeholder management isn't politics. It's structured communication that ensures everyone has the same information, understands the trade-offs, and knows what's been decided — even when they don't love the decision.
The 'Alignment' Email (Multiple Stakeholders)
Subject: [Project] — alignment needed on [specific trade-off]
Hi all, We have a trade-off to resolve on [project]: [Option A]: [What it delivers + what it costs — timeline, resources, what we sacrifice] [Option B]: [What it delivers + what it costs] Current recommendation: [Option X] because [one-sentence rationale]. This affects [who it impacts and how]. I need alignment from this group by [date] so we can move forward. If I don't hear objections by then, I'll proceed with the recommendation. Reply-all with your input, or flag if you need a meeting to discuss. [Your name]
The power move here: 'If I don't hear objections, I'll proceed.' This prevents the common stakeholder trap where no one explicitly agrees but no one explicitly disagrees, and the project stalls in limbo. Silence becomes consent, which creates momentum.
The 'Stakeholder Update' Email
Subject: [Project] update — [date]
Send weekly to all stakeholders:
PROGRESS: [What moved forward since last update] DECISIONS MADE: [What was decided and by whom — creates accountability] UPCOMING: [What's happening next and what's needed from stakeholders] RISKS: [Anything that could derail the timeline, with mitigation] OPEN QUESTIONS: [Decisions still pending — with owners and deadlines]
Consistent weekly updates prevent 90% of 'just checking in' emails and ad-hoc meetings. When stakeholders feel informed, they stop interrupting. The format should be identical every week so people can scan quickly for what changed.
Managing Conflicting Stakeholder Requests
When two stakeholders want incompatible things, don't choose between them in private. Surface the conflict transparently:
'Hi [Stakeholder A] and [Stakeholder B], I want to flag a tension: [A wants X] and [B wants Y]. Both are reasonable, but we can't do both within [constraint — time, budget, scope]. I'd recommend [your recommendation and why]. Can we align on this by [date]?'
The worst thing you can do is promise both stakeholders what they want and hope it works out. It won't. The conflict will surface eventually — and later is always worse than sooner. Transparent conflict is manageable. Hidden conflict is explosive.
If you can't resolve the conflict at your level, escalate with clarity: 'I've tried to align [A] and [B] on [topic]. We're stuck on [specific disagreement]. I need [executive] to make the call. Here are the trade-offs: [brief summary].' This isn't failure — it's appropriate escalation.
Top comments (0)