The study guide identifies B. Storyboards as the correct technique. A storyboard visually communicates how a proposed solution fits into a user's broader context, activity, or journey. Rather than showing only the interface, it presents a sequence of situations or interactions that helps stakeholders understand where, when, and why a solution matters to the customer. That makes a storyboard particularly useful in this scenario. The UX Designer already has an innovative concept; the challenge is helping the team understand how that concept integrates with the customer's real-world behavior. Option A, Personas, describe archetypical users, including characteristics, goals, behaviors, and pain points. Personas help teams understand who they are designing for, but they are less suitable for communicating the chronological context of a particular proposed solution. Option C, a High-fidelity Prototype, demonstrates the detailed appearance and interaction of the product itself. It can validate interface behavior but may still fail to communicate how the solution fits into the customer's broader activity. Storyboards bridge that gap by presenting the solution as part of a narrative. In Human-Centered Design, this allows stakeholders to evaluate the design in terms of customer context instead of viewing it only as a technical feature.
Study Guide reference/topics: Storyboards, contextual design, customer journey, communicating solutions, Human-Centered Design.
==================================
