Storyboarding

Processing a Customer Refund Storyboard (Google Slides)

What is Storyboarding? It is the process of visually planning and organizing a learning experience before development begins.  Some typical components can be slide layout, narration/script, visuals, interactions, assessment ideas, and directions for the developer.

Why use a Storyboard? 

• Clarity for stakeholders

• Efficiency

• Consistency

Not all situations warrant a need for a Storyboard, but if used it can help clients and SMEs visualize the learning experience before development. Storyboards encourage questions and ensures content, visuals, and instructional strategies are aligned with learning objectives. When using a Storyboard, it can helps maintain a unified tone, design, and pacing across modules that may be a part of the build.  

When in the learning process does Storyboarding happen? When Storyboarding is a part of the design process, it occurs after the needs analysis and design document or outline is approved. Storyboarding occurs before development begins in tools like Storyline, Rise, or other LMS/authoring platforms and often accompanies or follows scriptwriting, depending on the process. 

How is Storyboarding used by teams? Storyboarding is seen as a collaboration tool among instructional designers, subject matter experts (SMEs), graphic designers, and developers, and often as a sign-off checkpoint before development. Storyboarding can also be seen as a communication tool for aligning with voiceover talent or animators if needed. 

What tools are used? In the above example, Google Slides was used. Other tools can be PowerPoint, Word, Google Docs, Excel, or specialized tools like Storyline’s Story View. Figma is often the tool of choice if a prototype needs to be built.

*Storyboards vary by organization—some are high-fidelity with visuals; others are simple text documents. Flexibility is key depending on the project needs and team preferences, and the organization.