T04: Engage Stakeholders | Domain 2

📖 Stakeholder Identification & Analysis

🇺🇸 English

Identify stakeholders EARLY — anyone who can affect or be affected by the project. Late identification = late discovery of conflicting interests.

Stakeholder Register: Name, role, contact info, requirements/expectations, influence level, engagement level (current vs desired).

Engagement levels:

Unaware → Resistant → Neutral → Supportive → Leading (target for key stakeholders)

Reference: PMI — Stakeholder Management

🇻🇳 Tiếng Việt

Xác định stakeholders SỚM — bất kỳ ai có thể ảnh hưởng hoặc bị ảnh hưởng bởi dự án. Xác định muộn = phát hiện muộn các lợi ích xung đột.

Mức độ tham gia: Không biết → Kháng cự → Trung lập → Ủng hộ → Dẫn dắt (mục tiêu cho stakeholders chính)

📊 Power/Interest Grid

Quadrant	Power	Interest	Strategy	Example
Manage Closely	High	High	Frequent, detailed communication; involve in decisions	Project Sponsor, Bank Partner A CEO
Keep Satisfied	High	Low	Regular updates; keep them informed of major decisions	CFO, Legal Counsel
Keep Informed	Low	High	Regular communication; involve in appropriate activities	End users, QA team
Monitor	Low	Low	Minimal communication; periodic updates	General public, distant departments

🎯

Exam Tips — Stakeholder Engagement

Identify stakeholders early — this is always best practice
Negative stakeholders (those opposed to project) must be engaged too — understand and address their concerns
Goal: move stakeholders from Resistant/Neutral → Supportive
Stakeholder engagement plan is SEPARATE from communication plan but related
In Agile: Product Owner is primary stakeholder representative; demos involve stakeholders every sprint
Sponsor = highest-level internal stakeholder; resolves issues beyond PM's authority

🗂️ Stakeholder Engagement Plan

Stakeholder Engagement Plan — Project Alpha, FinTech Company X

── IDENTIFICATION APPROACH ────────────────────────── Initial stakeholder register created in Week 1 (kickoff workshop + PM interviews) Register reviewed and updated at each phase gate and upon any major scope change ── ANALYSIS ───────────────────────────────────────── Power/Interest grid mapping completed at project start Grid updated quarterly (or when stakeholder circumstances change) Current vs Desired engagement levels tracked per stakeholder ── ENGAGEMENT STRATEGIES BY QUADRANT ─────────────── Manage Closely (High Power / High Interest) → Weekly touchpoints (1:1 or call); involve in key decisions; share risks early Keep Satisfied (High Power / Low Interest) → Monthly updates on major milestones; alert immediately on critical risks Keep Informed (Low Power / High Interest) → Sprint reviews and demos; regular status emails; feedback channels open Monitor (Low Power / Low Interest) → Quarterly newsletter or project summary; no action unless status changes ── RESISTANCE MANAGEMENT ──────────────────────────── 1. Identify root cause of resistance (fear, loss of control, lack of info, past experience) 2. Address concerns early — schedule 1:1, listen without defending 3. Involve resistant stakeholders in relevant decisions where possible 4. Track engagement level change: Resistant → Neutral → Supportive 5. Escalate to sponsor only if direct engagement fails

🔧 Stakeholder Register Template

Name	Role	Expectations	Influence	Interest	Current Engagement	Desired	Strategy
CTO	Sponsor	On-time delivery, scalable arch	Very High	High	Supportive	Leading	Weekly 1:1, involve in tech decisions
Partner Tech Lead (A)	External partner	Stable API, SLA compliance	High	High	Neutral	Supportive	Bi-weekly call, early access to API docs
Compliance Officer	Internal gatekeeper	All regulatory requirements met	High	Medium	Resistant	Supportive	Involve early in requirements, share compliance checklist
End Users (Loan Officers)	Users	Easy-to-use interface, fast system	Low	High	Neutral	Supportive	User testing sessions, feedback incorporated

💼 Thực chiến / Scenario

🏢

FinTech Company X — Managing Resistant Compliance Stakeholder

Tình huống: Compliance Officer của FinTech Company X resistant với Project Alpha vì họ lo ngại về data privacy compliance (PII handling) trong new architecture. Họ chưa review requirements nhưng đã gửi email "disapproval" lên CTO.

PM approach: Meet directly (không defensive) với Compliance Officer. Listen to their specific concerns về PII encryption, audit logging, data retention. Document requirements họ cần. Incorporate compliance requirements vào sprint backlog NGAY (Sprint 2). Invite Compliance Officer vào sprint review để see progress.

Result: Compliance Officer moved from Resistant → Supportive khi thấy concerns được addressed seriously. Sprint 4 họ proactively helped document compliance controls — became an ally. This is stakeholder management in action.

✏️ Practice Questions

Question 1

A new stakeholder who has high influence over the project budget has been identified. They are currently unaware of the project. What is the BEST approach?

A. Add them to the distribution list for weekly status reports
B. Schedule a meeting to introduce the project, understand their expectations, and develop a tailored engagement strategy
C. Assign them to the "Monitor" category since they have low interest
D. Wait until they show interest before engaging them

✅ Answer: B — A high-influence stakeholder who is "unaware" needs proactive, personalized engagement immediately — not just adding to a mailing list. The goal is to move them from Unaware to at least Supportive. The PM should understand their expectations early to avoid surprises later. Waiting (D) risks them becoming resistant when they eventually discover the project.

Question 2

A key stakeholder who was initially supportive has become resistant after a project scope change that removed a feature important to them. What should the PM do?

A. Ignore their resistance since the CCB approved the scope change
B. Schedule a 1:1 to understand their specific concerns, explain the business rationale for the change, and explore compensating actions where possible
C. Escalate their behavior to the sponsor immediately
D. Involve them less in project activities to avoid further conflict

✅ Answer: B — A resistant stakeholder who was previously supportive signals unaddressed concerns. The PM should proactively engage — listen first, explain the rationale, and find compensating actions where possible. Ignoring resistance (A) allows it to escalate and threaten the project. Escalating immediately (C) is premature without attempting direct resolution. Involving them less (D) is the opposite of good stakeholder management and will deepen resistance.

Question 3

Which stakeholder identification mistake is MOST likely to cause project failure?

A. Identifying too many stakeholders and including them all in the register
B. Failing to identify negative stakeholders (those opposed to the project) until they create significant opposition
C. Updating the stakeholder register too frequently during the project
D. Including external stakeholders such as regulators or vendors in the register

✅ Answer: B — Negative or resistant stakeholders who are identified late are among the most common causes of project failure. By the time their opposition surfaces, they may have built alliances, influenced decisions, or created blockers that are costly to reverse. Identifying too many stakeholders (A) is a minor inefficiency. Frequent updates (C) are best practice, not a risk. Including external stakeholders (D) is correct and recommended.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs analyze stakeholder power/interest dynamics, generate tailored engagement strategies, draft stakeholder-specific communications, and identify disengaged or resistant stakeholders early.

Sample Claude Prompts

Stakeholder analysis and mapping Help me conduct a stakeholder analysis for my project. Project: [name and description] Stakeholders I've identified: [list of names/roles] Project phase: [initiation / planning / execution / close] For each stakeholder, analyze: 1. Power level (ability to impact project success/failure): High / Medium / Low 2. Interest level (how much they care about this project): High / Medium / Low 3. Current stance: Supporter / Neutral / Resistant / Unknown 4. Primary concern: [what they care most about] 5. Engagement strategy based on power/interest quadrant: - High power / High interest → Manage closely - High power / Low interest → Keep satisfied - Low power / High interest → Keep informed - Low power / Low interest → Monitor Generate a stakeholder register and engagement matrix. Also identify: Which stakeholder poses the biggest risk to project success and why?

Resistant stakeholder strategy I have a key stakeholder who is resistant to this project. I need a strategy to turn them around. Stakeholder: [role / influence level] Why they're resistant: [my best assessment — fear of change / competing priority / past bad experience / political reasons] What the resistance looks like: [specific behaviors — blocking decisions, withdrawing support, public criticism] What I've already tried: [attempts to engage] Their power in this project: [can they kill the project? delay it? reduce resources?] Generate a resistance management strategy: 1. Diagnose the true root cause of resistance (use ADKAR lens) 2. Identify what would move them from resistant to neutral (minimum goal) 3. Identify what would move them to supportive (stretch goal) 4. Tactical engagement plan: 3 specific actions in the next 30 days 5. Escalation threshold: when do I involve sponsor to manage this stakeholder?

Stakeholder engagement plan for new project I'm starting a new project with significant organizational change. Help me build a Stakeholder Engagement Plan. Project: [name, description, scale of change] Key stakeholder groups: [list] Timeline to go-live: [months] Change magnitude for each group: [High/Medium/Low impact on their work] Organizational culture: [risk-averse / change-resistant / innovative / political] Create a Stakeholder Engagement Plan with: 1. Engagement calendar (key touchpoints per stakeholder group per month) 2. Communication preferences per group (email / meetings / demos / written reports) 3. "Win" conditions — what each group needs to see to become supporters 4. Early warning indicators of disengagement 5. Champions identification and activation plan

Jira / Confluence Template

Confluence — Stakeholder Register

── CONFLUENCE: STAKEHOLDER REGISTER ───────────────────── Project: [Project Alpha] | PM: [name] | Updated: [YYYY-MM-DD] ── STAKEHOLDER PROFILES ────────────────────────────────── Name/Role: [VP Finance — Sponsor] Power / Interest: High / High → Manage closely Current stance: Supportive Primary concern: ROI and timeline — wants go-live before quarter end Communication: Weekly 15-min briefing + monthly steering deck Engagement action: Pre-brief before any CCB with scope impact Name/Role: [IT Operations Manager] Power / Interest: High / Low → Keep satisfied Current stance: Neutral (potential resistance if ops burden increases) Primary concern: System stability + support workload post-launch Communication: Bi-weekly technical update Engagement action: Include in hypercare planning; show ops runbook ── ENGAGEMENT HEALTH ───────────────────────────────────── Last engagement review: [date] | Next: [date] | At-risk stakeholders: [list]