Storyboarding visualises a user scenario as a sequence of frames, much like a comic strip, to communicate how a design will be experienced over time and across contexts. Borrowed from film production, where it has been used since the 1930s, storyboarding in design serves as a cheap, fast way to explore and communicate user journeys before anything has been built. The visual narrative format makes abstract ideas concrete and reveals temporal and contextual details that static wireframes or written specifications consistently fail to capture.
What It Is
A design storyboard consists of a sequence of hand-drawn or digitally created panels, each showing a key moment in a user's interaction with a product or service. Each panel typically includes a simple illustration of the scene, a caption describing what is happening, and optionally a speech bubble or thought bubble capturing the user's words or internal state. The level of drawing skill required is intentionally low: stick figures and rough sketches are standard. What matters is the sequence and the narrative, not the artistic quality of the individual frames.
How to Run It
Begin by defining the persona, the scenario, and the key moments you want to illustrate. Identify five to eight key frames that represent the most important points in the experience, including the triggering need, the moment of engagement with the product or service, the key interaction, and the resolution. Sketch each frame quickly using the simplest possible illustrations. Add captions and annotations. Review the storyboard with the team and with users to check whether the scenario feels plausible and whether the key experience moments have been captured accurately. Iterate based on feedback.
When to Use It
Storyboarding is most valuable during ideation and early concept development, when the team needs to communicate a design concept to stakeholders, clients, or users before any prototype exists. It is also useful for aligning a team around a shared vision of the intended user experience. Use it whenever you need to communicate 'here is how this will feel' rather than 'here is what this will look like,' because it foregrounds the human story of a design rather than its visual form.
Tips for Success
Focus on the emotional and experiential arc of the scenario rather than on technical accuracy. Storyboards that show a user's emotional state shifting as a result of interacting with a design are far more compelling than storyboards that focus only on interface states. Include context: show where the user is, what they are doing before and after the interaction, and how other people or systems are involved. Keep the drawing style loose and fast: overly polished storyboards signal false certainty and discourage the kind of honest feedback you need at this stage.
