![]() ![]() Depending on the purpose of the storyboard and on its audience, these images can be quick, low-fidelity drawings or elaborate, high-fidelity artifacts. The steps can be sketches, illustrations, or photos. VisualsĮach step in the scenario is represented visually in a sequence. For example: Corporate buyer, James, needs to replenish office supplies. The description of the scenario or story is clear enough that a team member or stakeholder could understand what is depicted before looking at the visuals. A short text description of the scenario is also included. The persona or role that corresponds to that scenario is clearly specified at the top of the storyboard. Storyboards are based on a scenario or a user story. ![]() Not sure where to start? Here's a storyboard template ( PDF version). There are always 3 common storyboard elements, regardless of form: a specific scenario, visuals, and corresponding captions. Using images makes the story quick to understand at first glance and easy to remember. In the world of UX, we use storyboards to provide additional context to our teams and stakeholders. Simple visuals and a basic, but specific scenario will be memorable for your team and stakeholders. A storyboard doesn't have to be complicated or high-fidelity. While the level of fidelity differs across industries, storyboards always communicate a story through images.ĭefinition: A storyboard communicates a story through images displayed in a sequence of panels that chronologically maps the story’s main events. You may already be familiar with the concept of storyboards from film, animation, or comic books. There are many ways to visually communicate stories to our teams and stakeholders - UX stories, storyboards, journey maps, and empathy maps being a few examples. A story captures attention, provides clarity, and inspires teams and stakeholders to take action. Storytelling plays a large role in our job as UX professionals. ![]()
0 Comments
Leave a Reply. |