What Is a Storyboard in UX Design? A Practical Guide

A storyboard in UX design is a sequence of frames that shows how a real person experiences a product or service in context. Not just the screens they tap through — the whole situation: where they are, what prompted them to act, how they feel at each step, and what their life looks like afterwards.

It borrows the format from film production, where storyboards map scenes before shooting begins. In UX, the purpose is similar: to make a user scenario concrete enough to discuss, critique, and build from, before significant time or money has been spent. A storyboard is one of the cheapest ways to test whether your team actually understands the problem it is trying to solve.

Want to use storyboards on a real project? UX Academy (myuxacademy.com)'s Beginner UX Design course teaches storyboarding and the full UX process with working professionals. Cohort 1 starts 5 Sep 2026 -- reserve your place with a £99 deposit.

What a UX storyboard is

A UX storyboard is a visual narrative. It shows a specific user — usually someone drawn from your user personas — moving through a specific scenario in a sequence of panels.

Each panel captures a moment:

• What is the user doing? (their action or situation)
• What is the context? (where they are, what device they are using, who else is present)
• What are they feeling? (frustrated, relieved, uncertain, satisfied)

A storyboard typically has between four and eight panels. More than that and it starts to become unwieldy. Fewer than four and it rarely captures enough context to be useful.

The key distinction from other UX artefacts is the emotional layer. A user flow tells you what a user does. A storyboard tells you what that experience is actually like. That difference matters because design decisions that look sensible on a flow diagram often reveal problems when you imagine how a real person would feel moving through them.

Why UX designers use storyboards

To build and share empathy

Research interviews and observation sessions generate rich insight. The problem is that insight often stays inside the heads of the people who did the research. A storyboard externalises it — it gives the whole team, including stakeholders who were not in the room, a shared picture of who the user is and what their experience looks like.

Teams that skip storyboarding tend to design for an abstract, idealised user rather than the complicated, distracted, time-pressured person revealed by the research. The storyboard keeps that real person visible throughout the project.

To spot problems early

When you draw out a scenario in sequence, you often notice things that were not obvious in the research notes. A user who is on a train with patchy signal. A moment where the product asks for information the user does not have to hand. A step that assumes the user has remembered something from three screens ago. These friction points surface naturally when you commit a scenario to paper — much more cheaply than they surface in a usability test six weeks later.

To align teams before design begins

Storyboarding is particularly valuable at the point in the UX design process just before wireframing starts. A short collaborative storyboarding session gets product managers, designers, and developers looking at the same user scenario and resolving disagreements about what the product needs to do before anyone has built anything.

To communicate to stakeholders

A three-panel storyboard showing a user's journey from frustration to resolution is faster to read and more persuasive than five paragraphs of research findings. If you need a client or senior stakeholder to understand why a design decision was made, a storyboard often does the job more effectively than a written rationale.

What does a UX storyboard contain?

The elements are simple. Most storyboards include:

Scenario — a one-sentence description of the situation being depicted. "Maya is trying to book a GP appointment during her lunch break." This grounds every subsequent panel.

Persona — the named user type the storyboard is drawn from. Even if the panels show a generic figure, naming the persona ties the storyboard back to the research.

Panels — the sequence of frames. Each panel shows a single moment in time. The visual does not need to be sophisticated — stick figures and rough sketches are completely acceptable. The point is communication, not illustration.

Captions — a short note under each panel explaining what is happening and, crucially, what the user is thinking or feeling. "Maya realises she cannot find her NHS number. She considers calling the surgery instead."

Emotional indicators — some storyboards include a simple emotion marker for each panel (a face showing frustration, relief, confusion). This makes the emotional arc of the journey explicit rather than implicit.

What you do not include: screen-level detail, UI specifications, exact copy, or anything that belongs in a wireframe. A storyboard is not a low-fidelity prototype. It operates at the level of human experience, not interface design.

How to create a UX storyboard

Step 1: Start with your research. A storyboard without research behind it is fiction. You need to know who the user is, what they are trying to do, and what their current experience looks like. If you have not done this yet, go back to your user research methods before you pick up a pen.

Step 2: Choose a specific scenario. Pick one task, one situation, one user type. Storyboards that try to show multiple users or multiple scenarios simultaneously lose their clarity. "How a busy working parent discovers and books a place on a course" is a usable scenario. "How users find us" is not.

Step 3: Map the key moments. Before drawing anything, list the moments that matter in the scenario. Aim for six to eight moments. These become your panels. Include the trigger (what prompted the user to act), the key interactions with the product, any friction points, and the resolution.

Step 4: Sketch each panel. Use whatever drawing medium is fastest. Paper and pen for a first draft. Figma or Miro if you need to share it remotely or refine it for a presentation. Each panel should be visually distinct — one moment, not a sequence within a panel.

Step 5: Write the captions. Captions are where most of the thinking happens. Write them in the user's voice or close to it: what they are doing, what they are thinking, and how they feel. Read them back and ask whether someone who had not done the research would understand the experience being depicted.

Step 6: Share and discuss. A storyboard that has not been reviewed is not finished. Share it with your team before treating it as a foundation for design decisions. The goal is to surface disagreements about the user scenario early, when they are cheap to resolve.

Storyboards vs user flows vs journey maps

These three artefacts are often confused. They are not interchangeable.

| | Focus | Level of detail | Best used for | |---|---|---|---| | Storyboard | Human experience in context | Scenario-level | Aligning on user needs; communicating empathy | | User flow | Steps through an interface | Screen-level | Mapping navigation logic; handoff to engineering | | Journey map | End-to-end experience over time | Service-level | Understanding the full customer lifecycle |

A storyboard is narrower than a journey map — it shows a single scenario in detail rather than the full arc of a customer relationship. It is broader than a user flow — it includes emotional context and real-world factors that a flow diagram does not capture.

In practice, you often use all three at different stages. Storyboarding comes early, when you are still establishing what the experience should be. Once the scenario is agreed, the next step is usually wireframing — translating the storyboard's human scenario into interface structure. User flows come alongside or after wireframing, when you are specifying how the interface will work. Journey maps are most useful for complex, multi-touchpoint products where the full service experience needs to be understood before any single scenario is designed.

When to use storyboards — and when to skip them

Storyboards earn their place when:

• The team has done research but has not yet aligned on the core user scenario
• You are starting a new product or a significant redesign
• Stakeholders are not close to the user research and need a bridge
• You want to communicate the rationale for a design decision in a way that will be understood by non-designers

They are less useful when:

• The user scenario is already well-established and agreed by the team
• You are making incremental changes to an existing product with known users
• You need to move quickly to wireframes and the team does not need alignment on the scenario first

Like most UX methods, storyboards scale to the complexity and uncertainty of the problem. On a one-week sprint for a mature product, they may add no value. On a six-month project for an entirely new service in an unfamiliar context, they can prevent months of wasted design work.

Tools for storyboarding

Paper and pen is the right tool for a first draft. The roughness is a feature — it keeps the focus on the scenario rather than the aesthetics, and it signals clearly that the work is exploratory. Most experienced UX designers sketch storyboards by hand even if they will later transfer them to a digital tool.

Figma works well for storyboards that need to be shared remotely, included in a presentation, or refined to a higher level of visual clarity. A simple frame-by-frame layout with annotation boxes is straightforward to produce. Figma's real advantage is that it lives in the same tool as your wireframes, so the transition from storyboard to design is frictionless.

Miro and FigJam are popular for collaborative storyboarding in workshop settings, where multiple team members are building the storyboard together in real time. The infinite canvas makes it easy to rearrange panels and add annotations without the structure of a formal Figma file getting in the way.

Dedicated storyboarding tools exist but are rarely used in UX practice. Boords, for instance, is designed primarily for film and animation storyboarding, not UX — it is rarely seen in product design teams. The method does not require specialist software — any tool that lets you place images and text in sequence will do the job.

Storyboarding as a learning exercise

For designers early in their careers, storyboarding is one of the most valuable skills to develop for a reason that goes beyond the artefact itself: it forces you to think from the user's perspective rather than the product's perspective. Drawing someone's experience in sequence — their context, their frustrations, their relief when something works — builds the habit of user-centred thinking that underpins every good design decision.

If you are switching careers into UX design, storyboarding is the kind of method that tends to resonate immediately because it connects design work to human experience in a visible way. It is also the kind of method that is easy to practise without a job — pick a scenario from your own life, research it (interview a friend, observe what happens), and draw it out. The thinking is what matters, not the drawing.

On the UX Career Track at UX Academy, storyboarding is taught as part of the discovery and synthesis phase of a real client project — alongside research methods, personas, and journey mapping — so you build a portfolio of connected artefacts that show a complete design process rather than isolated exercises. If you want to see what live UX training feels like before committing, the free UX masterclass at UX Academy (myuxacademy.com) is the place to start. Lead instructor Natalia Veretenyk and her team have used storyboarding professionally at organisations including Google, Adobe, and Canva. If you want to use these methods under supervision before you have to use them independently in a job, that is the fastest way to build the confidence to do it well. Take a look at our UX design courses to see what fits your situation.