Storyboard in Service Design: Guide, Example & Template

A service storyboard is a visual narrative that depicts a person’s experience with a service as an image sequence — like a comic strip that shows what happens, what the person feels, and what goes on behind the scenes [1]. Instead of abstracting a service process into swim lanes and arrows, a storyboard tells a story: it has a protagonist, a trigger, a sequence of moments, and an outcome.

The method originates from the film and animation industry. Walt Disney Productions used storyboards as early as the 1930s to plan animated films before the costly production process — Webb Smith, a Disney animator, is credited with inventing the technique of arranging individual drawings in sequence on a wall [2]. In the design context, Bill Buxton (Microsoft Research) adapted the method in his foundational work “Sketching User Experiences” (2007) and argued: “The storyboard is one of the most powerful tools in design — because it shows not what something looks like, but what it feels like when you experience it” [3].

For service design, IDEO and the pioneers of the service design movement made the method productive. Stickdorn et al. (2018) classify storyboarding in This Is Service Design Doing as a low-fidelity prototyping method that is particularly valuable for stakeholder alignment and the communication of service concepts [1]. The key difference from a Customer Journey Map: A journey map analyzes. A storyboard tells. The journey map shows you touchpoints, channels, and emotion curves as an abstract diagram. The storyboard shows you a person in a situation — with context, emotion, and progression.

This article gives you everything you need to use storyboarding in a service design project: the methodological background, a step-by-step guide, a completed practical example from financial services, the six most common mistakes, and a systematic comparison with related visualization methods.

Why a Storyboard Reveals More Than a Journey Map

Most service processes in organizations are documented as flow diagrams, process maps, or Service Blueprints. These tools are analytically strong — but they have a systematic weakness: they abstract the experience. A process diagram shows you WHICH steps a customer goes through. A storyboard shows you HOW THAT FEELS.

The Three Advantages of Narrative

1. Create empathy: A storyboard makes the customer visible — not as a data point, but as a person with a face, a context, and an emotional experience. When your management team sees Mr. K. frustratedly putting his smartphone down on the table because the banking app shows a timeout for the third time, that is more powerful than a slide saying “3% drop-off rate in the onboarding process.”

2. Achieve stakeholder alignment: Storyboards are universally understandable. They require no expertise in process notation, no experience with service design tools, and no explanation of symbols. Every stakeholder — from the board to the claims adjuster — can read and understand a storyboard. That makes storyboards the most effective communication tool for cross-functional teams.

3. Make service gaps visible: When you tell a story, the gaps stand out. “And then… Mr. K. waits 20 minutes without knowing what is happening” is a sentence that stands out in a storyboard — but disappears in a process diagram as “Wait time: 20 min.” The narrative forces you to design even the moments when nothing happens.

When a Storyboard, When a Journey Map?

Dimension	Storyboard	Customer Journey Map
Purpose	Tell, build empathy, communicate concepts	Analyze, identify patterns, optimize
Perspective	Narrative first-person of a protagonist	Analytical top-down view of touchpoints
Format	Image sequence (6-12 panels)	Diagram with axes and layers
Emotions	Central — visible in faces and situations	Supplementary — abstracted as emotion curve
Backstage	Optional — as lower panel half	Not included (Service Blueprint for that)
Audience	Broad stakeholder audience, incl. decision-makers	Project team, service designers
Phase	Ideation, concept communication, prototyping	Discovery, analysis, optimization

Decision guide: Use a storyboard when you want to communicate a service concept. Use a journey map when you want to analyze an existing service. In practice, both complement each other: the journey map provides the analytical foundation, the storyboard makes the insights tangible.

What Makes a Good Service Storyboard?

An effective service storyboard has five elements [1] [3]:

1. A concrete protagonist. Not “the customer” but a person with a name, age, context, and a specific need. “Maria, 34, product manager at an automotive supplier, wants to use the new banking app for the first time to make a business transfer.” The more concrete the protagonist, the stronger the empathy.

2. A trigger. What sets the story in motion? What event leads the protagonist to use the service? “Maria has an invoice on her desk that needs to be paid today.”

3. A sequence of 6-12 key moments. Each panel shows one moment of the service experience. Too few panels (under 6) skip the transitions. Too many (over 12) make the storyboard unreadable and invite excessive detail [1].

4. An emotional arc. The story must show an emotional progression — from the starting situation through the low point (or high point) to the outcome. Emotions are made visible through facial expressions, body language, and context details — not through emoticons or emoji.

5. Frontstage and backstage (optional but recommended). The upper half of each panel shows what the customer experiences. The lower half shows what the organization does to enable that moment. This duality connects the storyboard with the Service Blueprint and makes organizational prerequisites visible.

Drawing Quality Is Irrelevant

This point cannot be emphasized enough: A storyboard does not need to be beautiful. IDEO states: low-fidelity prototypes invite honest feedback because they look changeable [4]. The more professional a storyboard looks, the less criticism it receives — not because it is better, but because it looks “finished.” Stick figures work. Doodles work. What matters is the clarity of the story, not the quality of the drawing.

Step by Step: Creating a Service Storyboard

Step 1: Define Protagonist and Scenario

Establish the protagonist: Who lives through the story? Use a persona from your user research or define a concrete representative. Describe the person in one sentence: name, role, context, need.

Define the scenario: What is the starting situation? What is the trigger? What is the expected outcome? The scenario forms the frame — it defines the beginning and end of the story.

Example: “Mr. Kluge, 48, department head at a mid-sized manufacturer, is using his bank’s new digital credit application process for the first time to apply for an investment loan for new machinery.”

Step 2: Identify Key Moments

Walk through the service process and identify the 6-12 moments that carry the story. Not every process step is a key moment — only those that shape the experience.

Three categories of key moments:

1. Decision moments: The protagonist must decide or act (fill out a form, choose an option, upload a document)
2. Emotional turning points: The protagonist feels something new (relief, frustration, surprise, uncertainty)
3. Handover moments: The service changes channel, responsibility, or mode (from digital to in-person, from self-service to advisory)

Practical tip: Start with the emotional turning points. Once you know where the frustration and relief lie, the panels between them almost design themselves.

Step 3: Sketch the Panels

Draw one panel for each key moment. Each panel contains:

• Image: What does the viewer see? (Protagonist, context, touchpoint)
• Action: What does the protagonist do? (1 sentence below the image)
• Emotion: How does the protagonist feel? (Visible in facial expression or as a brief thought)
• Touchpoint: Which service element does the protagonist interact with?

Drawing technique: Use a thick marker on A4 paper or sticky notes. Draw quickly and roughly. If you spend too long on a panel, you will not want to change it. Buxton (2007) recommends: “Sketches are cheap and disposable — they should be created with the understanding that they will be thrown away” [3].

Step 4: Check the Emotional Arc

Lay all panels side by side and read the story from left to right. Check:

• Does the story have an arc? Is there a progression from the starting situation through a low or high point to the outcome?
• Are the transitions logical? Are there “teleportations” — moments where the protagonist suddenly appears in a different place without explanation of how they got there? Every teleportation marks a gap in the service design [1].
• Are moments missing? Are there wait times, channel switches, or information needs that you left out?

Step 5: Add the Backstage (Optional)

Draw a second row beneath each panel: what happens in the organization to enable this moment? Which system is called? Which employee becomes active? This backstage row connects the storyboard with the Service Blueprint and makes visible what organizational prerequisites are necessary for the customer experience.

Step 6: Review with the Team and Iterate

Present the storyboard to the team and relevant stakeholders. Ask three questions:

1. “Is this story realistic? Have you experienced similar situations?”
2. “Which moment feels wrong? Where would a real customer react differently?”
3. “What is missing? Which moment have we forgotten?”

The answers to these questions are more valuable than the storyboard itself. Iterate: adjust panels, add missing moments, remove panels that do not advance the story.

Storyboard Template: Structure and Format

Basic Structure

A service storyboard follows a consistent format:

+----------+  +----------+  +----------+  +----------+
|          |  |          |  |          |  |          |
| Panel 1  |  | Panel 2  |  | Panel 3  |  | Panel 4  |
| [Image]  |  | [Image]  |  | [Image]  |  | [Image]  |
|          |  |          |  |          |  |          |
+----------+  +----------+  +----------+  +----------+
| Action   |  | Action   |  | Action   |  | Action   |
| Emotion  |  | Emotion  |  | Emotion  |  | Emotion  |
+----------+  +----------+  +----------+  +----------+
| Backstage|  | Backstage|  | Backstage|  | Backstage|
| (opt.)   |  | (opt.)   |  | (opt.)   |  | (opt.)   |
+----------+  +----------+  +----------+  +----------+

Format recommendations:

• Physical: A3 landscape, 3-4 panels per row, 2-3 rows
• Digital: Miro, Mural, or Figma with sticky-note-like frames
• Paper prototype: Sticky notes as individual panels arranged on a whiteboard (best option for workshops because panels can easily be rearranged)

Variants

As-Is storyboard: Shows the current service process as it is experienced today — with all the breaks, wait times, and frustrations. Serves as diagnosis and starting point for improvement.

To-Be storyboard: Shows the future service process as it should be — the target vision. Serves as communication tool and basis for service prototyping.

Comparison storyboard: As-Is and To-Be side by side, panel by panel. Particularly powerful in stakeholder presentations because the difference becomes immediately visible.

Practical Example: Storyboard for a Banking App Onboarding Process

Starting Situation

A regional bank in the DACH region has developed a new digital banking app. The drop-off rate during onboarding is 34% — significantly above the industry average of 20-25%. The project team has analyzed the onboarding process as a Customer Journey Map and identified the drop-off points. Now it wants to present the findings to the board and convey an improved concept. The journey map is too technical, the PowerPoint slides too abstract. The team decides on a storyboard.

The Storyboard (9 Panels)

Protagonist: Mr. Kluge, 48, department head at a supplier, long-time branch customer, wants to use the app for the first time.

Panel 1 — Trigger: Image: Mr. Kluge sits on the commuter train, smartphone in hand. A colleague next to him shows him something on his phone. Action: “My colleague shows me how he does his transfers via app. ‘Takes 30 seconds,’ he says. I download our bank’s app.” Emotion: Curiosity, slight motivation.

Panel 2 — First Contact: Image: Mr. Kluge looks at his smartphone. The app start screen shows “Welcome! Please register.” Action: “I tap ‘Register’ and see a form with 14 fields. Account number? IBAN? TAN method? I don’t have any of that with me.” Emotion: Surprise, first frustration. Backstage: System requires complete account data for identification — legacy requirement from the core banking system.

Panel 3 — Drop-off: Image: Mr. Kluge puts the smartphone in his pocket. The train doors open. Action: “I need my account statements. I don’t have them with me. I’ll do it later.” Emotion: Annoyed, but not angry — more like “not that important anyway.”

Panel 4 — Second Attempt (3 days later): Image: Mr. Kluge at his desk at home, bank statement next to the smartphone. Action: “I have my IBAN. I type everything in. ‘Please confirm via video identification.’ Video ID? Now?” Emotion: Resignation. Backstage: Regulatory requirement (GwG/AML): Initial identification requires video ID or in-person verification.

Panel 5 — Video Identification: Image: Mr. Kluge holds his smartphone up, his ID card on the table. Background: messy living room. Action: “The video ID agent asks me to hold my ID card to the camera. The light reflects. ‘Please tilt the card.’ Third attempt.” Emotion: Embarrassment (about the background), impatience. Backstage: External video ID service provider, wait time dependent on capacity.

Panel 6 — Confirmation: Image: Smartphone shows: “Your identity has been confirmed. You will receive your access credentials by mail in 3-5 business days.” Action: “By mail? I just spent 20 minutes on video identification and now I have to wait for a letter?” Emotion: Frustrated, contradiction between digital process and analog media break. Backstage: Regulatory requirement: Initial PIN must be delivered via separate channel.

Panel 7 — Letter Arrives (5 days later): Image: Mr. Kluge stands at the mailbox, holding an envelope from the bank. Action: “Finally. I open the letter. An activation code. I open the app and enter the code.” Emotion: Relief, but muted — “only took a week.”

Panel 8 — First Transfer: Image: Mr. Kluge sits on the sofa, smartphone in hand, slight smile. Action: “I enter the IBAN and amount. Approval via Face ID. ‘Transfer completed.’ That actually took 30 seconds.” Emotion: Satisfaction, quiet amazement.

Panel 9 — Verdict: Image: Mr. Kluge on the commuter train (like Panel 1), smartphone in hand. The colleague asks: “So, how’s the app?” Action: “The app is good. But setting it up was a nightmare. I won’t recommend it to my wife until they make that simpler.” Emotion: Ambivalent — satisfied with the result, frustrated about the journey.

What the Storyboard Shows That the Journey Map Does Not

1. The time structure of the experience: The storyboard makes visible that three days pass between Panel 3 and Panel 4 — and five days between Panel 6 and Panel 7. In a journey map, these are columns. In the storyboard, they are gaps during which the customer forgets about the service.

2. The emotional impact of media breaks: The switch from video ID (digital) to postal mail (analog) is a touchpoint change in a journey map. In the storyboard, it becomes visible how absurd this switch is from the customer’s perspective — and that it immediately destroys the positive effect of the video ID success.

3. The recommendation barrier: Panel 9 shows a result that appears in no quantitative analysis: Mr. Kluge is satisfied with the app, but he does not recommend it because the onboarding was too cumbersome. This insight is critical for the bank’s growth strategy.

Note: This example is illustratively constructed to demonstrate the method in a service context. The observations are based on typical industry patterns in financial services.

6 Common Mistakes in Service Storyboarding

1. Too much detail, too little story

What goes wrong: The team draws 20 panels showing every click and every form field. The storyboard becomes a visual specification document and loses its narrative power.

Why it hurts: A storyboard with too many panels is like a film that shows every step, including opening the front door and turning on the light. The story drowns in detail. Stakeholders lose attention after panel 8.

Solution: Limit yourself to 6-12 panels. Each panel must show a key moment, not a process step. Ask for each panel: “Does this panel advance the story, or does it merely show a workflow step?“

2. No emotional arc

What goes wrong: The storyboard shows steps but no development. The protagonist remains emotionally flat — they “use the service” but feel nothing. The storyboard becomes an illustrated checklist.

Why it hurts: Without an emotional arc, the storyboard generates no empathy. It informs but does not move. And a storyboard that does not move will be forgotten.

Solution: Identify the emotional low point and high point of the story. Build the storyboard around these turning points. Show emotions through facial expressions, body language, and context details — not through labels like “customer is frustrated.”

3. Over-polished drawings

What goes wrong: The team invests hours in beautiful illustrations — or commissions a graphic designer. The result looks professional but is never changed because nobody wants to “destroy” the illustration.

Why it hurts: Buxton (2007) states the principle: “Sketches suggest, prototypes describe” [3]. An over-polished storyboard signals “finished” — and stakeholders hold back criticism. But that criticism is exactly what you need.

Solution: Draw with a thick marker on sticky notes or cheap paper. If the storyboard is too beautiful to change, it is too beautiful. Jake Knapp (Google Ventures) recommends: “If you can draw a stick figure, you can storyboard” [5].

4. Forgetting the backstage story

What goes wrong: The storyboard shows only what the customer experiences — but not what the organization must do behind the scenes. The result: a storyboard that promises an ideal experience without naming the organizational prerequisites.

Why it hurts: Decision-makers see the storyboard, are enthusiastic — and only discover during implementation that the experience requires an IT project, two process changes, and a regulatory clarification. The backstage reality catches up with the frontstage promise.

Solution: Add a backstage row beneath each panel. What must the organization do for this moment to happen as shown? This row makes the storyboard honest.

5. Showing only the happy path

What goes wrong: The storyboard shows the ideal flow — everything works, the customer is satisfied, the service runs smoothly. Errors, exceptions, and frustrations are excluded.

Why it hurts: A storyboard that shows only the happy path is propaganda, not analysis. It creates false expectations among stakeholders and ignores the moments where the service can be improved the most.

Solution: Create an As-Is storyboard with the real flow (including errors and frustrations) AND a To-Be storyboard with the target vision. The contrast between both is the strongest argument for change.

6. Treating the storyboard as the end product

What goes wrong: The storyboard is created, shown to the board — and then put in a drawer. It leads to no actions, no prototypes, no tests.

Why it hurts: A storyboard is a thinking tool, not a deliverable. Its value arises not at the moment of completion but in the discussions, decisions, and prototypes that follow. Stickdorn et al. (2018) put it bluntly: “A Customer Journey Map is not a ****ing deliverable” [1] — the same applies to storyboards.

Solution: Every storyboard must lead to a concrete next action: a service prototype, a touchpoint redesign, a pilot project, or a concrete decision.

Comparison: Storyboard vs. Journey Map vs. Service Blueprint vs. Scenario

Dimension	Storyboard	Journey Map	Service Blueprint	Scenario
Format	Visual image sequence	Diagram with axes	Swim lane diagram	Text narrative
Focus	Experience of a protagonist	Touchpoints and emotions	Frontstage + Backstage	Situation and context
Emotions	Central (visible)	Present (as curve)	Optional (secondary)	Described
Backstage	Optional (lower panel half)	Not present	Central (3 layers)	Optional
Drawing ability	Helpful, not required	Not required	Not required	Not required
Stakeholder accessibility	Very high	Medium	Low (expertise needed)	High
Best phase	Ideation, communication	Discovery, analysis	Redesign, optimization	Requirements definition

Decision guide: If you want to show a story: storyboard. If you want to analyze patterns: journey map. If you want to connect frontstage and backstage: Service Blueprint. If you want to describe a situation without drawing: scenario. The strongest combination: journey map as analytical foundation, storyboard as communication tool, blueprint as implementation template.

Frequently Asked Questions

What is a service storyboard?

A service storyboard is a visual narrative that depicts a person’s experience with a service as an image sequence [1]. Like a comic strip, it shows step by step what happens, what the person feels, and — optionally — what the organization does behind the scenes. Storyboards are used in service design to communicate service concepts, build empathy among stakeholders, and make gaps in the service process visible.

Do I need to be able to draw to create a storyboard?

No. Stick figures, simple shapes, and speech bubbles are entirely sufficient. Bill Buxton (2007) emphasizes: “A sketch should provoke, not impress” [3]. The rougher the storyboard, the more willing the team will be to criticize and change it. Professional illustration is counterproductive because it creates the impression of “finished.”

How many panels should a service storyboard have?

6-12 panels is the rule of thumb [1]. Fewer than 6 panels skip the transitions and emotional moments. More than 12 panels turn the storyboard into a visual process diagram and overwhelm the viewer’s attention. Focus on key moments, not process steps.

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

A Customer Journey Map is an analytical diagram that displays touchpoints, channels, and emotions in an abstract structure. A storyboard is a narrative image sequence that tells the experience of a concrete protagonist. The journey map analyzes. The storyboard tells. Both complement each other: the journey map provides the analytical foundation, the storyboard makes the insights tangible and communicable.

Can I create a storyboard digitally?

Yes. Tools like Miro, Mural, Figma, or PowerPoint work. For the workshop, however, we recommend the physical variant (sticky notes, paper, whiteboard) because it is faster, invites iteration, and preserves the “sketch character.” Digitize only after the workshop, once the story is validated.

Related Methods

A typical sequence in service development: With a Customer Journey Map, you analyze the existing service. With a storyboard, you communicate the insights and the target vision. With a Service Blueprint, you connect the customer experience with organizational processes. With service prototyping, you test whether the experience shown in the storyboard works in practice. The overarching method selection guide is in the Service Design Methods Overview.

• Service Prototyping: The storyboard as a low-fidelity prototype — a first test of whether the service story works before investing in more elaborate prototyping methods
• Customer Journey Mapping: The analytical foundation from which the storyboard’s key moments derive
• Service Blueprint: The backstage complement to the storyboard — shows what the organization must do for the customer experience to work
• Service Design: The overarching discipline in which storyboarding is embedded as a visualization method

---

Research Methodology

This article synthesizes findings from Stickdorn et al.’s classification of storyboarding in the service design context (2018), Buxton’s foundational work on design sketching (2007), IDEO’s Field Guide to Human-Centered Design (2015), Knapp’s Sprint methodology (2016), and the film and animation history of the storyboard. The practical example (banking app onboarding) is illustratively constructed based on typical industry process patterns in financial services.

Limitations: Academic studies on the effectiveness of storyboarding in service design are rare — most recommendations are based on practitioner experience rather than empirical comparative studies. The optimal panel count (6-12) is a rule of thumb from practice, not empirically validated.

Disclosure

SI Labs advises companies on the design of services. In the Integrated Service Development Process (iSEP), we use storyboards as communication and prototyping tools to test service concepts with stakeholders. This practical experience informs the framing of the method in this article. Readers should be aware of potential perspective bias.

References

[1] Stickdorn, Marc, Markus Edgar Hormess, Adam Lawrence, and Jakob Schneider. This Is Service Design Doing: Applying Service Design Thinking in the Real World. Sebastopol: O’Reilly Media, 2018. [Practitioner Handbook | Storyboarding as service design method | Citations: 1,500+ | Quality: 88/100]

[2] Finch, Christopher. The Art of Walt Disney: From Mickey Mouse to the Magic Kingdoms and Beyond. New York: Abrams, 2011. [Historiography | Disney Storyboarding Origins | Citations: 200+ | Quality: 75/100]

[3] Buxton, Bill. Sketching User Experiences: Getting the Design Right and the Right Design. San Francisco: Morgan Kaufmann, 2007. [Foundational work | Design Sketching and Storyboarding | Citations: 3,000+ | Quality: 90/100]

[4] IDEO.org. The Field Guide to Human-Centered Design. 2015. URL: https://www.designkit.org/resources/1.html [Practitioner Toolkit | 57 design methods including Storyboarding | Quality: 85/100]

[5] Knapp, Jake, John Zeratsky, and Braden Kowitz. Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. New York: Simon & Schuster, 2016. [Practitioner Book | Day 3 Storyboarding | Citations: 2,000+ | Quality: 80/100]

[6] Nielsen Norman Group. “Storyboards Help Visualize UX Ideas.” Accessed February 25, 2026. URL: https://www.nngroup.com/articles/storyboards-visualize-ideas/ [Practitioner Article | UX Storyboarding best practices | Quality: 85/100]

[7] Blomkvist, Johan. Representing Future Situations of Service: Prototyping in Service Design. PhD thesis, Linkoping University, 2014. [PhD Thesis | Service visualization and low-fidelity prototyping | Citations: 200+ | Quality: 90/100]