PMP · Question #483
A project manager for a large multiyear industrial project has a project with diversified stakeholders from various geographical areas. Recently, the project manager encountered an issue with stakehol
The correct answer is A. Five whys C. Ishikawa diagrams. To determine the root causes of ineffective stakeholder engagement, the project manager should employ specific analytical tools designed for cause-and-effect investigation.
Question
Options
- AFive whys
- BCommunications management plan
- CIshikawa diagrams
- DIssue log
- EOpen-space meetings
How the community answered
(49 responses)- A82% (40)
- B10% (5)
- D4% (2)
- E4% (2)
Why each option
To determine the root causes of ineffective stakeholder engagement, the project manager should employ specific analytical tools designed for cause-and-effect investigation.
The Five Whys is an iterative interrogative technique used to explore the cause-and-effect relationships underlying a particular problem. By repeatedly asking "Why?", the project manager can delve deeper into the symptoms of poor engagement to uncover its root cause.
A communications management plan outlines how communication will occur, but it is not a diagnostic tool for determining the underlying reasons for communication or engagement failures.
Ishikawa diagrams, also known as fishbone or cause-and-effect diagrams, visually categorize potential causes of a problem to identify its root causes. This tool allows the project manager to structure a brainstorming session around different categories (e.g., people, process, environment) contributing to the engagement issue.
An issue log simply records issues that have occurred; it does not inherently provide a methodology or tool for analyzing the root causes of those issues.
Open-space meetings are a format for self-organizing discussions, not a specific tool for root cause analysis of engagement problems.
Concept tested: Root cause analysis techniques
Source: https://www.pmi.org/learning/library/root-cause-analysis-project-management-6537
Topics
Community Discussion
6
Nina C.Nov 1, 2025A and C. Five whys and Ishikawa diagrams are root cause analysis tools, which is exactly what you need when the question asks for the underlying reason. I got tripped up initially because issue log sounded plausible, but re-read the stem: it is asking why the engagement is not working, not where to track the problem.
Yuki V.Oct 21, 2025Confirmed A and C on my exam. Both are root cause analysis tools, which is exactly what the question asks for.
Samuel O.Nov 17, 2025Took this one last week and A plus C is correct. Five whys gets you down to the real driver behind why engagement is falling flat instead of just treating symptoms, and Ishikawa diagrams lay out all the contributing factors in a visual way that is especially helpful when you are dealing with stakeholders spread across multiple regions. I have used fishbone diagrams on job sites for years when something is off with a client relationship and it always surfaces root causes nobody initially considered. B and D are operational documents, not root cause analysis tools, so they do not fit what the question is really asking. Has
Wesley A.Nov 19, 2025Agree on A and C, and I would add one thing from my first attempt: the question stem said "structured" analysis, which is the word that nudges Ishikawa ahead of Five Whys if you ever see them split into separate answer choices.
Wesley A.Nov 10, 2025Failed this one on my first attempt because I picked the communications management plan and the issue log, since both sounded like the right place to look when engagement goes sideways. But the key phrase is "determine the underlying reason," which is root cause analysis territory, not documentation or planning artifacts. Five whys (A) and Ishikawa diagrams (C) are specifically designed to dig into why a problem exists rather than just logging it or adjusting how you communicate. The issue log and communications plan help you track and manage the problem, but they do not tell you why it happened in the first place
Samuel O.Nov 11, 2025Spot on, Wesley, and I would add that in practice the issue log often contains the clues that point you toward doing the root cause analysis in the first place, so it is not either or, it is sequential.