# Storyboarding user flows

> Learn how to turn a user flow into a storyboard with a character, scene, plot, and narrative arc that wins over stakeholders.

Source: https://uxspot.io/storyboarding

<section id="what-is-storyboard">
<h2>What is a UX storyboard?</h2>
<img src="/images/storyboard.webp" width="2400" height="1330" alt="Storyboard template — six numbered sketch frames, each with caption lines underneath" title="Storyboard template">
<p class="blockquote">A UX storyboard is a sequence of panels that visualizes a user's experience with a product, step by step, from the moment a problem appears to the moment it is resolved.</p>
<p>The technique is borrowed directly from film-making. Before a director spends money on cameras, actors, and sets, the crew sketches every shot on paper to test whether the story actually works. UX designers do the same thing for a different reason: <strong class="highlight">a storyboard lets you test whether an experience makes sense before anyone spends time building it.</strong></p>
<p>Imagine you are designing a train ticket app. A flowchart can tell you that the user moves from search to seat selection to payment. A storyboard tells you something the flowchart cannot: the user is standing on a crowded platform, holding a coffee in one hand, with four minutes until departure. That context changes every design decision you make.</p>
<p>Storyboards come in different flavors, such as <a href="/storyboard-types" class="redirect">big picture and close-up boards</a>, but each of those deserves its own article. Here, we focus on what every storyboard shares.</p>
<ul>
<span>keywords</span>
<li>#Storyboard</li>
<li>#Visualization</li>
<li>#FilmMaking</li>
</ul>
</section>
<section id="four-ingredients">
<h2>The four ingredients</h2>
<p>Every good storyboard, whether it was drawn for a movie or a mobile app, contains the same four ingredients. If one is missing, the story falls flat and the storyboard becomes a decorated flowchart.</p>
<div id="character">
<h3>Character</h3>
<p>The character is the user your story revolves around, usually based on <a href="/understand-personas" class="redirect">one of your personas</a>. <strong class="highlight">Your character needs a name, a goal, and a reason to care, because nobody empathizes with "the user."</strong> Compare "the user wants to buy a ticket" with "Nadia is late for a job interview and needs a ticket in the next four minutes." The second version makes your team feel the stakes.</p>
<p>Show what your character does, says, thinks, and feels in each panel. A simple thought bubble or a frown communicates emotion faster than a paragraph of research findings.</p>
</div>
<div id="scene">
<h3>Scene</h3>
<p>The scene is the context and environment where the experience happens. Is your character at a quiet desk or on a noisy platform? On fast office Wi-Fi or a weak mobile connection? Alone or surrounded by distractions? <strong class="highlight">Most design failures happen because a product was designed for a calm scene and used in a chaotic one.</strong> Drawing the scene forces you to design for reality.</p>
</div>
<div id="plot">
<h3>Plot</h3>
<p>The plot is the problem your character faces and how your product resolves it. A storyboard without a problem is just an advertisement. Start with a clear conflict, such as a missed refund, a confusing checkout, or a lost booking, and end with a resolution that your product makes possible. The plot is where <a href="/value-proposition" class="redirect">your value proposition</a> either proves itself or falls apart.</p>
</div>
<div id="narrative-arc">
<h3>Narrative arc</h3>
<p>The narrative arc is how tension rises and falls across the panels. Like any story, a storyboard has a beginning that establishes the character and scene, a middle where the problem escalates, and an end where the resolution lands. Without an arc, panels are just disconnected screenshots. With one, your audience leans in to find out what happens next.</p>
</div>
<ul>
<span>keywords</span>
<li>#Character</li>
<li>#Scene</li>
<li>#Plot</li>
<li>#NarrativeArc</li>
</ul>
</section>
<section id="why-persuade">
<h2>Why storyboards persuade</h2>
<p>You could present the same insight as a spreadsheet: 34% of users abandon checkout at the payment step. Accurate, but forgettable. Show the same stakeholders a six-panel story of Nadia fumbling with a card form on a moving train, and the room reacts.</p>
<p class="blockquote">People forget numbers, but they remember stories, and they make decisions based on what they remember.</p>
<p>Stories also create shared understanding. When a stakeholder reads a spreadsheet, they imagine their own version of the problem, and everyone in the room imagines a different one. <strong class="highlight">A storyboard puts one concrete picture of the problem in every head, so the team argues about the same thing instead of ten imagined things.</strong> That alone can save weeks of misaligned work.</p>
<ul>
<span>keywords</span>
<li>#Stakeholders</li>
<li>#Storytelling</li>
<li>#Alignment</li>
</ul>
</section>
<section id="six-panels">
<h2>Storyboard a flow in six panels</h2>
<p>Six panels is a comfortable length: enough room for an arc, short enough to force focus. Here is a step-by-step way to fill them.</p>
<p><strong>Panel 1: Establish character and scene.</strong> Show who your character is and where they are. Nadia on the platform, phone in hand, clock visible.</p>
<p><strong>Panel 2: Introduce the problem.</strong> Make the conflict explicit. The ticket machine has a long queue and the train leaves in four minutes.</p>
<p><strong>Panel 3: Raise the stakes.</strong> Show what happens if nothing changes. Nadia pictures walking into her interview thirty minutes late.</p>
<p><strong>Panel 4: Enter the product.</strong> Your character discovers or opens your product. Keep the interface loose, a rectangle with a button is enough at this stage.</p>
<p><strong>Panel 5: Resolve the problem.</strong> Show the key interaction succeeding. Nadia buys a ticket in two taps while walking to the door.</p>
<p><strong>Panel 6: Show the outcome.</strong> End on the emotional payoff, not the interface. Nadia in her seat, relieved, as the train pulls away.</p>
<p>Under each panel, write one caption line describing the action and, if useful, what the character thinks or feels. <strong class="highlight">If you cannot caption a panel in one sentence, the panel is doing too much and should be split or cut.</strong> When you are done, walk through the sequence with a teammate and watch where they stop nodding. That pause is your weak point in the flow.</p>
<ul>
<span>keywords</span>
<li>#SixPanels</li>
<li>#UserFlow</li>
<li>#StepByStep</li>
<li>#Captions</li>
</ul>
</section>
<section id="drawing-skill">
<h2>Drawing skill doesn't matter</h2>
<p>The most common reason designers avoid storyboarding is "I can't draw." Good news: it doesn't matter. Stick figures, boxes, arrows, and speech bubbles are the entire vocabulary you need. A circle with a sad mouth communicates frustration just as well as a portrait would.</p>
<p class="blockquote">A storyboard is judged by the clarity of its story, never by the quality of its drawings.</p>
<p>In fact, rough sketches often work better than polished ones. Polished visuals invite feedback about colors and style, while rough panels keep the conversation focused on the experience itself. Spend your effort on the plot, not the pencil work.</p>
<ul>
<span>keywords</span>
<li>#StickFigures</li>
<li>#Sketching</li>
<li>#RoughIsFine</li>
</ul>
</section>
<section id="takeaways">
<h2>Takeaways</h2>
<p>A storyboard turns an abstract user flow into a story your whole team can see, feel, and question. Build it from four ingredients: a character worth caring about, a scene grounded in reality, a plot with a real problem, and an arc that carries tension from panel to panel. Six rough panels and honest captions will persuade a room faster than any spreadsheet, and your drawing skills have nothing to do with it.</p>
</section>