1. Stakeholder Register
| Name | Role | Interest Level | Influence Level | Expectations | Engagement Strategy | Owner |
|---|---|---|---|---|---|---|
| Jane Doe | Project Sponsor | High | High | On-time delivery, clear budget | Biweekly updates + executive summary | PM |
| Alex Li | End User Rep | Medium | Low | Easy-to-use interface | Invite to sprint demos | UX Lead |
| QA Team | Quality | High | Medium | Test environment access | Weekly updates + Slack channel | PM |
Tip: Use High/Medium/Low or 1–5 scoring to evaluate Influence and Interest.
2. Stakeholder Analysis Grid
| Category | Description |
|---|---|
| High Influence / High Interest | Engage closely. Keep fully informed. |
| High Influence / Low Interest | Keep satisfied. Don’t overload with detail. |
| Low Influence / High Interest | Keep informed. Provide context, not deep involvement. |
| Low Influence / Low Interest | Monitor, minimal engagement unless needed. |
Use this to place stakeholders on an engagement map (Notion doesn’t support visual quadrant yet — but you can manually cluster them by category).
3. Engagement Strategies
| Engagement Type | Description | Tools/Channels | Frequency |
|---|---|---|---|
| Inform | One-way communication (status updates, emails) | Email, Notion, Dashboards | Weekly / Monthly |
| Consult | Two-way input (surveys, feedback sessions) | Meetings, Slack, Forms | At milestones |
| Involve | Active participation (reviews, testing) | Workshops, Sprints, Demo Days | As scheduled |
| Collaborate | Shared ownership (decisions, planning) | Co-working sessions, Steering Committee | Biweekly or custom |
4. Communication & Access Methods
| Stakeholder Group | Communication Tool | Format | Notes |
|---|---|---|---|
| Execs / Sponsors | Email + Notion | Summary briefings | Monthly metrics + decisions only |
| Delivery Team | Slack + Jira | Real-time threads + task comments | Keep tight sync |
| External Partners | Zoom + Docs | Formal reviews | Gate-based checkpoints |
5. Engagement Tracking
| Stakeholder | Last Interaction | Next Scheduled | Feedback | Notes / Risks |
|---|---|---|---|---|
| Sponsor | 6/1 (report sent) | 6/10 | Positive, asked for timeline view | Wants early notice on delays |
| QA Team | 6/3 standup | Ongoing | Flagged tool issue | Escalation if not fixed |
6. Risks & Escalation Points
- Sponsor unavailability = delays in decisions
- External stakeholders unclear on deliverables = misaligned expectations
- Stakeholder conflict between product and ops teams
Include a short mitigation plan for each.