UX
Storyboarding
A practical UX method for visualising experiences over time so teams can align on flow, context, and key moments before committing to implementation.
How to use storyboarding to bring journeys to life, identify friction and gaps early, and improve alignment around the experience being designed.
What it is
Storyboarding is a UX method used to visualise an experience over time through a sequence of scenes.
It shows how a user interacts with a product or glossaryServiceA service is a component or function that performs a specific task within a system.Open glossary term in glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term, step by step.
Each frame represents a moment in the journey, including actions, thoughts, and emotions.
Storyboards can be simple sketches or more refined visuals, but the focus is on narrative, not polish.
The goal is to bring an experience to life so teams can understand, align, and design better solutions.
Storyboarding is most useful when teams need to understand the lived experience of a journey, not just the structure of screens or flows.
When to use it
Use this method when you need to understand or communicate an experience.
It is most useful when:
It is less useful when:
Storyboarding is often used in early to mid design phases.
Key takeaway
Use storyboarding when the challenge is making an experience understandable across time, context, and emotion before detailed design work starts.
How to run it
Set up properly
Be clear on the journey you are telling and where it starts and ends. Storyboards work because they are bounded narratives, not because they are drawings.
Decide who the storyboard is for. One made to think with looks very different from one made to persuade with.
Run the method
Storyboarding tells a journey as a sequence of scenes. It forces you to be specific about glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term and sequence in a way a flow diagram allows you to avoid.
- Define the start and end of the journey, including what happens before the product is involved.
- Break the experience into key moments rather than into screens. A storyboard of screens is a flow diagram with borders.
- Sketch each step as a scene, showing the person and their surroundings rather than the glossaryInterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term alone.
- Include actions, thoughts and emotions at each step, which is what distinguishes this from a wireframe sequence.
- Keep the visuals simple. Detailed illustration shifts the conversation to the drawing.
Show the world around the person, not just the screen. The glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term is the reason for choosing this method over a flow.
Capture and make sense of it
The value comes from making the experience concrete. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- The narrative, scene by scene
- Assumptions the story depends on
- Moments where the experience is weak or unresolved
- Questions the storyboard raised that need serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service
Use this to communicate a concept and to expose gaps. Anything you cannot draw is usually something you have not thought through.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If it doesn’t tell a clear story, it’s not working.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you design experiences, not just screens.
Get in touch
If this sounds like something you need, we can help you create storyboards that bring your user experience to life and uncover what really matters.
No guesswork. No assumptions. Just clear, experience-led design.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is storyboarding in UX?
It is a method for visualising a user journey through a sequence of scenes.
When should you use storyboarding?
Use it when designing or communicating experiences.
Do storyboards need to be detailed?
No. They just need to tell a clear story.
What should a storyboard include?
The sequence of what a person is doing, the context they are doing it in, and what they are thinking or feeling at each step. Include the moments before and after the product is involved. That is usually where the useful gaps show up.
Does storyboarding improve UX?
Yes. It helps teams understand and design better experiences.
Quick take
If you want to see how an experience plays out before building it, storyboard it.
Related Services
Related Guides
