3.10 Storyboard the Pain
At a Glance
Other names Pain Storyboard · Problem Storyboard
In Brief
You draw the customer’s current experience as a 4-8 panel comic strip that ends on the pain point you believe they face, then walk a participant through the panels and watch where they correct, hesitate, or add detail. The output is a clear read on whether your picture of the problem matches their reality — the sequence of steps, the trigger, the moment things go wrong — before you commit effort to a solution.
For the solution-focused counterpart, see Storyboard the Solution.
Common Use Case
You have spoken with a handful of people and believe you understand their pain point, but the problem statement you wrote down still feels abstract. Before committing effort to a solution, you want to check whether you have the experience right. You sketch it as a rough comic and walk participants through it, watching for where they push back.
Helps Answer
- Am I describing the customer’s problem accurately?
- Do I understand the context in which the pain occurs?
- What parts of the customer experience am I getting wrong or missing?
- Is the emotional weight of the problem as significant as I assume?
- What happens before and after the painful moment?
- Are there steps in the experience I have not considered?
Description
A storyboard focusing on the pain point is a visual narrative that walks through the customer’s current experience, ending with (or centered on) the pain point you believe exists. Unlike a written description, a visual storyboard is concrete and specific: it forces you to commit to details about who the customer is, what they are doing, where they are, and what goes wrong. This specificity makes it much easier for a participant to react to and correct, frame by frame.
The same specificity is also where you are most likely to be wrong, which is the point — a participant who says “that is not how it works at all” about a single panel has just handed you a correction you would never have surfaced from an abstract description.
Reactions can run in several directions. A participant may confirm some panels, reject others, describe steps you left out, or place the whole story in a different context than you assumed. Each of those reshapes your understanding of the problem. Pay attention when corrections cluster: when several participants fix the same panel the same way, that part of your model is wrong; when they fix it in opposite directions, you may be looking at more than one segment.
Storyboards draw this out because they are low-fidelity and obviously unfinished. People critique a rough sketch far more freely than a polished presentation, which reads as a decision already made, so keep the fidelity low on purpose. The visual format also carries across language and literacy differences, so it holds up when the experience spans channels, departments, or cultures.
How to
Prep
-
Define the pain point you want to depict. Write a one-sentence description of the problem you believe your customer faces. Be specific about who the customer is, what they are trying to accomplish, and what goes wrong. Vague pain statements produce vague storyboards.
-
Sketch the first and last panels first. The first panel establishes the context (who, where, what they are trying to do). The last panel shows the consequence of the pain (frustration, wasted time, lost money, embarrassment). Starting with these two endpoints anchors the narrative.
-
Fill in the middle panels. Add 2-6 panels that show the steps between the starting context and the painful outcome. Each panel should depict one moment or action. Use simple visuals — stick figures, basic shapes, arrows — and minimal text. Captions or speech bubbles can clarify what is happening, but the visuals should carry the primary narrative.
-
Prioritize visuals over text. Resist the urge to write paragraphs of explanation. If a panel needs more than one sentence of caption, you are trying to convey too much in a single frame. Split it into two panels instead. The storyboard should be understandable at a glance.
-
Recruit 3-5 participants. Storyboard reviews produce useful patterns when you can compare reactions across multiple sessions. Aim for 3-5 participants from your target segment for the first round, then iterate the panels and run a second round if reactions are mixed.
-
Prepare the session script. Decide how you will introduce the storyboard, what open-ended questions you will ask, and how you will record corrections, hesitations, and additions. Frame the opening so the participant knows there are no right or wrong answers and that you want their criticism. Pilot the script with one participant or a colleague before running it for real.
Execution
-
Walk the participant through the storyboard panel by panel. Present the storyboard and narrate each panel briefly. Do not rush — give the participant time to absorb each frame before moving on. Avoid defending or explaining the visuals beyond a single sentence per panel.
-
Ask the open-ended questions from your script. Use prompts like “Does this look like your experience?” “What would you change?” “What am I missing?” “How does this make you feel?” Avoid yes/no questions. The goal is to invite correction, not seek agreement.
-
Observe corrections, hesitations, and expansions. Note which panels the participant confirms without comment, which they correct, where they pause, and where they add detail. Hesitations are often as informative as explicit corrections — a participant who frowns at a panel but does not articulate why is signaling something is off.
-
Capture emotional reactions. Pay special attention to moments where the participant says “yes, that is exactly it” or “no, that is not right at all,” or where their tone or expression shifts. These are the most informative data points.
-
Resist the urge to defend. When a participant corrects a panel, your instinct will be to explain why you drew it that way. Do not. Acknowledge the correction, take notes, and ask follow-up questions. The storyboard is a probe, not a position to defend.
Analysis
-
Aggregate corrections across participants. After each session, log which panels were confirmed, corrected, and expanded, plus key quotes. After 3-5 sessions, compile the pattern. Panels that multiple participants correct in the same direction are clearly wrong; panels that different participants correct in different directions may signal multiple personas.
-
Pay more attention to emotional reactions than rational critiques. A participant who gets visibly frustrated looking at a panel is confirming that the pain is real and significant. A participant who shrugs and says “I guess that is sort of right” may be signaling that the pain is not urgent enough to build a business around.
-
Catalog the additions. Steps participants add independently — especially when multiple participants add the same missing step — are likely important to the experience and may contain additional pain points worth investigating.
-
Watch for segmentation signals. When different participants react to the same panel in opposite directions (“this is exactly my experience” versus “this is nothing like my experience”), you may be looking at distinct personas with different journeys, not one segment with a single pain point.
-
Treat “I guess that is sort of right” as a red flag. Lukewarm validation is often an honest signal that the pain is not significant. Probe whether the participant has a stronger reaction to a different panel or a different version of the story before concluding the pain is real.
-
Note what participants ignore. Panels that participants skim past without comment may be either obviously correct or completely irrelevant to them. Probe both possibilities — silence is data, but it is ambiguous data.
- Leading narrative bias The storyboard itself frames the conversation. Participants may agree with your narrative because it seems reasonable, even if it does not match their actual experience. Use open-ended follow-up questions to counter this.
- Social desirability bias Participants may not want to criticize your work, especially if you are visibly the creator. Have someone else present the storyboard if possible, or explicitly invite criticism.
- Anchoring bias The specific details you include in the storyboard anchor the conversation. Participants may correct details within your frame rather than offering an entirely different frame. Ask “what am I not showing here?” to counter this.
- Recall bias Participants may not accurately remember their own experience when comparing it to a storyboard. Where possible, conduct the review close to when they last experienced the pain.
- Confirmation bias (creator form) You may unconsciously dismiss or minimize corrections that contradict your storyboard narrative — a form of confirmation bias amplified by creative ownership. Discovering you are wrong is the most valuable outcome of a storyboard review.
Learn more
Case Studies
IDEO: Mapping shopper pain points during the cart redesign
In the 1999 ABC Nightline “Deep Dive” segment, IDEO designers observed shoppers and mapped pain points — child seating, aisle navigation, theft, checkout friction — before redesigning the supermarket cart in a week through rapid brainstorming, prototyping, and user feedback.
Nielsen Norman Group: Storyboards in UX practice
NN/g’s guidance defines a storyboard as scenario plus sequential visuals plus short captions, and describes its primary uses as summarizing usability research, building team prioritization consensus, ideating, and enriching journey maps; the article advises keeping fidelity low.
Further reading
- Storyboards Help Visualize UX Ideas — Nielsen Norman Group
- Journey Mapping 101 — Nielsen Norman Group
- This Is Service Design Doing — Marc Stickdorn et al. (Service Design Network)
- Storyboarding in the Software Design Process — UX Magazine
- About Face: The Essentials of Interaction Design — Alan Cooper et al. (Wiley)
Got something to add? Share with the community.
