CAPM Practice: Determine how to conduct stakeholder communication

Vague feedback often reflects discomfort with direct disagreement (common in high-context cultures) or uncertainty about what's being asked. BAs can help by using specific scenarios, prototypes, or comparative evaluations that make it easier for stakeholders to articulate preferences without feeling confrontational.

**Why not B:** Requiring all stakeholders to use the same direct feedback style ignores cultural norms and individual communication preferences. Imposing a single style can alienate stakeholders who are uncomfortable with direct disagreement, reducing their participation and the quality of feedback gathered.

**Why not C:** Involving only the direct communicators in requirements validation excludes valuable perspectives from stakeholders whose indirect style may reflect cultural background rather than lack of insight. Their input is essential for comprehensive requirements that serve all user groups.

**Why not D:** Ignoring vague feedback and relying only on direct feedback risks missing important requirements and concerns. Vague feedback often contains signals about unstated needs or disagreements that, when properly explored with the right elicitation techniques, yield critical requirements insights.