Stakeholder Analysis

Identify and map project stakeholders using power/interest grids and RACI matrices.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Danhvb/my-ba-skills --skill stakeholder-analysis-danhvb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Stakeholder Analysis
Source: https://github.com/Danhvb/my-ba-skills/tree/main/multi-agent-ba/.agent/skills/senior-ba/stakeholder-analysis
Command: npx skills add https://github.com/Danhvb/my-ba-skills --skill stakeholder-analysis-danhvb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stakeholder analysis helps project teams identify, prioritize, and manage people and groups who influence or are affected by a project, reducing surprises and improving alignment.

Core Features & Use Cases

  • Stakeholder identification and categorization using power/interest grids
  • RACI mapping to clarify roles and responsibilities
  • Communication planning to tailor messages and cadence
  • Real-world use: planning a new system rollout with cross-functional teams

Quick Start

Identify key stakeholders from sponsors, users, IT, and governance, then draft a stakeholder register and an initial communication plan.

Frequently Asked Questions about Stakeholder Analysis

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

FAQPage Schema
What is stakeholder analysis and when do I need a power interest grid?

Stakeholder analysis identifies and prioritizes people or groups influencing a project to reduce surprises and improve alignment. You need a power interest grid during project initiation, requirements gathering, and change management to effectively map engagement levels.

How do I map stakeholders and create a communication plan for a new system rollout?

To map stakeholders for a system rollout, identify key sponsors, users, IT, and governance members, then draft a stakeholder register. Use this input to create a communication plan that tailors messages and cadence to improve cross-functional alignment.

Can I use a RACI matrix for stakeholder management in IT and operations projects?

Yes, you can use a RACI matrix for stakeholder management in IT and operations projects to clarify roles and responsibilities. It maps specific tasks to stakeholders, ensuring clear accountability and reducing engagement risks across cross-functional teams.

What's the best way to categorize stakeholders for ongoing project governance?

The best way to categorize stakeholders for ongoing governance is using a power interest grid combined with a stakeholder register. This approach prioritizes influence and impact, enabling tailored communication planning and effective risk management throughout the project lifecycle.

Why does stakeholder communication planning fail without a stakeholder register?

Stakeholder communication planning fails without a stakeholder register because the register provides the foundational identification and categorization of key sponsors, users, and IT members. Without it, messages lack proper targeting, leading to misalignment and governance risks.

Does this stakeholder analysis approach work for cross-functional product teams?

Yes, this stakeholder analysis approach works for cross-functional product teams by providing flexible matrices and templates. It maps engagement and RACI responsibilities across diverse sponsors, users, and governance groups to improve alignment and manage risks.