Most stakeholder-mapping guides teach the theory — the power/interest grid, the four quadrants — and stop there. The harder part is doing it for a real, new client in your first two weeks, when you barely know who's who yet. Here's the practical version.
Start with the person who hired you — but don't stop there
Your point of contact is rarely the only stakeholder, and sometimes isn't even the most important one. In your kickoff call, ask directly: "besides you, who else should I know is watching this, or who'll need to sign off along the way?" Most clients will name two or three people without hesitation — they just weren't volunteering it until asked.
Score power and interest from what you observe, not what you assume
Titles are a weak signal. A VP who's checked out and a coordinator who's deeply invested can have inverted actual influence over whether your work gets used. Look for real signals instead:
- Power: Who can approve budget, kill the project, or override a decision? Who do other people in the room defer to?
- Interest: Who asks detailed follow-up questions? Who shows up to every call versus sends a delegate?
A worked example
Sponsor (VP Operations): High power, high interest — approved the budget, attends every check-in, asks pointed questions. → Manage closely.
Day-to-day contact (Project Manager): Lower formal power, very high interest — uses your work daily, escalates internally on your behalf. → Keep informed, but treat as a real ally, not just a conduit.
Procurement:High power (controls contract renewal), low interest (doesn't care about the work itself, only terms). → Keep satisfied — don't over-communicate, just don't let contract friction surprise you.
End users on the team:Low power, moderate interest — affected by the outcome, limited say in the decision. → Monitor, but their feedback is often the earliest signal something's off.
The map goes stale — and that's the part everyone skips
A stakeholder map built in week one is accurate in week one. By month three, the champion who pushed hardest for you might have moved teams, the quiet skeptic might have become your biggest advocate, and a new VP might have joined with zero context on why you're there. Treat the map as a living document tied to the relationship, not a one-time deliverable filed away after kickoff — revisit it at renewal points, or any time the account goes quiet in a way that doesn't match the map you built.
That last part is really a relationship-tracking problem more than a mapping problem — a map tells you who matters, but it won't tell you when one of them has gone quiet. The free BD Neglect Detectorcovers that half: paste in your contacts and last-contact dates and see who's cooling off before it costs you the relationship.