Difference between revisions of "Storyboards"

From
Jump to: navigation, search
(Procedure)
(Purpose & Objectives)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
== What is it? ==
 +
Storyboards are a visual representation of a sequence of action through a series of images. Similar to a comic book, they show the interaction between a user and the product in an appealing form that anyone can understand.  Each image represents an important step in the action. If the images are not self-explanatory, they are supplemented by additional comments.
 +
 
== Purpose & Objectives ==
 
== Purpose & Objectives ==
Why are you doing this? What are you aiming for?
+
''Why are you doing this? What are you aiming for?''
  
 
+
Storyboards have the great advantage that they are easy to understand for everyone due to their visual and concrete representation.
- explaining how to use the product through a story
+
In addition, they can be created without any special prior knowledge. They are a useful supplement to scenarios and are also popular for stakeholder presentations or initial user tests.
 
+
;They can be used
 
+
: as a supplement to scenarios
- help the user understand how the product functions
+
: to ty the pieces together from
 
+
:* personas,
 
+
:* scenarios,
- marketing: encourage potential users to use product through the story
+
:* requirements,
 
+
:* use cases
 
+
: into a visual representation of the planned interaction
- help creators understand user needs
+
: to set priorities about which interaction should be implemented
  
 
== Data Sources ==
 
== Data Sources ==
Where do you find the knowledge or inut needed to do it?
+
''Where do you find the knowledge or input needed to do it?''
+
;Use
- users
+
* Scenarios
 
+
* Personas
- similar platforms or apps
+
* Use cases
 
+
* User Stories
- developers or creators of the product
 
  
 
== Procedure ==
 
== Procedure ==
How do you do it? Which techniques and tools do you use?
+
''How do you do it? Which techniques or tools do you use?''
 
+
* Start with a scenarios to demonstrate how a person uses a system to achieve his/her goals. Include characteristics from your personas for a realistic representation.
 
+
* Define a sequence of key scenes in the interaction.
- brainstorm ideas on use of product
+
* Draw pictures or use wireframes, screenshots, photos to show what happens in the scenes.
 
 
 
 
- specify one scenario
 
 
 
 
 
- understand needs of user
 
 
 
 
 
- visualize the scenario through pictures or video
 
  
 
== Outcomes / Results ==
 
== Outcomes / Results ==
What do you get once you have done it?
+
''What do you get once you have done it?''

Latest revision as of 07:02, 30 June 2023

What is it?

Storyboards are a visual representation of a sequence of action through a series of images. Similar to a comic book, they show the interaction between a user and the product in an appealing form that anyone can understand. Each image represents an important step in the action. If the images are not self-explanatory, they are supplemented by additional comments.

Purpose & Objectives

Why are you doing this? What are you aiming for?

Storyboards have the great advantage that they are easy to understand for everyone due to their visual and concrete representation. In addition, they can be created without any special prior knowledge. They are a useful supplement to scenarios and are also popular for stakeholder presentations or initial user tests.

They can be used
as a supplement to scenarios
to ty the pieces together from
  • personas,
  • scenarios,
  • requirements,
  • use cases
into a visual representation of the planned interaction
to set priorities about which interaction should be implemented

Data Sources

Where do you find the knowledge or input needed to do it?

Use
  • Scenarios
  • Personas
  • Use cases
  • User Stories

Procedure

How do you do it? Which techniques or tools do you use?

  • Start with a scenarios to demonstrate how a person uses a system to achieve his/her goals. Include characteristics from your personas for a realistic representation.
  • Define a sequence of key scenes in the interaction.
  • Draw pictures or use wireframes, screenshots, photos to show what happens in the scenes.

Outcomes / Results

What do you get once you have done it?