PMP · Question #523
A distributed protect team wants to use the common ground principle to ensure that they have a common understanding of the scope. The team asks the protect lead to set up a workshop. What should the p
The correct answer is D. Provide the participants with specific instructions and sot the expectations. For a distributed team workshop aimed at establishing a common understanding of scope, the project lead should provide participants with specific instructions and set clear expectations. This ensures everyone is prepared and aligned on the workshop's purpose and how to achieve co
Question
A distributed protect team wants to use the common ground principle to ensure that they have a common understanding of the scope. The team asks the protect lead to set up a workshop. What should the project lead do?
Options
- AAsk the senior members of the development team to elaborate on the scope in detail
- BInvite participants to the workshop with sufficient lead time to prepare
- CReduce the number of participants to ensure that consensus is reached easier
- DProvide the participants with specific instructions and sot the expectations
How the community answered
(24 responses)- A13% (3)
- B4% (1)
- C4% (1)
- D79% (19)
Why each option
For a distributed team workshop aimed at establishing a common understanding of scope, the project lead should provide participants with specific instructions and set clear expectations. This ensures everyone is prepared and aligned on the workshop's purpose and how to achieve common ground.
While senior members' input is valuable, the workshop is for the *entire team* to gain common understanding; relying solely on senior members to elaborate doesn't facilitate common ground across all participants.
Inviting participants with sufficient lead time is good practice for any meeting, but it's a logistical step and doesn't directly address the *effectiveness* of the common ground principle itself; providing specific instructions and expectations is more impactful for workshop quality.
Reducing the number of participants might make consensus *seem* easier, but it risks excluding key perspectives and undermining the goal of achieving common understanding across the *entire team* or relevant stakeholders.
For a workshop, especially with a distributed team aiming for a common understanding (the common ground principle), clear preparation is crucial. Providing specific instructions on what to review, what to bring, and what the expected outcomes are ensures that all participants come prepared, can contribute effectively, and the workshop achieves its goal of aligning on scope, minimizing wasted time and maximizing productive discussion.
Concept tested: Facilitating common understanding in distributed teams
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
9
Luis F.Jul 5, 2026D is correct because the common ground principle requires setting clear expectations and giving specific instructions so everyone walks into the workshop on the same page about the scope. I almost picked B since lead time matters, but the question is really about what the lead does to establish common ground, not just logistics.
Orla P.Jul 7, 2026Agree on D, and to add a logistics angle, that common ground setup also means sending the agenda and any pre-reads far enough ahead that people actually have time to review them, not just a day before.
Orla P.Jul 3, 2026D is correct here because the common ground principle is about making sure everyone shares the same understanding, and the project lead facilitating that process with clear expectations is exactly what the exam is looking for. I have seen B trip people up since lead time matters, but does anyone know if PMI treats the facilitator setting expectations as more important than the logistics of the invite itself?
Lena V.Jul 5, 2026D is correct. Common ground requires setting clear expectations and giving specific instructions upfront.
Luis F.Jul 7, 2026Yeah D is right but I'd also add that documenting those expectations somewhere accessible is huge, because clear instructions don't help if nobody can find them later.
Viktor S.Jun 22, 2026D is right because common ground means shared understanding, not just shared documents, so setting clear expectations and instructions drives that. B is the tempting trap since lead time sounds courteous, but it skips the actual facilitation step that makes the workshop worth holding.
Zlatan X.Jun 24, 2026Agreed on D, Viktor, and the trap framing on B is solid, but I would push the rationale one level higher: common ground at the program level is about stakeholder alignment across components, which is why facilitated expectations matter more than artifacts.
Zlatan X.Jul 5, 2026Went with C on this one. The common ground principle breaks down fast on distributed teams because too many voices create fragmented understanding rather than shared alignment. By reducing the participant count, the lead creates the conditions where consensus is actually achievable and the workshop produces a coherent scope statement instead of a watered-down compromise. You can always cascade the agreed-upon understanding outward to the broader team afterward through governance channels. Consensus reachability is the real constraint here, not inclusivity.
Viktor S.Jul 5, 2026D is correct, and the reason is the opposite of what you described. The common ground principle depends on having the right voices in the room so that shared understanding reflects actual stakeholder needs, not a smaller group's opinion cascaded downward after the fact.