CAPM Practice: Determine how to conduct stakeholder communication

Complex requirements discussions with multiple stakeholders benefit from facilitated group sessions — where ideas can be built on, conflicts surfaced and resolved in real time, and consensus built together. Email chains are too linear and lose collaborative dynamics.

**Why not A:** Email chains with all stakeholders copied are poorly suited for complex requirements discussions. Email is linear, lacks real-time interaction, and makes it difficult to resolve conflicts or build on ideas collaboratively. Important nuances get lost in long threads with many participants.

**Why not C:** Text messages are too brief and informal for complex requirements discussions. They lack the structure needed for detailed analysis, cannot support visual models or reference materials, and create fragmented conversations that are difficult to track and reference later.

**Why not D:** Individual phone calls with each stakeholder conducted over several weeks is extremely slow and prevents the cross-pollination of ideas that occurs when stakeholders interact directly. This approach also makes real-time conflict resolution impossible, as disagreements can only be discovered and addressed sequentially.