An e-learning storyboard is a structured document that maps out what learners will see, hear, and do in a course — slide by slide — before development begins. It defines on-screen content, narration, interactions, and navigation in a format the full project team can review and respond to.
Why it matters#
Storyboarding is a communication tool first and a planning tool second. Without it, misalignments between the instructional designer, graphic designer, narrator, and developer surface late — when changes are expensive. A storyboard makes the course visible before a single interaction is built, so the team can identify errors, reduce scope creep, and validate the design against learning objectives while there is still time to change it cheaply.
Your brain processes visuals 60 times faster than text. A storyboard uses that to your advantage — stakeholders understand a visual layout in seconds where they would skim past a written spec.
What a storyboard contains#
| Element | Description |
|---|---|
| On-screen text | Copy that appears on the slide |
| Narration / audio | Script the narrator will record |
| Visuals and graphics | Description or placeholder image for each asset |
| Animations | Notes on motion, timing, and sequence |
| Interactions | Branching logic, click-to-reveal, drag-and-drop, scenarios |
| Navigation indicators | Where the learner goes next; branching paths |
| Knowledge checks | Questions, response options, and feedback copy |
Two storyboard formats#
Text-based#
A table format — every element is described in writing. Columns typically cover slide number, on-screen text, narration script, graphic description, and interaction notes. Easier to produce and review without design software. Best for projects where the developer will handle visual layout.
Visual#
Slides that show the actual screen layout alongside narration notes. Usually built in PowerPoint or Google Slides. Gives the team a concrete preview of the learner experience and reduces interpretation gaps between designer and developer.
Both formats are valid. The right choice depends on team size, tools, and how much visual interpretation you can delegate.
Storyboarding tools#
The tool matters less than the clarity of the communication. Common choices:
- Google Slides / Docs — real-time collaboration; comments feature supports async review cycles
- PowerPoint / Word — familiar to most stakeholders; integrates with Articulate Storyline imports
- Adobe Captivate Draft — rapid storyboarding on iPad; tied to the Captivate ecosystem
Choose the tool your stakeholders are already comfortable reviewing in.
Storyboarding for video#
When the deliverable is a training video rather than an interactive course, the storyboard takes on additional planning responsibilities that don’t exist in slide-based design.
Attention resets must be planned at the storyboard stage. Identify where learner attention is likely to dip — typically after ninety seconds of static content — and mark where each reset will occur, what type it will be, and what assets it requires.
B-roll requirements must be identified before filming day. Every moment in the script that would benefit from cutaway footage needs to be flagged in the storyboard, along with a description of what needs to be shot. B-roll that isn’t planned before the shoot doesn’t exist at edit time.
Screen capture sections need separate scheduling. Any sequence where the video will cut to software or an application being used must be noted so that recording can be arranged independently of the main shoot.
Key facts#
- A storyboard is not the course — it is the blueprint. Its job is to surface decisions and get alignment before anything is built. Treat polish as a sign of wasted effort at this stage.
- Every design choice needs a “why”. Why is this content on screen before that? Why is it shown this way? The storyboard is where you establish and document those reasons — so reviewers can challenge them early and developers can implement them correctly.
- Show more than you tell. A storyboard should favour visuals, graphics, and interactions over walls of narrated text. If the script describes something that could be shown with an image or animation, flag it.
- Storyboarding reduces scope creep. A reviewed and approved storyboard gives the project a fixed reference point. Changes requested after approval have a clear cost and can be managed as scope additions rather than corrections.
When to use it#
- At the start of every elearning development project, before any authoring tool work begins
- When handing a design off to a developer or media specialist
- When working with an elearning team that includes roles the designer does not fill themselves
- When stakeholders need to approve the course before development investment is made
- When planning a training video — to map attention resets, b-roll, and screen capture requirements before filming