What This Template Is For
The biggest risk to most product initiatives is not technical complexity or market timing. It is stakeholder misalignment. When key decision-makers are surprised, uninformed, or feel excluded, projects stall. Features get redesigned late. Launches get delayed. Trust erodes.
The Stakeholder Management Handbook covers the full discipline of stakeholder management in depth. This template provides five interconnected tools for managing stakeholder relationships systematically: a stakeholder identification worksheet, a power/interest grid for prioritization, a RACI matrix for decision rights, a communication plan for consistent updates, and templates for meeting cadences and status reports. Together, they ensure the right people get the right information at the right time.
When to Use This Template
- Kicking off a new initiative or project: Map stakeholders before work begins, not after the first conflict.
- Joining a new team or company: Build your stakeholder map in your first two weeks to understand the political landscape.
- Launching a cross-functional effort: Any initiative touching more than two teams needs explicit stakeholder management.
- Recovering from a miscommunication: If you have been surprised by stakeholder feedback, this template helps you prevent the next surprise.
- Preparing for a major launch: Use the Product Launch Playbook to coordinate the full launch process, and ensure every stakeholder knows what is happening, when, and what is expected of them.
The golden rule of stakeholder management: No surprises. If a stakeholder learns about a decision from someone other than you, your communication plan has a gap.
Step-by-Step Instructions
Step 1: Identify All Stakeholders (5 minutes)
List every person or group who has influence over your initiative or is affected by its outcome. Cast a wide net initially. You can deprioritize later.
- ☐ Executive sponsors and decision-makers
- ☐ Direct manager and skip-level leadership
- ☐ Cross-functional partners (engineering, design, marketing, sales, support, legal, finance)
- ☐ External stakeholders (customers, partners, vendors, regulators)
- ☐ Team members doing the work
- ☐ Anyone who blocked or delayed a similar initiative in the past
Step 2: Assess Power and Interest (5 minutes)
For each stakeholder, assess two dimensions:
- Power: How much influence do they have over the initiative's success? Can they approve, block, fund, or de-prioritize it?
- Interest: How much do they care about the initiative? Will they actively engage, or is this a low priority for them?
Plot each stakeholder on the power/interest grid below.
Step 3: Define Decision Rights with RACI (10 minutes)
For each major decision or deliverable, assign roles using the RACI model:
- R = Responsible: Does the work.
- A = Accountable: Makes the final decision. Only one A per row.
- C = Consulted: Provides input before the decision. Two-way communication.
- I = Informed: Told after the decision. One-way communication.
Step 4: Build the Communication Plan (5 minutes)
For each stakeholder group, define what information they receive, how often, through what channel, and who delivers it.
Step 5: Set Up Meeting Cadences and Templates (5 minutes)
Define recurring meeting structures and use the status update template for async communication.
Template 1: Stakeholder Identification Worksheet
List all stakeholders and capture the essential context you need to manage each relationship.
| # | Name | Role / Title | Team | Relationship to Initiative | What They Care About | Potential Concerns | Current Sentiment |
|---|---|---|---|---|---|---|---|
| 1 | [Name] | [Title] | [Team] | [Sponsor / Approver / Contributor / Affected] | [Their priorities and motivations] | [What might make them resist or push back] | [Supportive / Neutral / Skeptical / Opposed] |
| 2 | [Name] | [Title] | [Team] | ||||
| 3 | [Name] | [Title] | [Team] | ||||
| 4 | [Name] | [Title] | [Team] | ||||
| 5 | [Name] | [Title] | [Team] | ||||
| 6 | [Name] | [Title] | [Team] | ||||
| 7 | [Name] | [Title] | [Team] | ||||
| 8 | [Name] | [Title] | [Team] |
Template 2: Power/Interest Grid
Plot each stakeholder into one of four quadrants. The quadrant determines your engagement strategy.
HIGH POWER
|
KEEP SATISFIED | MANAGE CLOSELY
|
These stakeholders | These are your most
have power but low | critical stakeholders.
interest. Keep them | Engage deeply, consult
informed and happy. | regularly, never
Do not overwhelm | surprise them.
with detail. |
|
LOW INTEREST ------------|------------- HIGH INTEREST
|
MONITOR | KEEP INFORMED
|
Low power, low | High interest but low
interest. Minimal | power. Keep them in
effort required. | the loop. They are
Check in | often your champions
occasionally. | and early warning
| system.
|
LOW POWER
Stakeholder Placement
| Quadrant | Stakeholders | Engagement Strategy |
|---|---|---|
| Manage Closely (High Power, High Interest) | [Names] | Weekly 1:1 updates, consulted on all major decisions, preview materials before broader sharing |
| Keep Satisfied (High Power, Low Interest) | [Names] | Monthly summary updates, escalate only critical decisions, keep communications concise |
| Keep Informed (Low Power, High Interest) | [Names] | Regular team updates, invite to demos and reviews, use as advocates and feedback sources |
| Monitor (Low Power, Low Interest) | [Names] | Quarterly updates or as-needed, included in broad communications only |
Template 3: RACI Matrix
Define decision rights for every major deliverable or decision point. The single most important rule: there must be exactly one "A" (Accountable) per row.
| Decision / Deliverable | [Person 1] | [Person 2] | [Person 3] | [Person 4] | [Person 5] | [Person 6] |
|---|---|---|---|---|---|---|
| [e.g., Product requirements] | A | R | C | C | I | I |
| [e.g., Design direction] | C | R | A | I | I | I |
| [e.g., Technical architecture] | I | C | I | A | R | I |
| [e.g., Go-to-market plan] | C | I | I | I | I | A |
| [e.g., Launch decision] | A | C | C | C | I | C |
| [e.g., Budget approval] | A | I | I | I | I | I |
| [e.g., Pricing] | A | C | I | I | I | C |
| [e.g., Customer communication] | C | I | I | I | I | A |
RACI Validation Checklist
- ☐ Every row has exactly one "A"
- ☐ No person is "A" on more than 3-4 items (to prevent bottlenecks)
- ☐ Every row has at least one "R"
- ☐ The people marked "C" have been told they will be consulted and have agreed
- ☐ "I" stakeholders know they will be informed after decisions, not before
- ☐ The team has reviewed and agreed to the RACI assignments
Template 4: Communication Plan
| Stakeholder / Group | Information They Need | Frequency | Channel | Format | Owner | Notes |
|---|---|---|---|---|---|---|
| [Executive sponsor] | Progress against goals, risks, decisions needed | Weekly | 1:1 meeting | 15-min verbal update with one-page written brief | [PM name] | Prefers concise bullets, not slides |
| [Engineering lead] | Requirements, priorities, timeline changes | Daily standup + weekly sync | Slack + meeting | Standup: async. Sync: 30-min meeting with agenda | [PM name] | Prefers detailed technical context |
| [Design partner] | User research, requirements, feedback on designs | 2x per week | Design review meeting | FigJam or Figma with comments | [PM name] | Likes collaborative working sessions |
| [Sales team] | Feature updates, launch timeline, competitive positioning | Bi-weekly | Email + Slack channel | Written update with customer-facing messaging | [PMM name] | Needs customer-ready language |
| [Customer success] | Release dates, known issues, customer impact | Weekly | CS Slack channel | Written release notes + FAQ | [PM name] | Needs info before customers ask about it |
| [Full leadership team] | Quarterly progress, strategic decisions | Monthly | Leadership meeting | 5-slide deck with data | [PM name] | 10-minute slot, leave time for questions |
| [Broader company] | Major milestones and launches | As needed | All-hands or company Slack | Announcement post | [PM name] | Keep it celebratory and concise |
Template 5: Meeting Cadence
Recurring Meetings
| Meeting | Purpose | Attendees | Frequency | Duration | Owner | Agenda Template |
|---|---|---|---|---|---|---|
| Executive check-in | Align on priorities, surface risks, get decisions | PM + Executive sponsor | Weekly | 15 min | PM | Progress, risks, decisions needed |
| Cross-functional sync | Coordinate across engineering, design, and PM | PM + Eng lead + Design lead | Weekly | 30 min | PM | Last week, this week, blockers |
| Stakeholder review | Present progress to all key stakeholders | All "Manage Closely" stakeholders | Bi-weekly | 45 min | PM | Demo, metrics, upcoming milestones, open questions |
| Sprint planning | Plan the upcoming sprint's work | Product team | Bi-weekly | 60 min | PM + Eng lead | Priorities, capacity, commitments |
| Retrospective | Reflect on what went well and what to improve | Product team | Bi-weekly | 45 min | Rotating | What went well, what did not, what to change |
Meeting Best Practices Checklist
- ☐ Every meeting has a written agenda shared 24 hours in advance
- ☐ Action items are captured with owners and due dates
- ☐ Meetings end 5 minutes early to allow for transition
- ☐ Standing meetings are reviewed monthly for continued relevance
- ☐ Async alternatives are used when a meeting is purely informational (write a doc instead)
Template 6: Status Update Template
Use this template for weekly written status updates to stakeholders. Keep it to one page or less.
Project: [Project name]
Date: [Date]
Author: [Your name]
Overall status: On Track / At Risk / Off Track
Progress This Week
- [Accomplishment 1]
- [Accomplishment 2]
- [Accomplishment 3]
Upcoming This Week
- [Planned item 1]
- [Planned item 2]
- [Planned item 3]
Risks and Blockers
| Risk / Blocker | Impact | Mitigation | Help Needed From |
|---|---|---|---|
| [Risk 1] | [What happens if unresolved] | [What you are doing about it] | [Who can help] |
| [Risk 2] | [What happens if unresolved] | [What you are doing about it] | [Who can help] |
Decisions Needed
| Decision | Context | Options | Deadline | Decision Maker |
|---|---|---|---|---|
| [Decision 1] | [Brief context] | [Option A vs. Option B] | [Date] | [Name] |
Key Metrics
| Metric | Target | Current | Trend |
|---|---|---|---|
| [Metric 1] | [Target] | [Current value] | [Up / Down / Flat] |
| [Metric 2] | [Target] | [Current value] | [Up / Down / Flat] |
Filled-Out Example: SaaS Feature Launch
Stakeholder Identification (Example)
| # | Name | Role | Team | Relationship | What They Care About | Concerns | Sentiment |
|---|---|---|---|---|---|---|---|
| 1 | Maria Chen | VP Product | Product | Executive sponsor | On-time delivery, customer impact, alignment with annual goals | Team may be overcommitted this quarter | Supportive |
| 2 | James Okafor | Engineering Manager | Engineering | Technical lead | Technical feasibility, code quality, team capacity | Scope creep, insufficient design specs | Neutral |
| 3 | Priya Sharma | Head of Design | Design | Design partner | User experience quality, research-backed decisions | Being brought in too late for meaningful input | Supportive |
| 4 | Carlos Rivera | Sales Director | Sales | Affected by launch | Revenue impact, customer-facing messaging, competitive positioning | Feature may not address the top sales objection | Skeptical |
| 5 | Aisha Johnson | CS Lead | Customer Success | Affected by launch | Customer readiness, support documentation, known issues | Customers will have questions her team cannot answer | Neutral |
| 6 | David Kim | CFO | Finance | Budget approver | Cost, ROI timeline | Cost overruns if timeline extends | Neutral |
Power/Interest Placement (Example)
| Quadrant | Stakeholders | Strategy |
|---|---|---|
| Manage Closely | Maria Chen (VP Product), James Okafor (Eng Manager) | Weekly 1:1 updates, included in all key decisions |
| Keep Satisfied | David Kim (CFO) | Monthly budget update, escalate only if cost changes |
| Keep Informed | Priya Sharma (Design), Aisha Johnson (CS) | Bi-weekly sync, included in demos and reviews |
| Monitor | Carlos Rivera (Sales) | Bi-weekly email update, looped in for launch messaging |
RACI (Example)
| Decision | Maria (VP) | James (Eng) | Priya (Design) | Carlos (Sales) | Aisha (CS) | David (CFO) |
|---|---|---|---|---|---|---|
| Product requirements | A | C | C | C | I | I |
| Technical architecture | I | A | I | I | I | I |
| Design direction | C | I | A | I | I | I |
| Launch date | A | C | C | I | C | I |
| Pricing | A | I | I | C | I | C |
| Go-to-market messaging | C | I | I | A | C | I |
Tips for Getting the Most Out of This Template
- Map stakeholders before the kickoff, not after. The most common stakeholder management failure is reactive. Discovering a critical stakeholder after they have already formed a negative opinion. Spend 30 minutes mapping stakeholders before work begins.
- Manage up and sideways, not just down. Product managers often focus on their immediate team while neglecting executive sponsors, peer PMs, and cross-functional leads. Your RACI and communication plan should reflect all directions.
- Adapt your communication style to each stakeholder. Your CFO wants a one-page summary with numbers. Your design lead wants to discuss user research in a collaborative session. Your engineering manager wants technical detail. One format does not fit all.
- Refresh the stakeholder map at major milestones. New stakeholders emerge as projects progress (e.g., legal gets involved before launch, the support team becomes critical during rollout). Update your map at each phase transition.
- Track sentiment changes. If a stakeholder shifts from "Supportive" to "Skeptical," that is a signal to investigate. Schedule a 1:1 to understand their concerns before they escalate.
- Use the RACI to prevent design-by-committee. When everyone feels like they should approve every decision, progress stalls. The RACI makes decision rights explicit, so people know when they are consulted versus informed. For guidance on prioritizing which stakeholder conflicts to address first, focus on the "Manage Closely" quadrant of the power/interest grid.
- Write status updates even when there is nothing exciting to report. Consistent communication builds trust. A brief "on track, no blockers" update is better than silence, which stakeholders often interpret as a problem.
- Ask stakeholders how they want to be communicated with. Do not assume. Some prefer Slack messages, others prefer email, others want a scheduled meeting. Ask each "Manage Closely" stakeholder directly: "What format and frequency works best for you?"
Key Takeaways
- Stakeholder management is a proactive discipline, not a reactive one. Map stakeholders before work begins
- Use the power/interest grid to allocate your communication effort where it matters most
- The RACI matrix prevents decision-by-committee by making one person accountable for each decision
- Consistent status updates build trust. Even "on track, no news" is valuable
- Adapt your communication style, frequency, and channel to each stakeholder's preferences
- Refresh the stakeholder map at each project milestone and whenever the organizational context changes
About This Template
Created by: Tim Adair
Last Updated: 2/8/2026
Version: 1.0.0
License: Free for personal and commercial use
