CAPM Practice: Determine how to conduct stakeholder communication

Storytelling — presenting scenarios, day-in-the-life narratives, and concrete examples — makes requirements emotionally real and comprehensible. Decision-makers connect with stories about user impact far more readily than abstract requirements lists.

**Why not A:** Writing fictional user stories that do not reflect real user needs contradicts the purpose of storytelling in BA work. Effective BA storytelling uses realistic scenarios grounded in actual user research and requirements to make abstract concepts tangible, not to fabricate fictional narratives disconnected from reality.

**Why not C:** Storytelling is a well-established professional communication technique used in business presentations, change management, and stakeholder engagement. Far from being inappropriate, narrative techniques help decision-makers connect emotionally with user needs and understand the real-world impact of requirements decisions.

**Why not D:** Presenting case studies from previous projects to replace current requirements discussions diverts attention from the present project's unique needs. While past experiences can inform current work, storytelling in BA communication means creating scenarios specific to the current project's users and requirements, not substituting with historical case studies.