What it is
A sequence of sketched frames depicting a user’s experience over time, the situation, actions, and emotions, used to communicate a scenario or concept as a narrative.
When to use it
During Ideate and early Prototype, to explore or communicate how a concept fits into a user’s real context.
Why (value)
Anchors design in narrative and context, makes abstract concepts tangible, and reveals gaps in the experience a static screen would hide.
How to run it
- Pick the scenario and the user.
- Break the experience into key moments (frames).
- Sketch each frame: setting, action, emotion.
- Add captions to clarify.
- Share to communicate and pressure-test the concept.
Inputs and outputs
- Inputs: A scenario or concept and a target user.
- Outputs: A visual narrative of the experience.
Time and effort
Low. An hour or two.
Evidence and limitations
A communication and framing tool, not evidence. The story reflects intent and assumptions until validated. See Evidence and limitations.
Tips and pitfalls
- Focus on context and emotion, not UI detail.
- Keep frames few and meaningful.
- Rough sketches are fine, clarity beats polish.
Variations
Concept storyboards, scenario storyboards, comic-style narratives.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
- Gamestorming.
Explore related methods
- Scenarios — Narrate how a specific person accomplishes a goal so the team designs for realistic context.
- Sketching — Think with a pen: explore many ideas fast and cheap before committing to any.
- Journey mapping — Visualize a person's end-to-end experience across steps, emotions, and touchpoints to find pain and opportunity.
