stakeholder-mapping

Prioritize stakeholders using Power-Interest and Impact-Power grids with engagement strategies.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill stakeholder-mapping-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-mapping
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/1-exploration/stakeholder-mapping
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill stakeholder-mapping-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After identifying stakeholders, teams often struggle to decide who deserves deep engagement versus light monitoring, and they systematically overlook high-impact, low-power groups whose voices never reach roadmap decisions. ## Core Features & Use Cases - Dual Grid Analysis: Runs Power × Interest and Impact × Power 2x2 grids independently, then compares placements to reveal blind spots and misaligned engagement. - Quadrant-Based Engagement Strategies: Assigns per-quadrant strategies (manage closely, keep satisfied, keep informed, monitor) and plans deliberate quadrant migration with named owners. - Use Case: Before a quarterly roadmap review, map executives, engineering leads, legal, support teams, and customers onto both grids to discover that customer support is under-engaged despite bearing high product risk, then recruit them into UAT and launch readiness criteria. ## Quick Start Map the stakeholders for my platform migration initiative onto Power-Interest and Impact-Power grids and recommend an engagement strategy for each.

Frequently Asked Questions about stakeholder-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize stakeholders for a product initiative?▼

Place each stakeholder on a Power × Interest grid to assign engagement strategies: manage closely, keep satisfied, keep informed, or monitor. Then run an Impact × Power grid independently and compare placements to find stakeholders you are under-engaging relative to how much the product affects them.

What is the difference between a Power-Interest grid and an Impact-Power grid?▼

Power × Interest answers how to engage each stakeholder based on influence and attention. Impact × Power answers who bears the consequences but lacks organizational voice. Running both and comparing them reveals blind spots that either grid alone misses.

When should I run stakeholder mapping in a product workflow?▼

Run it after stakeholder identification has produced the full named list, and before per-stakeholder engagement planning. Re-run it at quarterly review cycles or after reorgs, since authority and influence shift between quadrants over time.

How do I engage high-impact low-power stakeholders?▼

Elevate them with concrete actions rather than passive access: recruit them into discovery research and usability testing, give them a named role in requirements review, and include them in launch readiness criteria. Naming them on a map without changing engagement is the most common failure mode.

What are common mistakes in stakeholder mapping?▼

Common pitfalls include running only one grid, conflating org-chart seniority with actual power, treating placements as permanent, quantifying rankings within quadrants, and stopping at placement without defining migration actions and owners.