Storyboard

The customer's whole journey drawn out frame by frame, like a comic strip, from the moment they hit the problem to the moment your solution resolves it. You walk a real person through the frames and watch where they stop nodding. You're testing the narrative before you build the thing it's about.

The question it answers

A storyboard answers a messaging question: does the story of how this fits their life actually land, or does it break somewhere you couldn't see from inside it? Messaging is whether the story and the words land in their life. Usability is whether a person can actually work the screen in front of them. Two different questions, and a tool answers one of them, not both.

That's a different question from the two prototypes next to it on this shelf. A paper prototype and a clickable prototype both test usability, whether a person can work the screen in front of them. A storyboard zooms all the way out. It puts no screen in anyone's hand. It tests whether the whole arc, the problem, the moment they reach for you, the relief, holds together as a thing that belongs in their day.

This is the purest messaging test in the catalog. A landing page sells the dream in a single panel. A storyboard tests the whole life around it, and the frame where the story breaks is a hole a polished pitch would hide.

How to run it cheaply

The minimum version is a stack of hand-drawn frames and five real people. You're spending an afternoon, not a sprint, and you need zero engineering.

1. Map the journey end to end, then pick the six or so frames that carry it. The first frame is the problem at its sharpest. The last is your solution resolving it. The frames between are the real moments in their life, not your product's features.
2. Draw each frame by hand. One panel per beat. Ugly is okay. A storyboard isn't art, it's a sequence you can point at, and rough drawings tell people you want the truth, not a compliment on your sketching.
3. Write down the audience, the success number, and the end date before you show anyone a single frame. This is the discipline the whole catalog leans on. For a messaging test the number is usually a break count: how many of your five testers can stall at the same frame before you call that frame broken, often two or three of five.
4. Walk one real person through the frames at a time, in order. Narrate lightly, then go quiet and let them react, with the patience to keep quiet at the exact frame you're most nervous about. Where they frown, where they ask "wait, how does that part work," that's the signal you came for.
5. Mark every frame where the nodding stops, and run five people one at a time so the real hole repeats itself.

Five is the working number for the same reason it is on the prototype pages. The Nielsen Norman Group found that five users surface about 85% of the problems in a flow. Not all of them, but the big ones, the ones worth knowing before you build.

A worked example

Here's the move run start to finish. The product and the reactions are invented to make the mechanics concrete. The method is real.

You're pitching a meal kit aimed at people who work twelve-hour hospital shifts, and you want to know if the story holds together before you spend a dollar selling it. So you draw six frames. The exhausted post-shift drive home. The empty fridge. The phone notification, "your box is at the door." The ten-minute cook. The actual sit-down meal. The next morning, feeling human. You walk five target customers through it, one at a time, and you watch.

Three of five frown at the notification frame. "Wait, how does a perishable box just sit at my door for a twelve-hour shift?" That's not an opinion from a survey. It's the same break, in the same frame, three separate times.

You found a cold-chain hole, a problem keeping perishable food cold from box to door, that no landing page would ever surface. You fix that frame before you build anything or spend on a single ad. The cheapest place to find a broken story is on paper, in front of five people, before the story is load-bearing.

When to reach for it, and when not

Reach for a storyboard when the question isn't "can they tap the button" but "does this even make sense as a thing in their life." It's cheap, so run it before you've spent real money telling the story anywhere it's expensive to be wrong.

Don't reach for it when the question is something else:

• If the question is whether a person can work a specific screen, that's usability, not messaging. Use a paper prototype first, then a clickable prototype if you need the finer read. A storyboard tests the story. A prototype tests the tapping. Don't run one and think you ran the other.
• If you haven't yet proven anyone wants the thing at all, you're on the wrong shelf. Earn the yes first with a demand experiment, a test of whether anyone wants this at all, like a social-media teaser or a landing-page test. The storyboard tunes a story worth telling. It doesn't tell you whether to tell one.

One note. Reuse the teaser and landing page you already built for demand, run them again with a different question, and they'll test whether the words land too. The storyboard is the purest messaging test, not the only one.

That's the rule underneath the whole catalog. Match the prototype to your question. There's no best experiment. There's the cheapest one that answers the question you're actually asking. When that question is "does the story of this hold up in their real life," the storyboard is almost always the cheapest answer on the board.

The taxonomy behind this page comes from Testing Business Ideas by David Bland and Alex Osterwalder, who map the storyboard as one of more than 40 ways to test an idea before you build it. Start low-fidelity. Add fidelity only when you need more specific feedback.