Stakeholder Map How-to: 30-Minute Version
You can “know” twenty names and still ship into a wall. A stakeholder map fixes that only if every name has a next action. Without actions, you drew a pretty org chart.
Time box: 30 minutes to draft a one-page living map and a top-five outreach list. Keep it private unless your manager asks to coach from it. This play fits week 1-4 of a new role, the start of a project, or the week after an org change. Use it with the Individual Contributor hub and New Hire hub.
When to use (and when not to)
Use when:
– You’re new and names are blurry
– You own a project with cross-functional handoffs
– Reporting lines just changed and your “usual suspects” list is stale
– Your manager asks who you’re aligning with and you shrug
Do not use when:
– You’re ranking people you haven’t met as “enemies” or blockers from gossip
– You want a power ranking to paste in Slack
– You’re coding personal traits, protected characteristics, or drama into the grid
– You’re avoiding the real work by over-engineering boxes and colors
The point is map actions, not vibes. Influence guesses are working hypotheses, not science.
Who is involved
- You alone for the draft (quiet focus).
- Optional: 10 minutes in a 1:1 for manager review (“Who’s missing?”).
- Do not crowdsource the map in a team channel.
Prep
Before the timer:
– Open any org chart or directory you can access (if none, use calendar + Slack member lists).
– Pull last two weeks of meeting invites and recurring channels.
– Write your current goals or project outcome in one sentence.
– Have a blank doc or sheet ready with the template columns below.
Template (fill in 30 minutes)
Use a simple table. A 2×2 influence/interest sketch is optional eye candy; the action column is mandatory.
| Name | Role / team | What they care about | Influence on my work (H/M/L) | Interest in my work (H/M/L) | Next micro-action | By when |
|---|---|---|---|---|---|---|
Micro-actions that count: ask manager for a warm intro; book a 15-minute listen; change who you CC; send a one-line FYI before a decision; “monitor” (intentionally no outreach this week).
If a row has no next action, delete the row or mark monitor. Orphan names are decoration.
Optional 2×2 (sketch, then act)
- High influence / high interest → partner closely
- High influence / low interest → keep informed with crisp asks
- Low influence / high interest → use as allies and early readers
- Low influence / low interest → monitor lightly
Don’t obsess over perfect placement. Thirty minutes is “good enough,” not consulting theater. Matrix orgs and startups look different; adapt labels, don’t force a Fortune-500 model onto a ten-person team. For how functions actually collide, see How departments work together.
Steps inside the 30-minute box
- Minutes 0-8: List. Brain-dump 8-15 names tied to your goals: manager, skip if relevant, peers, cross-functional partners (product, sales, finance, support, legal), and anyone who can block or unblock delivery. Skip celebrities you’ll never meet.
- Minutes 8-18: Plot. Fill care-about, influence, and interest. Be honest about blockers. Under-ranking quiet blockers is a common miss; over-ranking distant execs is the other.
- Minutes 18-25: Prioritize outreach. Star five people for action this week. Each star needs a micro-action and a date.
- Minutes 25-30: Schedule or queue. Send intro asks, hold calendar holds, or add “monitor” notes. Put the top-five list at the top of the doc.
Refresh the map every 2-4 weeks, or after a scope change. A static map lies.
Script: manager review in a 1:1
I drafted a one-page stakeholder map for [role/project] with next actions, not a political ranking. Can we spend five minutes on who’s missing or mis-weighted? I especially want a sanity check on [Name] and [Name].
If your manager adds someone: write the action in the room (“You’ll intro me by Friday” or “I’ll request 15 minutes”).
Output
- One-page living map (table above).
- Top-5 outreach checklist for this week:
Top 5 this week
1. [Name]: [micro-action] by [day]
2. ...
5. ...
Monitor only: [names]
Last refreshed: [date]
Sample (fictional project): Jordan owns a checkout redesign. Map includes Sam (Legal, high influence on copy), Priya (Eng lead, high interest), Maya (manager), and Alex (Support, early reader). Next actions: warm intro to Sam, 15-minute listen with Priya, CC Maya on weekly async update. Distant VP stays on “monitor.” Labeled sample only; your cast will differ.
Watch-outs
- Pretty org chart syndrome. No action column means you wasted 30 minutes.
- Gossip mode. Never encode rumors as “influence facts.”
- Exec tourism. Mapping people you’ll never interact with crowds out real partners.
- Sharing the map broadly. Keep it private. It’s a work tool, not a scoreboard.
- One-and-done. Org charts move. Refresh on a calendar reminder.
How this connects
Run this after (or alongside) the First-week question list play so names from those chats land on the map. Use the map to decide who gets your async update and whose forums need a read-the-room checklist. For longer ramp context, see first 90 days and skills vs. visibility.
A good-enough map is eight to twelve names, five actions, and a refresh date. Stop when the next action list is clear. Start again when the work or the org changes.