CAPM Practice: Determine how to conduct stakeholder communication

All feedback — positive and negative — is valuable. Negative feedback often surfaces important issues. BAs should probe for specifics, separate the concern from the emotion, assess its validity, and either adjust requirements or explain the reasoning for not doing so.

**Why not A:** Dismissing negative feedback because it contradicts the majority is unprofessional and risky. Minority viewpoints often reveal blind spots or edge cases that the majority has overlooked. Ignoring them can lead to requirements gaps and stakeholder disengagement.

**Why not B:** Deflecting negative feedback to the project sponsor abdicates the BA's facilitation responsibility. Handling stakeholder concerns constructively is a core BA competency, and escalating routine feedback undermines the BA's role and credibility.

**Why not D:** Documenting negative feedback separately and restricting its visibility creates information silos. All feedback should be transparently addressed with relevant stakeholders to maintain trust and ensure concerns are properly resolved.