What principle is an analyst applying when using a storyboard during a Planning Workshop?

Using a storyboard during a Planning Workshop aligns closely with the principle of getting real using examples. This principle emphasizes the importance of illustrating ideas and concepts through tangible examples that stakeholders can understand and relate to. Storyboards serve as visual tools that depict user experiences, workflows, or key functionalities, making it easier for participants to engage, discuss, and iterate on potential solutions effectively.

This visual representation allows analysts to bring concepts to life, providing context that can lead to deeper discussions and insights. When stakeholders can visualize the user journey or an interaction scenario, they are more likely to provide relevant feedback, highlight missing elements, and collaboratively refine the project’s direction.

Other principles, while valuable in their own right, do not specifically capture the essence of using a storyboard in this context. For instance, while thinking as a customer emphasizes understanding customer needs, it does not directly involve the visual representation aspect. Similarly, stimulating collaboration and continuous improvement and seeing the whole focuses on broader teamwork dynamics and holistic perspectives rather than the concrete, illustrative approach that storyboards provide.