A solution storyboarding SOP checks whether the story of your product matches the lives of the people you build it for, and it takes less than a week. You draw six to eight simple panels, like a comic strip, showing one customer from the moment the problem hits to the moment the solution pays off. Then you show the panels to real customers and ask them to tell the story back. Every panel is an assumption about where people are, what they feel and what they do next. Customers spot the wrong ones in seconds, long before you pay a designer.

What is solution storyboarding and when should you use it?

Solution storyboarding borrows the storyboard from film and animation to test a product idea. Each panel shows a scene: the setting, the person, what they do and a caption with what they think or feel. Jake Knapp's five-day design process from Google Ventures uses a storyboard to plan a prototype, and Kenn Adams's Story Spine ("Once upon a time... Every day... Until one day...") gives a ready structure for the beats.

Use this SOP:

When your solution spans several moments or people, such as a parent, a child and a school, or a buyer, a courier and a shop.
When the context decides success: on the bus, at a client site, at 11pm after the kids sleep.
Before you design screens, so the prototype shows the moments customers know from their own lives.
When the team pictures the product differently. One storyboard puts everyone on the same page, literally.

A storyboard tests one future story with customers. To generate solution ideas as a team, use the solution sketching workshop SOP. To map how customers handle the problem today, use customer journey mapping.

What do you need before you start?

One customer profile with a name, situation and trigger. The free user persona generator or the persona development SOP gets you there.
Interview notes about the moment the problem hits: where, when and with whom.
Drawing tools: paper and a marker work fine. Boords, Storyboarder or Canva help if you want clean panels for remote sessions.
5 to 8 target customers for 30-minute sessions, in person or over Zoom.
A notes sheet with one row per panel.

How do you run it, step by step?

1. Pick one scenario

Choose the most common trigger from your interviews: the moment the problem shows up. One storyboard covers one scenario. If you have three very different triggers, draw three storyboards and test the most frequent one first.

2. Write the beats with the Story Spine

Write six to eight beats before you draw: the normal day, the trigger, how the person finds your solution, first use, the result and the day after. Write each beat as an assumption you could be wrong about, such as "She opens the reminder on her phone at the bus stop."

3. Sketch the panels

Draw one scene per beat with stick figures, a clear setting and a caption. Add a thought bubble for the feeling. Keep the product small in the frame: the story is about the person, and the screen only appears where it matters.

4. List the assumptions under each panel

Below every panel, write the one or two assumptions it depends on: who is present, which device, how much time, what they feel. This list becomes your scoring sheet during sessions.

5. Walk customers through the panels one by one

Show one panel at a time and ask the participant to narrate: "What's happening here?" Then ask: "Is this you? What would you do instead?" Stay quiet and let them correct the story. Corrections are the data. Note the exact words.

6. Score each panel

Mark each panel per participant as confirmed, adjusted or rejected. After all sessions, count. Panels most people reject point at a wrong assumption about context, device, timing or people involved.

7. Redraw and retest

Fix the rejected panels using the participants' own corrections and test the new version with three people who haven't seen it. Repeat until the story holds.

8. Hand the story to design

The confirmed panels become the outline for your prototype or your explainer video. Every screen you design should belong to a panel customers confirmed.

Template you can copy

STORY SPINE BEATS (one scenario)
1. Every day, [persona] ... (normal routine)
2. Until one day, ... (trigger, the problem hits)
3. Because of that, she ... (finds or opens the solution)
4. Because of that, ... (first use, what she does)
5. Because of that, ... (the result she gets)
6. Until finally, ... (what changes in her week)
7. And ever since, ... (the habit that forms)

PANEL SHEET
Panel # | Scene | Caption (what she does) | Thought bubble (what she feels) |
Assumption 1 | Assumption 2

SESSION SCORING (one row per panel, per participant)
Participant | Panel # | Confirmed / Adjusted / Rejected |
Their correction (exact words) | Interest moment Y/N

SESSION QUESTIONS
- What's happening in this picture?
- Is this you? What would you do instead?
- Who else would be there?
- (After the last panel) Tell me the whole story back in your own words.

Worked example: medication reminders for a parent far away

This example is illustrative. A founder plans a service that helps adult children check that an elderly parent living alone takes daily medication. Her seven-panel storyboard shows the daughter setting it up, the father getting a reminder on a phone app, and a weekly report.

She runs sessions with 7 adult children of elderly parents.

Panels 1 to 3 (worry, trigger, setup) were confirmed by 6 of 7.
Panel 4, the father using a phone app, was rejected by 5 of 7: "My dad doesn't use a smartphone." Three said a phone call would work.
Panel 6, the weekly report, prompted 4 of 7 to ask "Can my brother see it too?"
3 participants asked when they could try it, without being prompted.

She redrew panel 4 as an automated landline call and added a shared family view to panel 6. A second round with 3 new participants confirmed all 7 panels. Her prototype now starts with the family view, a screen that wasn't in her first plan.

What should you measure, and when do you stop?

Metric	Pass signal	Warning signal
Panel recognition rate	70%+ of panels confirmed by most participants	Fewer than half of panels confirmed
Rejected assumptions	Each rejected panel has a clear, repeated correction	Corrections contradict each other
Story retelling accuracy	Participants retell the result in their own words	They can't say what the product does for them
Unprompted interest	2+ participants ask when they can try it	Polite thanks and nothing else

Stop when a fresh group of three confirms every panel. If corrections contradict each other across participants, your profile covers two different customers: split them and draw a storyboard for each.

Which mistakes should you avoid?

Drawing the product instead of the person. Panels full of screens test your interface, and this test is about context.
Explaining the panels. If you have to explain, the panel fails. Let them narrate.
Testing with your team. Colleagues know the plan and fill in the gaps.
Polishing the art. Stick figures get honest corrections. Glossy panels get compliments.
Skipping the retest. A fixed panel is a new assumption until someone else confirms it.

How can AI speed this up?

AI image tools can turn your beats into consistent panels in minutes, which helps for remote sessions. Keep the style simple so it doesn't look finished. An AI assistant can also draft the Story Spine beats from your interview notes and summarize the session scores. The human check: you run the sessions and write down the exact corrections, because an AI summary flattens the "my dad doesn't use a smartphone" moments into averages.

For more ways to test ideas visually, our sister site collects 100 startup methods, and the F/MS free startup school covers the full path from idea to launch.

Where does this SOP fit in your validation plan?

Storyboarding comes early in Solution Validation, between understanding the customer and building anything clickable.

Before: capture feelings and context with customer empathy mapping and map today's path with customer journey mapping.
Alongside: generate alternative ideas in a solution sketching workshop.
After: build the confirmed panels into a clickable prototype, or turn them into a script for a solution explainer video.

See all Solution Validation SOPs.

FAQ

How many panels should a solution storyboard have?

Six to eight. Fewer skips the context, more turns into a manual nobody reads.

Do I need to be able to draw?

No. Stick figures, a few props and clear captions are enough. Rough drawings invite corrections, which is what you want.

How many people should I test a storyboard with?

Five to eight from one target profile, then three new people for the revised version.

What is the difference between a storyboard and a customer journey map?

A journey map shows how customers deal with the problem today, step by step. A storyboard shows one future story with your solution in it, drawn as scenes for customers to react to.

Solution Storyboarding SOP