PMP · Question #435
During initiation of a new product improvement project, a project manager finds historical data showing that a similar project resulted in customers complaining of an even worse user experience compar
The correct answer is B. Define a user focus group as external stakeholders with a high influence on outcomes. To prevent a repeat of poor user experience from a previous similar project, the project manager should proactively define a user focus group as key external stakeholders. Engaging these users early ensures continuous feedback and integration of their needs throughout the project
Question
During initiation of a new product improvement project, a project manager finds historical data showing that a similar project resulted in customers complaining of an even worse user experience compared to the previous product version. How can the project manager prevent this outcome in the new project?
Options
- AHire a team of external users to perform acceptance testing on the product
- BDefine a user focus group as external stakeholders with a high influence on outcomes
- CHire a consultant to perform a benefit analysis as an input to the project charter
- DDefine a high-level risk and plan mitigation after completing the work breakdown structure (WBS)
How the community answered
(50 responses)- A14% (7)
- B76% (38)
- C6% (3)
- D4% (2)
Why each option
To prevent a repeat of poor user experience from a previous similar project, the project manager should proactively define a user focus group as key external stakeholders. Engaging these users early ensures continuous feedback and integration of their needs throughout the project, addressing the historical problem head-on.
Acceptance testing occurs towards the end of the project, and waiting until this stage to involve external users is too late to prevent fundamental user experience issues that could have been identified much earlier.
Defining a user focus group as external stakeholders with high influence ensures that customer feedback and user experience are continuously incorporated throughout the project lifecycle, starting from the initiation phase. This proactive engagement is critical to building a product that meets user expectations and prevents a recurrence of negative user experience.
Hiring a consultant for a benefit analysis focuses on justifying the project's value and is not directly aimed at addressing or preventing user experience issues through direct user feedback.
Defining a high-level risk and planning mitigation after completing the WBS means addressing the risk relatively late in the planning process, whereas proactive engagement with users is more effective at preventing user experience issues from the outset.
Concept tested: Proactive Stakeholder Engagement for Quality
Source: https://www.pmi.org/learning/library/stakeholder-engagement-user-experience-8656
Topics
Community Discussion
10
Orla P.May 17, 2026B is the right call here. The core issue is that a similar project missed the mark on user experience because users were not adequately engaged, so classifying a user focus group as high-influence external stakeholders during initiation ensures their input is captured early in the charter and stakeholder register. Option A is too narrow since it limits user involvement to acceptance testing at the end, which is exactly when you discover the user experience problems. Option D delays the risk response until after the WBS is complete, which skips the critical initiation phase where stakeholder engagement needs to be established.
Fatima Z.May 19, 2026Co-sign on B, and remember the stakeholder trick with HILO: High Influence, Low interest stakeholders get Keep Satisfied while your high-influence user focus group falls into Manage Closely because their interest is through the roof, so the charter is exactly where you stamp that engagement strategy before the WBS even breathes.
Wesley A.Apr 23, 2026I went with C on my second attempt and I am pretty confident it is the right call here. The scenario is during initiation, and the core problem is that a similar project delivered a worse user experience, which means the expected benefits were not realized or validated. A benefit analysis feeds directly into the project charter and forces the team to define measurable expected outcomes before work begins, which is exactly how you avoid repeating a failed pattern. D is the trap I fell for the first time, because it sounds responsible to log a risk, but planning mitigation only after the WBS is done is too late for an
Luis F.Apr 23, 2026Actually B is the right answer here, Wesley. The key phrase is similar past project, which points straight at lessons learned as an input to project charter development, so you would review what went wrong last time and bake those insights into initiation before you ever get to benefits analysis or risk logs.
Fatima Z.May 7, 2026B is right. Users are stakeholders, and the R in IRIS says Register them early.
Lena V.May 8, 2026Agreed on B, but the exam also wants you to distinguish between internal and external stakeholders since the engagement strategy differs, and that nuance shows up in the distractors.
Luis F.May 11, 2026Yeah B is right, you want users flagged as high-influence stakeholders early in initiation.
Orla P.May 13, 2026B is correct, and the reason it matters logistically is that high-influence stakeholders identified in initiation are the ones you loop into sign-offs and change-control decisions later, so flagging them early saves you approval bottlenecks.
Lena V.May 13, 2026A is the move. Real external users doing acceptance testing catches UX problems before launch.
Orla P.May 14, 2026B is correct here. A describes a pilot or beta rollout with external users, whereas B specifically refers to UAT, which is the formal acceptance testing phase where stakeholders validate the system meets requirements before go-live.