Stakeholder Map

What Is This?

Overview

The Stakeholder Map skill helps project managers, product owners, and team leads build a structured stakeholder map using a Power/Interest grid. It takes a list of stakeholders and their attributes, places each one into the appropriate quadrant, and generates a tailored communication plan for each group. The output gives teams a clear picture of who needs what level of attention and how to engage them effectively throughout a project lifecycle.

This skill is built around the classic two-axis framework where Power represents a stakeholder's ability to influence project outcomes, and Interest represents how much they care about those outcomes. By combining these two dimensions, the skill produces four distinct groups, each requiring a different engagement strategy. The generated communication plan specifies frequency, channel, tone, and key messages for each quadrant.

The skill is part of the Happycapy PM Skills collection and is designed to work within AI-assisted project management workflows. It accepts structured input describing stakeholders and returns a formatted map with actionable communication guidance, reducing the time teams spend on stakeholder analysis from hours to minutes.

Who Should Use This

• Project managers preparing for a product launch or major initiative who need a fast, structured way to organize stakeholder relationships
• Product owners aligning cross-functional teams across engineering, design, marketing, and operations
• Program managers overseeing multiple workstreams who need consistent stakeholder engagement across teams
• Consultants and agency leads who onboard new clients and need to quickly map decision-makers and influencers
• Scrum masters or agile coaches facilitating sprint reviews and needing to identify the right audience for each ceremony
• Business analysts gathering requirements who need to prioritize which stakeholders to interview first

Why Use It?

Problems It Solves

• Teams often treat all stakeholders the same, sending identical updates to executives and end users alike, which wastes time and creates noise
• Without a structured map, high-power stakeholders get overlooked until they block a project at a critical moment
• Communication plans are frequently created ad hoc, leading to inconsistent messaging and missed touchpoints
• Cross-functional teams lack a shared reference for who owns which stakeholder relationships, causing duplication or gaps
• New project managers inherit projects without clear documentation of stakeholder dynamics, slowing their ramp-up time

Core Highlights

• Generates a Power/Interest grid with stakeholders placed in one of four quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor
• Produces a communication plan with recommended frequency, channel, and message type per quadrant
• Accepts plain-language stakeholder descriptions and converts them into structured output
• Supports iterative refinement, allowing teams to add or update stakeholders as the project evolves
• Works across industries and project types, from software launches to organizational change initiatives
• Integrates into existing project documentation workflows by outputting clean markdown or structured text
• Reduces stakeholder analysis time significantly compared to manual methods

How to Use It?

Basic Usage

Invoke the skill by providing a list of stakeholders with their names, roles, and a brief description of their relationship to the project.

Skill: stakeholder-map

Stakeholders:
- Sarah Chen, VP of Engineering, approves technical architecture decisions
- Marcus Webb, End User Representative, uses the product daily
- Dana Okafor, Legal Counsel, reviews compliance requirements
- Tom Reyes, Marketing Director, owns the go-to-market plan

The skill processes each entry, assigns a Power and Interest score, places the stakeholder in the appropriate quadrant, and returns a communication plan.

Specific Scenarios

For a product launch, run the skill two weeks before kickoff to identify which executives need weekly briefings versus which teams need only milestone updates. For a cross-functional alignment effort, use the output to assign stakeholder owners across your team so no relationship is managed by a single point of failure.

Real-World Examples

A fintech team used this skill before a regulatory audit to identify that their compliance officer was high-power but low-interest, requiring concise, infrequent updates rather than detailed sprint reports. A SaaS company used it during a platform migration to discover that their largest enterprise customer contact had high interest but low power, shifting their strategy from executive briefings to detailed technical documentation.

Important Notes

Requirements

• A list of at least three to five stakeholders with names, roles, and a brief description of their project relationship
• Basic understanding of the project scope and objectives to accurately assess power and interest levels
• Access to an AI assistant or platform that supports the Happycapy PM Skills collection
• Willingness to review and validate the generated quadrant placements, as automated scoring benefits from human judgment