5.12 Storyboard the Solution
At a Glance
Other names Solution Storyboard · Storyboard
In Brief
Storyboard the Solution is a comic-strip narrative — typically 4 to 8 panels — that draws a proposed solution into the context of a customer’s real life. Unlike wireframes or prototypes that show the product in isolation, a storyboard shows the entire journey: the trigger event, the decision to use the product, the experience of using it, and the outcome. You show this narrative to people in your target segment and listen for confusion, skepticism, excitement, and corrections that refine how the solution should work in context — not a yes/no verdict, but the reactions that reshape your design.
Common Use Case
You have validated that a problem is real and you have a proposed solution in mind, but you have not yet built wireframes or a prototype. You want to test whether the end-to-end journey — trigger, decision, action, value, outcome — makes sense to customers before committing engineering effort. The output is a corrected storyboard plus a list of participant objections, missing panels, and reframings that should change your design.
Helps Answer
- Does the proposed user experience make sense to customers?
- Is the trigger event realistic — would customers actually seek this solution at that moment?
- Are there steps in the journey that feel confusing, unrealistic, or unnecessary?
- What do participants expect to happen that the storyboard does not show?
- Does the outcome depicted match what the customer actually wants?
Description
Storyboard the Solution is a sequence of rough drawn panels showing your proposed solution in use, from the moment that triggers it through to the outcome it produces. Drawing it forces you to think through the entire experience, not just the product interface. The payoff starts before anyone else reviews it: many product concepts fall apart when you try to draw the panel before the participant opens the app and the trigger event turns out to be implausible, or the panel after they finish and the outcome turns out to be underwhelming. A sequence of rough panels exposes narrative leaps that prose, slide decks, and feature lists hide.
Showing the storyboard moves the conversation beyond “would you use this?” (which usually gets a polite yes) to the specific experience depicted. Participants react to the narrative naturally: “That’s not how it would happen for me,” “I wouldn’t do it at that point, I’d do it when…,” “What happens after this panel? Does it also…?” These reactions are the data you are looking for.
Storyboard the Pain is the companion technique: it visualizes the problem before any solution exists. Run it first to confirm the problem, then run Storyboard the Solution once you have a concept worth testing.
How to
Prep
1. Define the customer journey you are depicting.
Pick one specific customer segment and one specific scenario. Storyboards fail when they try to show the general case — the panels become abstract and participants cannot react to them. Map the journey as five beats before you start drawing: trigger (the moment they notice the problem), decision (the moment they reach for a solution), action (the core interaction with your product), value (the moment they get what they came for), and outcome (what life looks like after). These five beats become the spine of your 4-to-8 panel storyboard.
2. Draft the first and last panels first.
The first panel is the trigger; the last panel is the outcome. Get these two right and the middle panels follow naturally. An implausible first panel undermines the whole journey, and an underwhelming last panel cannot be fixed by adding features.
3. Fill in the middle panels.
Use 2 to 6 middle panels to show how the customer moves from problem to outcome: how they discover the solution, their first interaction with it, the key moment of value delivery, and the transition to the outcome. Each panel should advance the story by one meaningful step.
4. Show the person, not just the product.
Every panel should include the user and their context — at a desk, on the bus, in a meeting. The product is a supporting character, not the star. A storyboard that shows only screens is a wireframe with extra steps; it loses the narrative leverage that makes the method work.
5. Keep the artwork rough and the text sparse.
Stick figures are perfectly effective. Polished illustrations distract participants into commenting on the art rather than the experience. A short caption or thought bubble per panel is enough — the storyboard should be immediately understandable without reading paragraphs of text. AI image generators can produce panels in minutes, but the polish often hurts the conversation; if you use them, ask for sketch-style output and resist the urge to refine.
6. Write the two open questions you will ask per panel.
The session runs on two questions you ask after the participant narrates each panel: one that tests whether the panel is realistic (“Does this feel realistic? What would actually happen differently for you?”) and one that tests what the participant expects next (“What would you expect to see next?”). Phrase them as open, non-leading questions and keep them fixed across sessions so reactions are comparable.
7. Review internally before you run a session.
Show the storyboard to a team member who was not involved in creating it. If they cannot follow the story without explanation, revise for clarity. The storyboard has to stand on its own — in the feedback session, you will not be allowed to narrate it for the participant.
Execution
1. Recruit 5 to 10 participants from the target segment.
You are looking for the same kind of participant you would recruit for a Solution Interview: people who have the problem, in the context the storyboard depicts. Five sessions is the minimum for any pattern to emerge; ten is the point at which corrections start to repeat.
2. Walk through the storyboard one panel at a time.
Show one panel at a time, in order. Ask the participant to narrate what they see — do not explain it yourself first. Their narration is data: where they hesitate, what they assume, what they ignore. After they have described the panel in their own words, ask the two questions you prepared in Prep. Avoid validating their interpretation. Your job is to surface their mental model of the journey, not to defend yours.
3. Observe corrections, extensions, and objections.
Note four classes of reaction in real time:
- Confusion — “What’s happening here?” The panel does not communicate; rewrite or replace it.
- Skepticism — “I wouldn’t do it that way.” The journey beat does not match the participant’s mental model; investigate.
- Excitement — “Oh, that would be great.” The panel resonates; treat as a candidate for the value moment in your messaging.
- Correction — “Actually, the problem for me starts earlier/later.” The participant is rewriting your storyboard for you; capture the rewrite verbatim.
4. Iterate between sessions when corrections converge.
If three participants in a row correct the same panel the same way, revise the storyboard before continuing. The point of running 5 to 10 sessions is to converge on a journey that resonates, not to collect uniform feedback on a fixed artifact. Two to three rounds of iteration typically produce a storyboard that stops generating surprises.
Analysis
The storyboard is generating useful data when participants engage with the narrative — arguing with it, correcting it, extending it. If they simply nod and say “looks good,” either the storyboard is too vague to react to or the participant is being polite. Push for specifics: “Walk me through your version of panel 3.”
Categorize each correction into one of four buckets, then read the pattern across participants:
- Broken trigger. Participants tell you the trigger event is unrealistic, mistimed, or attached to the wrong emotion. If multiple participants correct the same trigger panel, your go-to-market assumptions may be wrong even if the product is right. Fix the trigger before anything else — every later panel depends on it.
- Missing decision logic. Participants describe a step between the trigger and the action that is not on the storyboard (“first I would check whether…”). Your journey is skipping the part where the participant talks themselves into using the product. Add the missing panel; that is often where adoption actually breaks.
- Feature-set mismatch. Participants want to skip a panel (“I would not need this step”) or ask what happens behind a panel (“does it also…”). The product scope you are depicting is wrong — too much in some places, not enough in others. Tighten the action panels to what the product will actually do at launch.
- Outcome inflation. Participants want the outcome panel to show more than your solution delivers. There is a gap between expectation and product scope, and the storyboard is leaking promises the product cannot keep. Either pull the outcome panel back to what is real, or expand the solution.
Convergent corrections across all four buckets tell you the concept is salvageable but the journey needs work. Corrections that cluster in only one bucket — usually trigger or outcome — tell you to fix that one thing and re-test before changing anything else. No corrections at all tell you the panels are too abstract, the artwork is too polished, or the participants are being polite; tighten the panels and recruit a new round.
The highest-leverage solution-design changes are the ones that resolve corrections in the trigger and decision buckets, because errors there propagate through every later panel. Action and outcome corrections are usually local — they change one or two panels, not the whole journey.
- Narrative bias A well-told story is persuasive regardless of whether the underlying product works. Participants may respond to the quality of the storytelling rather than the feasibility of the experience. Use rough sketches to keep the focus on substance.
- Anchoring The storyboard frames the conversation around your proposed journey. Participants may accept the framing rather than imagining alternatives. Ask explicitly: “How would you do this differently?”
- Selection bias Participants who agree to look at storyboards may be more imaginative and open to new products than your general target market. Pair the storyboard sessions with a recruiting screener that does not advertise the topic.
- Overgeneralization from a single scenario One storyboard covers one journey for one persona. Corrections from that session describe that scenario, not the whole segment. When corrections cluster around segment or trigger differences, create a second storyboard for the other case before drawing product conclusions.
Learn more
Case Studies
Savioke: Storyboarding a hotel-delivery robot
Ahead of a hotel pilot, Savioke ran a five-day Google Ventures design sprint that storyboarded the end-to-end guest-meets-robot delivery journey across lobby, elevator, and hallway, then tested the prototype with real guests at a Cupertino hotel — validating personality and interaction design before scaling.
Further reading
- Storyboard — IDEO Design Kit
- Storyboard — Wikipedia
- Storyboards Help Visualize UX Ideas — Nielsen Norman Group
- Knapp, Jake, John Zeratsky, and Braden Kowitz. Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon & Schuster, 2016. Day 3 of the design sprint is “Storyboard”; the book’s framing of the storyboard as the bridge between sketching and prototyping informs the trigger-to-outcome structure used here.
Got something to add? Share with the community.
