The Storyboard, Used Well
A blank page is a luxury.
Most projects don't get one.
If you build courses, campaigns, or video content for a living, you already know the real work happens before anyone opens Storyline, Rise, or Premiere.
This course teaches you how to use The Storyboard, the template you just bought (or are about to), to plan e-learning, marketing videos, or any sequenced visual content with the discipline of a working ID and the speed of a designer who knows exactly what each field is for.
The course is organized around ADDIE (Analyze, Design, Develop, Implement, Evaluate) because that's the spine most instructional designers and content marketers already work from. Each lesson maps to a phase, so by the end you'll have built a real storyboard slide and know exactly where it sits in your production process.
First, a quick hello — then click a lesson on the left, or hit begin.
Why storyboard at all?
The cost of fixing a slide is small. The cost of fixing a finished module is enormous. Storyboarding is where you make cheap mistakes on purpose.
The storyboard is the blueprint stage of a learning or video project. It sits between the kickoff call (where you got fuzzy goals) and the build phase (where you commit hours of design and recording time).
Where it lives in ADDIE: click a phase
Notice what the template asks for first: not the visual, not the script. The narrow left rail demands Slide, Module, Title, Objective, the administrative and strategic fields. That order is intentional. It's the storyboard quietly forcing you to do ADDIE in sequence.
1. Which of these is a measurable learning objective?
2. The storyboard's Objective field should hold…
Anatomy of the template
Hover or tap each field. Each one is doing a specific job, and most people fill them in the wrong order.
The Script with Action/Timing bar runs full-width across the bottom for a reason: voiceover or on-screen copy is the longest piece of writing on any slide, and it deserves the room. We'll spend Lesson 03 just on this field.
Here are five pieces of one real slide, jumbled up. Drag each card into the field where it belongs.
Writing the script
The Script field is where most storyboards quietly fail. Here's how to write one that a developer or video editor can actually build from.
A good script line tells the reader three things at once: what the learner hears, what's happening on screen, and roughly when. Compare:
That's the difference between a storyboard that gets approved and one that triggers a re-write loop. The format that holds up is:
These four voiceover lines belong to one 24-second slide. Drag each line into the time slot where it plays.
The visual column
The big white box on the right. It is not a finished design. It's a description of one.
You don't need to be an illustrator to fill the Visual field. You need to be specific enough that the person building the slide doesn't have to guess. Three things make a visual brief usable:
- A composition note: left/right/center, full-bleed, split-screen, etc.
- A content note: what's actually depicted (a chart, a person, a UI mockup, an icon set)
- A state note: is anything animated, layered, or revealed in pieces?
- A source note if it exists: stock photo ID, brand asset name, or "to be illustrated"
Tap each item to mark it understood.
A brief is build-ready when a designer could make it without asking a single question. Drag each one into the right bin.
Build a slide
Your turn. Fill in a slide using the actual template structure. Try the example, or write your own. Your work stays in this browser.
Review & iterate
Before you send the storyboard to a stakeholder, run it through this checklist. Tap each line as you confirm it.
- Every slide has a single, measurable objective, not a topic.
- Module and Slide numbers match the project plan and tell a clear sequence.
- Scripts have quoted VO and time cues, not paraphrased intent.
- Visual descriptions name composition, content, and animated states.
- Notes capture accessibility (alt text intent, captions) and any source credits.
- A non-team-member could read any one slide and know exactly what to build.
When you've ticked all six, you're ready to hand off. The storyboard becomes a contract: stakeholders sign off here, before a single screen is built. That's how you avoid the eight-week rebuild.
You're the instructional designer on a phishing-awareness module. The deadline is tight. Your choices decide how it plays out.