When you’re in the early stages of designing and developing an eLearning course, it’s likely your subject matter experts will throw a boatload of information at you. This might include best practice documents, long email chains, links to various online resources, and poorly-designed PowerPoint decks. And if you’re like me, you can quickly feel like you’re drowning in a sea of information, which usually leaves you overwhelmed and paralyzed!
As eLearning designers (and instructional designers), it’s our job to take all of that raw content and organize it into a cohesive, engaging, and effective course. While there are many different strategies and processes for how you transform raw content into a completed eLearning course, I’ve always been a huge proponent of using a storyboard.
An eLearning storyboard is simply a document that outlines the learning content, slide-by-slide or screen-by-screen.
An eLearning storyboard is simply a document that outlines the learning content, slide-by-slide or screen-by-screen. The purpose of a storyboard is to provide your stakeholders and subject matter experts a preview of how the course will flow and how the content will be presented. The storyboard also gives reviewers the opportunity to easily make edits and change the course content before you begin development.
While this is a pretty straightforward explanation, it’s important to remember that not all eLearning storyboards are the same. eLearning storyboards come in many different formats, and when and why you use each one depends on what you need to accomplish with it.
In this post, I’ll give you an overview of the two main types of eLearning storyboards, and share tips for when you should use each in your eLearning development process.
Out of all of the different types of eLearning storyboards that you can create, perhaps the most common is a written storyboard. A written storyboard is the type of storyboard that most closely aligns with my description above: a document that outlines the learning content, slide-by-slide or screen-by-screen.
Usually, when I am drafting a written storyboard, I like to use Microsoft Word or similar software (Google Docs, etc.), and I like to include some essential elements. Some of these elements are designed to help provide a sense of organization and structure to the storyboard and other elements are intended to provide a holistic view of the course content and structure. At the very minimum, I like my written storyboards to indicate what audio narration will be included on the slide (if any), what will be presented on-screen in terms of the text and graphics, and any relevant technical notes needed for development.
I prefer to use a written storyboard with almost every project I work on, especially when there’s a lot of subject matter expert involvement. In my experience, I find that written storyboards help focus my reviewers on the course content, rather than how the course will look and feel.
Additionally, I find these types of eLearning storyboards easier to edit. For example, a small edit to how a fully-developed branching scenario works might result in hours’ worth of work for you to implement it into the design. However, when that branching scenario is just on paper, in a storyboard, making a change is just a matter of moving or rewriting some text. It’s because of this that I recommend finalizing as much of the content in the storyboard stage before you move into full development.
Unlike a written storyboard, a visual storyboard is focused not only on the course content, but also the course design. A visual storyboard is a hybrid between a written storyboard and a visual prototype.
While visual storyboards are a popular method for rapid eLearning development and iteration, they take a bit more time to get started. This is because you’re working on the course content and visuals simultaneously. Unlike a written storyboard, a visual storyboard is usually created in PowerPoint or even the actual eLearning authoring tool (i.e., Articulate Storyline) being used to develop the course.
I recommend using a visual storyboard when you’re working with reviewers who are familiar with the eLearning development process. In my experience, when using a visual storyboard, I’ve found the review process to be difficult, especially when working with stakeholders and subject matter experts who aren’t familiar with the development process. For example, when you tell your reviewers to focus on the content, they inevitably get sidetracked questioning your use of colors or placeholder images.
I’ve found that a visual storyboard or prototype works best after you’ve finalized your learning content in a written storyboard.
The Bottom Line
While there are many different types of eLearning storyboards for you to use, which one you choose to go with depends on what you need to get out of it. Use a written storyboard when you need to focus on the learning content and use a visual storyboard you’re ready to visualize your learning content.
What other types of eLearning storyboards have you used? Share your tips by commenting below!