A product manager's real job is not to write specs. It's to choreograph the humans around a product so the right decisions get made at the right time. That starts with knowing who the humans are, and what they care about.
In the last decades of the 20th century, the word "stakeholder" became more commonly used to mean a person or organization that has a legitimate interest in a project or entity. The concept has been broadened to include everyone with an interest (or "stake") in what the entity does. , Wikipedia
That's the definition to start with. But a useful definition for a PM is narrower: a stakeholder is someone whose buy-in, information, or silence you need to ship. If they're not on that list, they're audience, not stakeholder.
The two axes that matter
Every stakeholder can be classified along two dimensions: Power (can they change the product?) and Interest (do they care what happens to it?).
Crossing those two axes gives four archetypes. Each needs a different kind of relationship, and failing to match the relationship to the archetype is how PMs get ambushed in meetings.
Deep interest, no veto. The users, operatives, and day-to-day champions whose feedback is gold.
Your co-owners. Team leaders, operations managers, key clients. Work with them, not for them.
Regular users and residents. They pull information when they want it. Make it easy.
Board, Legal, Finance, HR. Can change the product but usually don't follow closely. Keep them in the loop; protect from surprises.
The four archetypes, in depth
Each category needs a specific communication approach, cadence, and technique. Here's what each one looks like in practice.
Players
High power · High interest
Collaborate / Partner
Who they are
Key shareholders and users of the product. Team leaders. Operations managers. The people whose authority and engagement are both high. In short: co-owners of the outcome.
Your goal
- Establish a trusting relationship
- Be ready to work through constructive conflict
- Work with them, not for them
How to communicate
Involve them in any meeting where strategic decisions are made. One-on-ones to understand their pains. Bring their influence to bear on your behalf.
Techniques
- Strategic / roadmap meetings
- Workshops and demos
- Weekly 1:1 status & strategy
- Written status updates
Subjects
Low power · High interest
Involve / Keep satisfied
Who they are
Users of the product with no veto power but deep interest: managers, subcontractors, administrators, operatives, client residents, bid teams, support, IT. Key for the project.
Your goal
- Gather ideas and opinions
- Get feedback regularly
- Evolve a real feel for their needs and use it to make informed product decisions
How to communicate
Keep them up to date with the overall direction. Ask often for feedback. Bounce ideas off them, they'll spot your blind spots faster than anyone on your team.
Techniques
- Weekly status email
- Product demos
- Sprint review meetings
- Office hours / open forum
Context setters
High power · Low interest
Consult / Keep informed
Who they are
The Board, HR, Legal, Finance. People with the formal power to change the product but limited day-to-day interest. Their relevance spikes at moments, and you need to be ready.
Your goal
- Establish enough of a relationship that needs and concerns aren't unheard
- Say no when the data supports a different direction, respectfully
How to communicate
Consult regularly so their opinions are expressed and recorded. No surprises, ever. If they learn something important from a meeting they weren't in, you've failed.
Techniques
- One-to-one status & strategy meetings
- Weekly status update (email or short meeting)
- Quarterly deep-dive
Crowd
Low power · Low interest
Monitor / Inform
Who they are
All regular users, customers, operatives, residents. They use the product but aren't activated. The silent majority.
Your goal
- Keep them informed so awareness, sentiment and adoption can grow
- Make information pullable, they shouldn't have to ask
How to communicate
Make it easy to find what they need when they want it: trainings, user documentation, recorded demos. Push only when you have something worth pushing.
Techniques
- Presentation website / company pages
- User documentation & self-serve trainings
- Monthly / quarterly email
- Release notifications
For every conversation, lead with three things
Motivators
What moves this person toward a yes?
Priorities
What is on their top-three list this quarter?
Positive view
If not "what should we do?", then "what should we avoid?"
The Stakeholder Map, a working template
Theory gets you nothing without a list of real names. The Stakeholder Map has two parts: the Power/Interest grid above tells you how to engage each person. The table below tells you what each person cares about.
Engagement cadence at a glance
| Low interest | High interest | |
|---|---|---|
| High power | Keep satisfied, brief updates, no surprises | Manage closely, deep engagement, regular 1:1s |
| Low power | Monitor, minimal effort, acknowledge only | Keep informed, regular comms, bring them along |
The stakeholder table
Fill this in with 5–10 real people. Update the current stance column monthly.
| Name / Role | Dept | Power | Interest | Stance | What they care about | Cadence |
|---|---|---|---|---|---|---|
| Head of Data Management | Data | High | High | Champion | Regulatory reporting, data quality, team credibility | Weekly 1:1 |
| Head of Technology | Technology | High | Medium | Skeptic | Infrastructure stability, not being sidelined | Bi-weekly 1:1 · pre-align before joint meetings |
| Vendor PM | External | Medium | High | Supporter | Delivery reputation, scope clarity | Daily / weekly ops calls |
| Legacy system user lead | Business | Low | High | Skeptic | Not having their workflow broken | Monthly update · pilot invitation |
| [Add more as needed] |
Stance vocabulary
Five labels, used consistently:
Champion Supporter Neutral Skeptic Blocker
People move between these labels as the project evolves. That's why this column has to be reviewed monthly, yesterday's champion can be today's skeptic if you stop listening.
The five rules
- Five to ten names. More than that, you're padding. Fewer, and you're missing someone.
- Update the current stance column monthly. People move as the project evolves.
- Lead with what they care about, not with what you want. Speak to their concerns, not yours.
- Pre-align skeptics and blockers one-on-one before any group meeting. No surprises in rooms.
- The format is less important than the habit. A messy spreadsheet updated weekly beats a beautiful one that hasn't changed in three months.
The highest-leverage habit Before any meeting with three or more stakeholders, spend fifteen minutes one-on-one with the most skeptical person in the room. You are not trying to change their mind. You are trying to ensure they don't surprise you.
A field guide to stakeholder patterns
A bit of humour to close: beyond the four archetypes, there are recognisable behavioural patterns to watch for in any org. Productboard's Dangerous Animals of Product Management 2.0 is a useful taxonomy, know the species so you can recognise the behaviour early.
🦛
HiPPO
Highest Paid Person's Opinion
Decisions go the way the most senior person in the room wants. Saying no is hard, but letting the HiPPO decide everything kills team morale and ships unvalidated features.
🦓
ZEbRA
Zero Evidence but Really Arrogant
Gut-feel strategy dressed up as certainty. Sometimes lucky. Usually a sound strategy to avoid.
🐦
Seagull
The Seagull Manager
Swoops in, causes a ruckus, swoops out. Leaves the team to clean up. Good intentions; no on-the-ground perspective.
🐺
WoLF
Works on Latest Fire
Neglects technical debt. Everything becomes reactive. Productivity and innovation quietly erode.
🦏
RHiNO
Really High-value New Opportunity
"If we just had feature X, we'd close this one giant customer." One-off requests crowd out real problems.
🐡
PUFFIn
Plans Unending Feature Factory Initiatives
Jumps from shiny new feature to shiny new feature. Hello, feature factory.
🪿
GOOSE
Guesstimating Overly Optimistic Scheduling Estimates
Forgets engineering reality. Always over-promising, always under-delivering.
🐆
PUMA
Promotes Unusually Meaningless Assumptions
Snap judgements dressed as insight. Scratches the surface without digging into data and customer needs.
🐍
CoBRA
Cognitive Bias Related Assertions
Snap decisions shaped by unexamined bias. Slow down, check your judgement, then strike.
🐂
YAK
Yet Another KPI
Adding metrics until they drown meaning. Metrics are only useful if they move the behaviour you want.
Source: Productboard, The Dangerous Animals of Product Management 2.0.
Putting it all together
Start with the grid. Populate the table. Talk to each person on the list this week. Update the stance column in a month. The discipline compounds, and within a quarter you'll find yourself walking into rooms where the outcome is already pre-aligned, because the hard conversations happened one-on-one, early.
That's the work.
What to read next
Great stakeholder management only pays off when you have a real plan to present. Start with the Solutions Workflow if you haven't already, or use the Solution Document as your next meeting's pre-read.