CAPM Practice: Determine how to conduct stakeholder communication

BAs should escalate when communication failures create project risk that they cannot resolve at their level — such as a key decision-maker who is persistently unavailable, preventing critical requirements from being confirmed.

**Why not A:** Waiting for formal written complaints before escalating allows communication problems to fester and grow. Critical stakeholder unresponsiveness can block requirements decisions and introduce project risk long before a formal complaint is filed. BAs should escalate when risk is evident, not only after formal grievances.

**Why not B:** Escalating after every meeting would overwhelm leadership with unnecessary information and undermine the BA's credibility. Escalation should be reserved for situations where the BA cannot resolve communication failures independently and the issue poses genuine risk to requirements quality or project decisions.

**Why not D:** Escalating immediately at the first sign of any communication difficulty is premature. Minor communication issues are common and often resolvable by the BA through alternative approaches, follow-up, or adapted techniques. Escalation should occur when the BA has exhausted their options and the issue creates project risk.