Skip to content

borghei/Claude-Skills / project-management/senior-pm

senior-pm

Verified

Scores portfolio health, risk exposure and resource capacity from a project JSON and frames board-ready status reports. Use when running a portfolio review, writing an executive RAG report, or rebalancing people across projects.

references/stakeholder-engagement-guide.md

View on GitHub
# Stakeholder Engagement Guide for Senior Project Managers

## Executive Summary

This guide provides senior project managers with a structured approach to stakeholder identification, classification, engagement, and communication. It centers on Mendelow's Power/Interest Grid as the primary classification framework, with practical engagement tactics, communication templates, influence mapping techniques, and strategies for handling resistance.

---

## Power/Interest Grid Framework (Mendelow's Matrix)

### Overview

Mendelow's Matrix is a two-dimensional model that classifies stakeholders based on two axes:

- **Power** (vertical axis): The stakeholder's ability to influence project decisions, resources, and outcomes
- **Interest** (horizontal axis): The stakeholder's level of concern or engagement with the project

This creates four quadrants, each requiring a distinct engagement strategy.

### The Four Quadrants

```
  Power
  HIGH  | Keep Satisfied      | Manage Closely      |
        | (low interest)      | (high interest)     |
  ------+---------------------+---------------------+
  LOW   | Monitor             | Keep Informed       |
        | (low interest)      | (high interest)     |
        +---------------------+---------------------+
               LOW                   HIGH
                       Interest
```

### Quadrant 1: Manage Closely (High Power / High Interest)

**Who they are:** Executive sponsors, key decision-makers, product owners, and senior leaders with direct project involvement.

**Why they matter:** These stakeholders can make or break your project. They have both the authority to influence outcomes and the motivation to do so.

**Engagement approach:**
- Treat as partners, not just recipients of information
- Involve in decision-making and trade-off discussions
- Provide advance notice of issues before they escalate
- Seek their input on strategy and direction

### Quadrant 2: Keep Satisfied (High Power / Low Interest)

**Who they are:** C-suite executives, board members, regulatory bodies, and senior leaders with oversight but not daily involvement.

**Why they matter:** While they may not be engaged day-to-day, they can intervene and redirect the project at any time. Dissatisfaction can trigger sudden, disruptive involvement.

**Engagement approach:**
- Respect their time with concise, outcome-focused updates
- Escalate only significant issues that require their authority
- Ensure they feel confident the project is under control
- Avoid unnecessary detail or frequent meetings

### Quadrant 3: Keep Informed (Low Power / High Interest)

**Who they are:** End users, team members, subject matter experts, and community stakeholders who care about outcomes but lack decision authority.

**Why they matter:** They provide valuable feedback, influence organizational sentiment, and can become advocates or detractors. Their collective voice can shift stakeholder power dynamics.

**Engagement approach:**
- Provide regular updates through accessible channels
- Create opportunities for input and feedback
- Acknowledge their interest and contributions
- Use them as project champions and early adopters

### Quadrant 4: Monitor (Low Power / Low Interest)

**Who they are:** Tangentially affected departments, external observers, and stakeholders with minimal connection to the project.

**Why they matter:** While low priority, their position can change. A compliance issue might suddenly give a regulatory observer high power, or organizational changes might shift interest levels.

**Engagement approach:**
- Light-touch communication via existing channels
- Make information available on-demand
- Periodically re-assess their classification
- Watch for signals that power or interest is increasing

---

## Stakeholder Classification Strategies

### Initial Identification Techniques

1. **Organizational chart analysis:** Map reporting lines and identify formal authority
2. **Process mapping:** Identify who is affected by project inputs and outputs
3. **Budget trail:** Follow funding sources to uncover financial stakeholders
4. **Regulatory scan:** Identify compliance and governance stakeholders
5. **Historical review:** Look at who was involved in similar past projects
6. **Snowball method:** Ask known stakeholders "Who else should be involved?"

### Assessing Power

Power comes from multiple sources. Evaluate each stakeholder across these dimensions:

| Power Source | Description | Assessment Question |
|---|---|---|
| **Positional** | Authority from organizational role | Can they approve, block, or redirect the project? |
| **Resource** | Control over budget, people, or tools | Do they control resources the project needs? |
| **Expert** | Specialized knowledge or skills | Does the project depend on their expertise? |
| **Political** | Relationships and organizational influence | Can they mobilize support or opposition? |
| **Informational** | Access to critical data or communication channels | Do they control information flow? |

### Assessing Interest

Interest is driven by how much the project affects the stakeholder:

| Interest Driver | Indicators |
|---|---|
| **Direct impact** | Their work processes, tools, or team will change |
| **Performance link** | Their KPIs or OKRs are affected by project outcomes |
| **Strategic alignment** | The project advances or threatens their strategic goals |
| **Career implications** | Project success/failure affects their professional standing |
| **Personal values** | The project aligns with or conflicts with their beliefs |

### Dynamic Reclassification

Stakeholder positions are not static. Reassess classifications when:

- Project scope changes significantly
- Organizational restructuring occurs
- A major risk materializes
- Budget or timeline shifts substantially
- New regulatory requirements emerge
- A stakeholder changes roles or responsibilities

---

## Communication Plan Templates per Quadrant

### Manage Closely - Communication Plan

| Element | Detail |
|---|---|
| **Frequency** | Weekly (minimum) |
| **Format** | 1:1 meetings, steering committee, ad-hoc calls |
| **Content** | Detailed status, risks, decisions needed, financial health |
| **Preparation** | Tailored agenda, pre-read materials, decision frameworks |
| **Follow-up** | Meeting minutes within 24 hours, action items tracked |
| **Escalation** | Immediate for blockers; same-day for emerging risks |

**Sample weekly update structure:**
1. Key accomplishments this week (3-5 bullets)
2. Upcoming milestones and dependencies
3. Risks and issues requiring attention
4. Decisions needed (with recommendations)
5. Resource or budget concerns
6. Next week priorities

### Keep Satisfied - Communication Plan

| Element | Detail |
|---|---|
| **Frequency** | Monthly (or at major milestones) |
| **Format** | Executive summary email, quarterly review presentation |
| **Content** | High-level status, budget vs. actual, strategic impact |
| **Preparation** | One-page dashboard, RAG status, executive talking points |
| **Follow-up** | Action items only if their input was requested |
| **Escalation** | Only for issues requiring their authority or budget approval |

**Sample monthly executive summary structure:**
1. Overall status (RAG: Red/Amber/Green)
2. Budget health (% spent vs. % complete)
3. Key milestone progress
4. Strategic alignment update
5. Items requiring executive attention (if any)

### Keep Informed - Communication Plan

| Element | Detail |
|---|---|
| **Frequency** | Bi-weekly |
| **Format** | Newsletter, demo invites, shared dashboard, team channel |
| **Content** | Progress updates, upcoming changes, how they are affected |
| **Preparation** | Standardized template, accessible language |
| **Follow-up** | Feedback mechanism (survey, comment thread) |
| **Escalation** | Channel for them to raise concerns that get routed appropriately |

**Sample bi-weekly newsletter structure:**
1. What happened since last update
2. What is coming next
3. How this affects your area
4. Ways to get involved or provide feedback
5. FAQ or myth-busting section

### Monitor - Communication Plan

| Element | Detail |
|---|---|
| **Frequency** | Quarterly |
| **Format** | Organizational newsletter, all-hands mention, intranet page |
| **Content** | Major milestones, organizational impact, general awareness |
| **Preparation** | Brief paragraph or slide for existing communication channels |
| **Follow-up** | None unless they initiate contact |
| **Escalation** | N/A - they should know how to reach the project team if needed |

---

## Engagement Tactics by Quadrant

### Manage Closely - Tactical Playbook

| Tactic | Frequency | Purpose |
|---|---|---|
| Weekly 1:1 meeting | Weekly | Personalized status, relationship building |
| Steering committee seat | Bi-weekly/Monthly | Governance, decision authority |
| Pre-read distribution | Before key meetings | Informed participation, faster decisions |
| Draft review invitations | As needed | Early feedback, ownership |
| Informal check-ins | Ad-hoc | Relationship maintenance, early warning |
| Joint problem-solving sessions | As issues arise | Collaborative resolution, trust building |

### Keep Satisfied - Tactical Playbook

| Tactic | Frequency | Purpose |
|---|---|---|
| Executive summary email | Monthly | Awareness without time burden |
| Milestone demo invitation | At milestones | Visibility into progress |
| Quarterly business review | Quarterly | Strategic alignment check |
| Budget/timeline alert | As needed | No surprises on financials |
| Annual strategic briefing | Annually | Long-term alignment |

### Keep Informed - Tactical Playbook

| Tactic | Frequency | Purpose |
|---|---|---|
| Project newsletter | Bi-weekly | Regular, structured updates |
| Sprint demo invitation | Per sprint | Tangible progress visibility |
| Feedback survey | Monthly | Input channel, engagement |
| FAQ document updates | As needed | Self-service information |
| Champion/ambassador program | Ongoing | Leverage their enthusiasm |

### Monitor - Tactical Playbook

| Tactic | Frequency | Purpose |
|---|---|---|
| All-hands project slide | Quarterly | General awareness |
| Intranet/wiki page | Kept current | On-demand information |
| Organizational newsletter blurb | Quarterly | Passive communication |
| Reclassification check | Quarterly | Catch shifting dynamics |

---

## Influence Mapping Techniques

### Beyond Power and Interest

While the Power/Interest Grid is the primary framework, influence mapping adds a third dimension: the ability of stakeholders to affect the attitudes and decisions of other stakeholders.

### Influence Network Mapping

1. **Identify influence relationships:** For each stakeholder, ask "Who do they influence?" and "Who influences them?"
2. **Map connections:** Draw lines between stakeholders who influence each other
3. **Identify hubs:** Stakeholders with many influence connections are network hubs
4. **Find bridges:** Stakeholders who connect otherwise disconnected groups

### Influence Assessment Criteria

| Factor | Description | Weight |
|---|---|---|
| **Network centrality** | How connected they are to other stakeholders | High |
| **Trust level** | How much others trust their judgment | High |
| **Communication reach** | Size of their communication network | Medium |
| **Track record** | History of successful influence in the organization | Medium |
| **Domain expertise** | Recognized authority in relevant areas | Medium |

### Using Influence Data

- **Identify influencer paths:** To reach a hard-to-engage stakeholder, find who influences them
- **Amplify supporters:** High-influence supporters can be project champions
- **Neutralize blockers:** Engage influencers who can address blocker concerns
- **Build coalitions:** Connect supporters to create a unified voice of support

---

## Dealing with Blockers and Resistance

### Understanding Resistance

Resistance is not inherently negative. It often signals legitimate concerns that, if addressed, improve the project. Common sources of resistance:

| Source | Example | Typical Response |
|---|---|---|
| **Fear of change** | "This will disrupt our proven processes" | Acknowledge concern, show transition plan |
| **Loss of control** | "I won't have oversight anymore" | Define their role in the new state |
| **Past experience** | "We tried this before and it failed" | Explain what is different this time |
| **Competing priorities** | "My team is already at capacity" | Address resource concerns concretely |
| **Lack of trust** | "I don't believe the timeline is realistic" | Provide evidence, invite scrutiny |
| **Political concerns** | "This project benefits their department, not mine" | Find mutual wins, reframe benefits |

### Blocker Engagement Framework

**Step 1: Diagnose**
- Schedule a 1:1 to understand their concerns (listen first)
- Identify whether resistance is rational, emotional, or political
- Determine if their concerns are about the "what" or the "how"

**Step 2: Acknowledge**
- Validate their concerns without necessarily agreeing
- Demonstrate that you have heard and understood their position
- Share where you agree and where you see things differently

**Step 3: Address**
- For rational concerns: provide data, evidence, and risk mitigation plans
- For emotional concerns: build relationship, demonstrate empathy, provide reassurance
- For political concerns: find mutual benefits, involve neutral mediators, align with organizational goals

**Step 4: Involve**
- Give them a role that addresses their concerns (review board, advisory, testing)
- Create structured opportunities for input
- Report back on how their input influenced decisions

**Step 5: Escalate (if necessary)**
- Document the concern and your attempts to address it
- Engage the executive sponsor or a trusted mutual contact
- Frame the escalation around project risk, not personality conflict

### Blocker Priority Matrix

| Power Level | Recommended Urgency |
|---|---|
| High power blocker | Address within 48 hours; escalate if unresolved in 2 weeks |
| Medium power blocker | Address within 1 week; monitor for influence spread |
| Low power blocker | Address within 2 weeks; watch for coalition building |

---

## RACI Integration with Stakeholder Mapping

### Connecting the Frameworks

The Power/Interest Grid tells you **how to communicate** with stakeholders. RACI tells you **what role they play** in specific activities. Together, they create a complete engagement model.

### Mapping Quadrants to RACI Roles

| Quadrant | Typical RACI Roles | Rationale |
|---|---|---|
| **Manage Closely** | A (Accountable), R (Responsible) | High power + high interest = active decision-making roles |
| **Keep Satisfied** | A (Accountable), I (Informed) | High power = accountability; low interest = inform only |
| **Keep Informed** | C (Consulted), I (Informed) | High interest = want input; low power = consultative role |
| **Monitor** | I (Informed) | Low power + low interest = minimal involvement |

### Integration Best Practices

1. **Start with stakeholder mapping** to understand the landscape before assigning RACI roles
2. **Validate RACI with quadrant:** If a "Monitor" stakeholder is assigned "Accountable," either the RACI or the classification needs revision
3. **Use RACI to operationalize the communication plan:** The communication plan defines the cadence; RACI defines the specific activities
4. **Review both together:** When stakeholder classifications shift, review and update RACI assignments

### Warning Signs of Misalignment

| Signal | Problem | Fix |
|---|---|---|
| "Manage Closely" stakeholder has no R or A roles | They are disengaged despite high power/interest | Assign meaningful governance or decision roles |
| "Monitor" stakeholder is Accountable for activities | Over-assignment; creates bottlenecks | Reassess classification or reduce RACI scope |
| Too many C's on one activity | Decision paralysis | Reduce to only essential consultees |
| No A assigned for critical activities | Accountability gap | Assign based on power/interest classification |

---

## Stakeholder Review Cadence

| Review Type | Frequency | Purpose |
|---|---|---|
| **Classification review** | Monthly | Reassess power/interest changes |
| **Communication effectiveness** | Bi-weekly | Check if engagement approach is working |
| **Blocker status check** | Weekly | Track progress on resistance resolution |
| **Full stakeholder audit** | Quarterly | Comprehensive reassessment of all stakeholders |
| **Post-milestone review** | At milestones | Adjust engagement for next project phase |

---

## Key Metrics for Stakeholder Engagement

| Metric | Target | Measurement |
|---|---|---|
| Stakeholder satisfaction score | > 4/5 | Periodic pulse survey |
| Communication plan adherence | > 90% | Track planned vs. actual touchpoints |
| Blocker resolution rate | 100% within 30 days | Track blocker status over time |
| Decision turnaround time | < 5 business days | Measure from request to decision |
| Escalation frequency | Decreasing trend | Count escalations per month |
| Stakeholder NPS | > 30 | Quarterly net promoter score survey |

---

**Last Updated:** March 2026
**Framework Version:** 1.0
**Companion Tool:** `scripts/stakeholder_mapper.py`
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall