PMP Practice: Root Cause Analysis of Vision Misunderstandings
Question 16 of 20 in Develop a Common Vision
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Facilitate a workshop where the team maps out the full product lifecycle together, identifying which components require predictive approaches due to regulatory constraints and which can use adaptive methods, then co-create success criteria that reflect both compliance and user value
Explanation
The root cause of the misunderstanding is that team members are viewing methodology as an all-or-nothing choice rather than understanding how different approaches serve different project needs within the same initiative. In a hybrid environment, developing a common vision requires helping the team see how predictive and adaptive approaches can coexist purposefully. By facilitating a collaborative mapping session, Koa enables the team to understand why certain components need sequential control (regulatory compliance for hardware) while others benefit from iteration (user experience for software). Co-creating success criteria that honor both compliance and user value helps everyone see how their work contributes to the overall product vision. The team has already demonstrated siloed thinking, so bringing them together to visualize the integrated delivery approach directly addresses the fragmentation. The sponsor's request to align everyone indicates Koa has the authority and responsibility to facilitate this alignment rather than escalate or divide the teams further.
**Why not B:** Forcing a single methodology ignores the legitimate need for different approaches in different parts of the project. Regulatory hardware genuinely requires predictive control, while user-facing software benefits from adaptive methods. This would either compromise compliance or sacrifice user responsiveness unnecessarily, and doesn't help the team understand why the hybrid approach serves the vision.
**Why not C:** Creating separate visions defeats the purpose of developing a common vision and would reinforce the silos that are already causing problems. The hardware and software must integrate into a single medical device product, so the teams need a shared understanding of how their work connects. Independent delivery schedules could create integration risks and compliance gaps.
**Why not D:** This presents a false choice and inappropriately escalates a problem the project manager should resolve. Both regulatory compliance and user responsiveness are necessary for a successful medical device product—they're not competing priorities requiring executive arbitration. Escalating also delays resolution and signals to the team that the PM cannot facilitate alignment, which undermines Koa's leadership.
Key Concept
This question covers Root Cause Analysis of Vision Misunderstandings under Develop a Common Vision (People).
This is 1 of 100 free PMP questions
Unlock 6,300+ PMP practice questions with detailed explanations, progress tracking, and exam readiness prediction.
Unlock All Questions