Brand/User Scenerios & Storyboards

The following is information regarding experience and user scenarios, how to write and storyboard them. It has been taken directly from the following blog:

https://www.justinmind.com/blog/user-personas-scenarios-user-stories-and-storyboards-whats-the-difference/

  

Scenarios

A scenario is a situation that captures how users perform tasks on your site or app. Scenarios describe the user’s motivations for being onsite (their task or goal) and/or a question they need answered, and suggest possible ways to accomplish these objectives. It is essentially a development of the user story, and can relate to multiple target users. However, scenarios can also be broken down into use cases that describe the flow of tasks that any one user takes in a given functionality or path.
For example, a scenario could outline how John uses a mobile app to buy a ticket to a design workshop whilst on his way to work.

Benefits to your design process
Scenarios help stakeholders envision the ideas of the design team by providing context to the intended user experience – frequently bridging communication gaps between creative and business thinking. For the design team, scenarios help them imagine the ideal solution for a user’s problem.

 “Scenarios are the engine we use to drive our designs.”UX influencer, Kim Goodwin

How to write a scenario

Scenario planning starts with scenario mapping. The design team, developers and product owner will meet to exchange ideas and create a strategy based on their user personas. With the primary user defined through persona development, they can now consider the key task that the user hopes to achieve. The next step is to perform a scenario analysis, put the user’s goals into context and walk through the steps that the user would take.


















Scenario mapping. Image Credit: Apps For Good

Storyboards

A storyboard is a visual representation of how the user would react with your site or app. There are different types of storyboards that designers can create: sketches, illustrations and screenshots, slideshows and animated, live demos. The technique was developed by Disney Studios for motion picture production in the 1930s.

As Nick Babich has it, storyboarding helps you “visually predict and explore a user’s experience with a product”.

Here’s a sketched storyboard example:


















Low fidelity storyboard. Image Credit: Google.ca

Benefits to your design process
Storyboarding is a great way to communicate design ideas to teams, stakeholders and end users visually. As with high-fidelity prototypes, visualizing a design idea with an interactive storyboard will help the audience remember as well as empathize and engage with it.

How to create a storyboard
To create a storyboard, you’ll need to set the scene, defining your character, or buyer persona, environment (where the persona finds themselves), and plot (what they want to achieve). Then, you can start to sketch out the initial idea for each scene, and build them up with as much interaction as you like. Using a prototyping tool like Justinmind is a great way to create storyboards – both for static designs and interactive animations.