A practical guide for Product Managers — frameworks, templates, and playbooks
Plot stakeholders based on their power (ability to block or accelerate your product) and interest (how much they care about your product area). Each quadrant tells you the right engagement strategy.
High Power × High Interest — Your inner circle
High Power × Low Interest — Can block you if ignored
Low Power × High Interest — Champions & advocates
Low Power × Low Interest — Minimal effort
← LOW INTEREST HIGH INTEREST →
1. List every person (not role) who touches your product decisions.
2. Score each on Power (1–5) and Interest (1–5).
3. Plot them into quadrants. Review monthly — people shift quadrants as projects evolve.
4. Adjust your engagement strategy accordingly. Someone moving from "Monitor" to "Manage Closely" mid-project is a signal to increase communication immediately.
| Stakeholder | What They Care About | What They Need From You | Priority |
|---|---|---|---|
| Engineering Lead / Manager Core Team |
Clear requirements, technical feasibility, team velocity, minimal scope churn | Well-written specs, stable priorities, early heads-up on changes, removing blockers | Critical |
| Design Lead Core Team |
User experience quality, research-backed decisions, design consistency | User context, problem framing (not solutions), time for exploration, design review slots | Critical |
| VP / Director of Product Leadership |
Strategy alignment, metrics progress, team health, cross-product coherence | Regular metric updates, risk flags, strategic recommendations, decision escalations | Critical |
| CEO / CTO Executive |
Business outcomes, market position, revenue growth, strategic bets | Concise impact summaries, strategic narrative, confidence in team execution | High |
| Sales & Account Management GTM |
Feature timelines for deals, competitive gaps, customer-requested features | Honest timelines, feature talking points, early access to beta, "what's coming" previews | High |
| Marketing GTM |
Launch dates, positioning, differentiators, customer stories | Launch briefs 4–6 weeks early, messaging input, access to beta users for case studies | High |
| Customer Success / Support Customer |
Feature adoption, churn risk, support ticket volume, user pain points | Release notes, known issues, migration guides, feedback loops that show you listened | High |
| Data / Analytics Enabler |
Correct instrumentation, data quality, meaningful metrics | Clear success metrics upfront, tracking requirements in specs, analysis requests with context | Medium |
| Legal / Compliance Gatekeeper |
Regulatory risk, data privacy, terms of service, IP issues | Early review requests (not last-minute), clear scope of what you're building, patience | Medium |
| Finance Gatekeeper |
Budget adherence, ROI, unit economics, cost projections | Business cases for new investments, cost impact of decisions, revenue projections | Medium |
| Customers / End Users External |
Product solves their problem, reliability, value for money, being heard | Feedback channels, transparent roadmap, consistent quality, responsive support | Critical |
| Partners / Integration Teams External |
API stability, documentation, mutual business value, joint roadmap | Stable APIs, deprecation notices, co-marketing opportunities, technical support | Medium |
Match cadence and format to each stakeholder's quadrant. The golden rule: no one should ever be surprised by your decisions.
| Stakeholder | Cadence | Format | Content Focus | Pro Tip |
|---|---|---|---|---|
| Engineering Lead | Daily standup + Weekly 1:1 | Standup, Slack, Doc reviews | Sprint progress, blockers, upcoming spec reviews, tech debt trade-offs | Share spec drafts 2 days before review so they can think async |
| Design Lead | 2–3x per week | Figma sessions, Slack, Syncs | User problems, research insights, design direction alignment | Frame problems, not solutions — let design explore |
| VP of Product | Weekly 1:1 | 1-pager or deck + verbal | Metrics, risks, decisions needed, strategic alignment | Lead with "what I need from you" — their time is scarce |
| CEO / CTO | Monthly / Quarterly | Executive summary email or brief | Business impact, strategic wins, key metrics, upcoming bets | 3 bullets max. Lead with outcomes, not activities |
| Sales | Biweekly | Slack channel + Monthly sync | Feature releases, roadmap previews, competitive responses | Give them a "cheat sheet" they can share with prospects |
| Marketing | Biweekly + Launch sprints | Launch brief doc, Slack | Positioning, timelines, user stories, differentiators | Loop in 6 weeks before launch, not 6 days |
| Customer Success | Biweekly | Release notes, Slack, Sync | What shipped, known issues, migration impact, feedback themes | Share "what we heard and what we did about it" summaries |
| Legal / Compliance | As needed (early!) | Review doc + Meeting | Data handling, user terms, regulatory impact | Send review requests with 2-week lead time minimum |
| Data / Analytics | Per feature cycle | Tracking spec in PRD | Success metrics, event tracking requirements, analysis requests | Include tracking requirements in every spec, not as an afterthought |
| Broader Org | Monthly / Quarterly | Newsletter, All-hands, Wiki | Wins, learnings, what's next | Celebrate the team, share user impact stories |
Responsible — does the work
Accountable — owns the outcome (only 1 per task)
Consulted — provides input before decision
Informed — notified after decision
Use when: Roles are unclear, decisions are slow, or too many people think they have veto power.
Classifies stakeholders on three attributes:
Power — can they impose their will?
Legitimacy — is their involvement appropriate?
Urgency — do they need immediate attention?
Use when: You need to decide WHO to prioritize among many competing voices.
Similar to Power/Interest but focuses on:
Influence — how much they can sway others
Impact — how much the project affects them
Use when: You need to identify hidden influencers who don't have formal authority but shape opinions.
Concentric circles showing proximity:
Core — product team (PM, Eng, Design)
Inner Ring — direct stakeholders (Sales, CS, Marketing)
Outer Ring — indirect stakeholders (Legal, Finance, HR)
External — customers, partners, regulators
Use when: Explaining to your team why some stakeholders get more access and influence than others.
Track where each stakeholder sits on the commitment spectrum:
Hostile → Resistant → Neutral → Supportive → Champion
Use when: You need to move specific people from resistance to support — helps you plan targeted influence strategies.
Recommend — proposes the decision (usually PM)
Agree — must agree (can veto)
Perform — executes after decision
Input — provides info/analysis
Decide — makes the final call
Use when: Decisions stall because nobody knows who has the final say.
Real scenarios PMs face, with tested response strategies.
"We'll lose a $500K deal if we don't build X by next quarter."
"I had a great idea over the weekend — can we add this to the current release?"
"This is overengineered. We can't build this in the timeline you're proposing."
Marketing wants a simple onboarding flow; Enterprise Sales wants extensive customization options.
An executive directly tells engineering to build something without consulting you.