Stakeholder communication
Explain the same truth to an exec, an engineer and a frontline user, and get a decision.
Roadmap: Discovery & consulting core, Client simulation & ownership
Why it matters
Every deployment runs on three systems: the technical one, the business one and the human one. A correct solution that no one owns politically never gets adopted. FDEs spend as much time aligning people as writing code, and interview loops include role-plays built to test exactly this.
What it's made of
- Mapping stakeholders by power and interest
- Answer-first writing (lead with the conclusion)
- Structuring problems without gaps or overlaps (MECE)
- Translating one fact for four audiences
- Pushing back without being passive or combative
- Recording who owns each decision and each accepted risk
Lead with the answer
Executives read the first two sentences. Put your recommendation there, then the reasons, then the details. "We should pilot with the claims team first. They have the most volume and the cleanest data, and they've asked for it." Everything after that is support.
The trade-off sentence
When you make a call, say it in four parts so nobody has to guess:
- This choice: "We'll sync nightly instead of in real time."
- This benefit: "It ships in two weeks and is far simpler to run."
- This trade-off: "Data in the assistant can be up to a day old."
- This validation: "We'll check with the pilot group whether that matters before investing in real-time."
One fact, four audiences
"Manual entry drops 70%" means different things to different people. To the CFO it's hours and cost saved. To the team lead it's fewer errors to fix. To the engineer it's which fields are auto-filled and how. To the frontline user it's "you stop retyping the order number." Practise saying it all four ways.
Pushing back well
When an executive wants a company-wide launch in two weeks, don't just say no. Acknowledge the goal, name the risk in their terms, and offer a smaller, faster path: "Two weeks is doable for one team, and that gets us real numbers to justify the full rollout. Going company-wide now risks a public failure that sets adoption back months."
Mid-level looks like
Explains technical choices clearly to both technical and business audiences, and keeps people updated.
Senior looks like
Builds alignment while leaving the decision with its rightful owner, frames recommendations around the executive's own costs, and defuses escalations calmly.
Common pitfalls
- Presenting a ranked list of 12 opportunities when the sponsor cares about 2.
- Agreeing to an aggressive deadline on the spot to avoid conflict.
- Using jargon with executives, or vagueness with engineers.
- Overpromising, which is the fastest way to lose trust you can't rebuild.
Practice drills
Drill 1
Rewrite "This integration cuts manual data entry by 70%" for a CFO, a team lead, an engineer and a frontline user.
A strong answer: Four versions that each speak to what that person cares about, with no jargon for business readers.
Drill 2
Role-play: an executive demands a company-wide launch in two weeks. You believe a narrow pilot is safer. Keep it under three minutes.
A strong answer: Acknowledging the goal, naming the risk in business terms, offering a concrete faster path, and leaving the decision with the exec.
Drill 3
Write a one-paragraph recommendation memo whose first sentence is the decision you want made.
A strong answer: Conclusion first, at most three supporting reasons, an explicit ask and owner.
Best resources for this skill
Repos, courses, articles and podcasts, ranked by how much they teach.
Read next
The Pyramid Principle
Barbara Minto
Teaches you to lead with the answer and group supporting points logically. It is the fastest way to make status updates, design docs and escalation emails readable by a customer's executives.
Writing for Busy Readers
Todd Rogers, Jessica Lasky-Fink
Evidence-based rules for messages people actually read: fewer words, fewer ideas, clear asks, easy formatting. Ideal for the steady stream of Slack and email updates an FDE sends to customer stakeholders.
Storytelling with Data
Cole Nussbaumer Knaflic
Shows how to turn a chart into an argument by removing clutter and directing attention. Use it when presenting pilot results, eval scores or ROI numbers to people who will decide whether to expand the deployment.
Made to Stick
Chip Heath, Dan Heath
Explains why some ideas are remembered and repeated while others vanish. Helpful when you need a customer champion to retell your technical proposal accurately to their leadership without you in the room.