agentleFS
zpower426zpower426/pmpowers/skills/stakeholder-management/SKILL.md

stakeholder-management

Skill0 starsChanged 7 months agoMITView on GitHub

Align expectations of different stakeholders through structured matrices and communication plans to ensure the product receives all-around support.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    High Power / Low Interest: Keep satisfied, they are potential obstacles if unhappy.

    line 20
  2. Distinctive:

    Low Power / High Interest: Keep informed, they are often the best testers and advocates.

    line 21
  3. Distinctive:

    No Surprises: If a stakeholder hears about a major negative change for the first time in a review meeting, your communication has failed.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stakeholder Management: Stakeholder Alignment Guide

The Product Manager is the balancer of interests.

Checklist

  1. Identify Stakeholders (Mapping) — R&D, Sales, Marketing, Senior Management, Customers.
  2. Apply Power/Interest Grid — Identify who needs to be managed closely versus who just needs to be kept informed.
  3. Develop Communication Strategy — Adopt different communication frequencies and granularities for different roles.
  4. Get Early Buy-in — Conduct one-on-one "socializing" before formal meetings.

Core Framework: Power/Interest Grid

  • High Power / High Interest: Key players, must be deeply involved throughout the process.
  • High Power / Low Interest: Keep satisfied, they are potential obstacles if unhappy.
  • Low Power / High Interest: Keep informed, they are often the best testers and advocates.
  • Low Power / Low Interest: Monitor only, avoid wasting excessive energy on them.

Expert Principles

  • No Surprises: If a stakeholder hears about a major negative change for the first time in a review meeting, your communication has failed.
  • Interest Exchange: Understand the other party's KPIs. They will only support you if you help them achieve their goals.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.