Stakeholder Engagement and Communication
This domain tests how you identify, analyse, and engage stakeholders so decisions and feedback flow at the speed of delivery. Expect power/interest mapping, communication cadence, information radiators, decision rights, conflict, and remote or hybrid engagement.
Core rules
- Stakeholders are not a distribution list. Map influence, interest, and impact, then choose engagement style.
- Communication is a feedback loop, not a status broadcast. Prefer two-way, frequent, and visual channels for delivery teams.
- Match cadence and detail to the audience: sponsors need outcome and risk; regulators need evidence and traceability; users need working software.
- Information radiators such as burn-up charts, cumulative flow diagrams, risk boards, and decision logs create pull; they do not replace conversation.
- Surface disagreement early. Conflict about work is healthy; unresolved conflict becomes a delivery risk.
Worked example
A regulator has high power and high interest but cannot attend daily reviews. A product owner proposes inviting them to stand-ups. Reasoning: that is poor fit. High power and interest do not mean high-frequency operational involvement. Better: a monthly compliance review with a pre-read evidence pack, a named contact, a decision log, and a release-readiness checklist. The team keeps daily feedback with users and business owners. Engagement is tailored to authority, need, and risk, not to one cadence for everyone.
Traps
Communicating only with the sponsor; treating a stakeholder map as a one-time artefact; over-relying on email; confusing a status report with engagement; inviting everyone to every ceremony; ignoring quiet stakeholders who hold veto power.