---
title: "storyboards"
tags: 
- info203
---

mockup of user scenarios

problem with sketches
- hard to capture dynamics of interation over times=
- captures user interface not user behaviour

a good storyboard should tell a story
short and concise
low fidelity
not about pretty picures. ⇒ about communicating ideas

![](https://i.imgur.com/dyZIPH9.png)
![](https://i.imgur.com/YE27hWp.png)
![](https://i.imgur.com/uOqAl4o.png)


# 1 pros
+ holistic focus ⇒ helps emphasoze how an interface accopmlishes a task
+ avoid commitment to a particular UI
+ helps get all the stakeholders on the same page in terms of the goal


# 2 Tips
tell a story
![](https://i.imgur.com/NTpXK14.png)

- base it off the scenario

play with the angle/perspectives

![](https://i.imgur.com/aJ11kgo.png)
![](https://i.imgur.com/aBSoHwJ.png)

simplify and develop vocabulary/your own style
![](https://i.imgur.com/jwDROAW.png)


using tracing and templates
![](https://i.imgur.com/wwf7ab3.png)


- setting
	- people
	- environment
	- task being done
- sequence
	- what steps
	- what leads someone to the app
	- task task
- satisfaction
	- what is the users motivation
	- what does it enable people to accomplish
	- what need does the system fill