PMP · Question #63
A project manager is developing the stakeholder register and is having trouble understanding the motivation of some of the stakeholders. What should the project manager do to get this information?
The correct answer is D. Organize a one-on-one conversation with each stakeholder. To understand stakeholders' motivations, the project manager should hold individual conversations with them, as this allows for direct, in-depth clarification and relationship building.
Question
A project manager is developing the stakeholder register and is having trouble understanding the motivation of some of the stakeholders. What should the project manager do to get this information?
Options
- AIdentify each stakeholder's motivations from the business case.
- BRequest stakeholders articulate their motivations at the kick-off meeting.
- CEmail project objectives to all stakeholders and ask for endorsement.
- DOrganize a one-on-one conversation with each stakeholder.
How the community answered
(19 responses)- A5% (1)
- B5% (1)
- C16% (3)
- D74% (14)
Why each option
To understand stakeholders' motivations, the project manager should hold individual conversations with them, as this allows for direct, in-depth clarification and relationship building.
The business case provides high-level project justification and objectives, but it typically doesn't detail individual stakeholder motivations.
Requesting stakeholders articulate motivations in a group setting like a kick-off meeting might not yield candid or complete responses due to group dynamics or time constraints.
Emailing objectives and asking for endorsement is a passive approach that won't reveal underlying motivations or allow for clarifying questions.
Understanding stakeholder motivations often requires personal interaction to uncover their true interests, expectations, and potential impact on the project. One-on-one conversations provide a dedicated, private setting where stakeholders are more likely to express their individual concerns, priorities, and underlying motivations, allowing the project manager to gather detailed and nuanced information.
Concept tested: Identifying stakeholder motivations
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/stakeholder-engagement
Topics
Community Discussion
5Confirmed D on my PMP attempt last month. The stakeholder register is built early, before you have a kickoff or a fully baked set of project objectives, so you are not relying on group settings or documents to read minds. A direct, private conversation is the only reliable way to draw out individual motivations and concerns, especially from quieter or resistant stakeholders. Options A, B, and C assume the info is already written down or will be volunteered in a group setting, which rarely happens in practice.
Leaned toward B first since kickoff seemed like a natural place to surface motivations. But the PM is still building the stakeholder register, so you need that info before kickoff, which makes D the right call.
Good catch on the sequencing, though the real giveaway is that identifying motivations is a stakeholder register task, not a kickoff activity.
D is right but B is tempting, direct one-on-one gets real motivations.
Agree on D but B wastes time when you are already cramming after a 10 hour shift, save the heart-to-heart for the survey comments.