Skip to main content
ClaudeWave
Skill5.9k repo starsupdated 5d ago

stakeholder-engagement-advisor

The Stakeholder Engagement Advisor provides tailored engagement strategies for individual priority stakeholders by diagnosing their motivations, relationship history, and concerns separately from your own objectives, then delivering a customized outreach plan. Use this skill before critical conversations, when navigating resistance, or when preparing to align relationships with high-impact stakeholders who could block or reshape your initiative.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills /tmp/stakeholder-engagement-advisor && cp -r /tmp/stakeholder-engagement-advisor/skills/stakeholder-engagement-advisor ~/.claude/skills/stakeholder-engagement-advisor
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Stakeholder Engagement Advisor

## Purpose

Plan how to engage a specific stakeholder — before a critical conversation, milestone, or relationship repair. Generic stakeholder engagement fails because it treats all stakeholders with the same message, medium, and cadence. An executive sponsor who privately disagrees with your direction needs different handling than an impacted frontline user who's never been consulted. This skill diagnoses the specific stakeholder relationship you're managing and delivers a tailored engagement approach that accounts for both sides of the conversation — their motivations and yours.

Run this skill once per priority stakeholder. Priority stakeholders are those in the "manage closely" quadrant from stakeholder-mapping, every Q1 (high-impact, low-power) stakeholder regardless of Power × Interest placement, and anyone who has the potential to block, delay, or fundamentally reshape your initiative.

## Key Concepts

**Stakeholder Motivations vs. Your Motivations** — The most common engagement failure is planning only your side of the conversation. Effective stakeholder engagement requires mapping what the stakeholder needs, wants, and fears — separately from what you need from them. Where these overlap, you have an alignment path. Where they diverge, you have a negotiation to prepare for.

**Proxy** — A credible representative who speaks for or stands in for a stakeholder who is hard to reach, part of a large group, or represents a community rather than an individual. A good proxy is validated: they understand and can speak for the people they represent. A convenient proxy — the person who shows up to meetings — often cannot. Name the proxy explicitly and verify their representativeness before relying on their input.

**Analysis Before Action** — The engagement plan has two phases: diagnosis (who is this person, what drives them, what is the relationship history?) and planning (what will you say, through which medium, with what desired outcome?). Teams that skip directly to planning produce tactics without foundation — a message crafted for the wrong motivation, a medium that signals the wrong level of importance, an ask that misreads what the stakeholder actually controls.

**Equity Lens in Engagement** — High-impact, low-power stakeholders (Q1 from stakeholder-mapping) require proactive engagement design, not an open-door policy. An open door serves the people who already know they have a seat at the table. Q1 stakeholders typically need you to go to them: structured research recruitment, named roles in review processes, and deliberate inclusion in decisions that affect them.

**Next Action Commitment** — Every engagement plan must end with a named next action: who does what, by when, through which medium, with what key message and desired outcome. Engagement plans without this commitment are intentions, not plans. The next action is the only part that actually moves the relationship forward.

**Engagement Context** — The situational frame around the engagement matters as much as the stakeholder profile. Preparing for a first contact requires different framing than recovering from a conflict, securing buy-in before a launch, or maintaining an already-aligned relationship. The context shapes the message, the medium, and the desired outcome.

## Application

This skill runs as a guided conversation. Answer each question; the advisor synthesizes your inputs and delivers a tailored engagement plan structured around three decision points:

1. **Stakeholder profile** — who they are and what role they play
2. **Power and impact** — how much authority they hold vs. how much they're affected
3. **Engagement context** — the situation you're preparing for

After all three, you receive a set of numbered engagement approaches to choose from, then a specific action plan.

---

**Opening**

> "We're going to plan your engagement with a specific stakeholder. I'll ask three questions about them and the situation, then deliver a tailored approach — message framing, medium, cadence, and your next action.
>
> Who is this stakeholder? Give me their name, role, and one sentence on the history of your relationship with them so far."

---

**Question 1 of 3 — Stakeholder profile**

> "Which of the following best describes this stakeholder?
>
> 1. **Executive sponsor or senior decision-maker** — holds formal authority over scope, budget, or go/no-go; your initiative needs their active support or at minimum their absence of resistance
> 2. **Cross-functional peer or partner** — adjacent team lead whose capacity, systems, or process your initiative touches; peer relationship, not a reporting one
> 3. **End user or community representative** — the person or group who will live with the product's outcomes daily; may have limited org power but high stakes in the result
> 4. **Skeptic or potential blocker** — has publicly or privately expressed resistance, doubt, or competing priorities; could slow or derail the initiative if not addressed
> 5. **Newly identified stakeholder** — discovered mid-initiative; relationship history is thin or nonexistent"

*Based on the answer, tailor the next question and the eventual recommendation.*

---

**Question 2 of 3 — Power and impact profile**

> "Looking at this stakeholder's position from your stakeholder mapping — or your best read if you haven't mapped formally yet:
>
> 1. **High power, high impact** — they can shape the initiative AND they're significantly affected by its outcome (e.g., the VP whose team's workflow changes and who controls the budget)
> 2. **High power, low impact** — they control resources or approval but aren't significantly affected day-to-day (e.g., a CFO approving budget for a product they'll never use)
> 3. **Low power, high impact** — they're directly affected by the product's outcome but have limited org authority to shape it (e.g., frontline users, support agents, end communities)
> 4. **Low power, low impact** — limit