Practice vocabulary for managing difficult stakeholders: conflicting priorities, HiPPO dynamics, de-escalation, redirecting off-topic demands, and alignment before sprint.
0 / 5 completed
1 / 5
A PM says 'the stakeholder has conflicting priorities'. What does this mean in practice?
Conflicting priorities means a stakeholder is asking for multiple outcomes that compete for the same resources, time, or budget — for example wanting a new feature delivered in two weeks while also demanding zero technical debt and full test coverage. The PM must facilitate a conversation to force a prioritisation choice.
2 / 5
What is a 'HiPPO' in stakeholder management?
HiPPO stands for Highest Paid Person's Opinion. It describes the dynamic where the most senior person in the room drives decisions based on gut feeling rather than data or team expertise. Good PMs and tech leads learn to redirect HiPPO influence by presenting evidence, framing options, and facilitating structured decision-making.
3 / 5
A meeting is getting heated. The PM uses 'de-escalation vocabulary'. Which phrase is an example of de-escalation?
De-escalation vocabulary acknowledges the stakeholder's emotion and concern without dismissing it, then redirects toward a constructive path. Phrases like 'I understand', 'let's capture that', and 'let's address it properly' reduce tension while keeping the conversation productive.
4 / 5
A stakeholder keeps raising off-topic demands during sprint planning. How should the PO redirect them?
The correct technique is to acknowledge the demand (so the stakeholder feels heard), log it in the backlog, and explain it will be prioritised in the next backlog refinement. This prevents scope creep during planning while ensuring the stakeholder's request is not lost.
5 / 5
The team says 'we need alignment before the next sprint'. What does alignment mean here?
Alignment means all key stakeholders share the same understanding of what will be built, why it is the priority, and what success looks like. Without alignment before sprint planning, the team risks building the wrong thing or facing mid-sprint scope changes from stakeholders who weren't consulted.