How to storyboard an eLearning course

A storyboard is the bridge between the learning design and the authoring tool. It shows what the learner will see, do and receive as feedback before time is spent polishing the final course.

It is especially useful when an SME, designer and developer need a shared picture of the course. A good storyboard makes decisions visible early, when they are cheap to change.

Confirm the audience, performance problem and measurable learning outcomes first. Then identify the evidence learners must produce and the essential content needed to support it.

If you storyboard before these decisions, the document often becomes a prettier version of the source material rather than a learning design.

• Screen, page or section identifier
• Purpose and linked learning outcome
• On-screen copy or content summary
• Visual or media direction
• Learner action or interaction
• Feedback and branching behaviour
• Accessibility notes
• SME/source reference
• Developer or author notes

You do not need every field for every project. Use enough detail to remove ambiguity without turning the storyboard into a second authoring tool.

Imagine a short course teaching managers how to respond to a suspected phishing email. One outcome is: “Given a suspicious message, identify the safest next action.”

Section: Suspicious invoice scenario. Content: realistic email with sender, link and urgency cues. Action: learner chooses from four responses. Feedback: explains the risk in each choice and reinforces the reporting route. Accessibility: email text is available as structured text rather than an image alone.

Notice that the storyboard describes a decision and feedback, not simply “show slide about phishing signs.”

A useful pattern is context → model → practice → feedback → harder practice → assessment → job aid. Not every course needs this exact sequence, but learners usually need more than explanation followed by a final quiz.

Place practice close to the knowledge it uses, then revisit important decisions later to strengthen retrieval.

Ask SMEs to review accuracy and realism, not typography. Give them focused questions: Is this the decision people actually face? Is the wrong option plausible? Is any critical step missing? What would an experienced employee do here?

Resolve major content and branching questions before building. Keep a decision log when reviewers disagree.

A storyboard is build-ready when every section has a purpose, content supports an outcome, interactions have defined behaviour, assessment logic is clear and unresolved SME questions are visible.

Then move into authoring and treat the storyboard as a design reference, not a prison. Small improvements discovered during prototyping are normal.

Continue with the complete eLearning course creation guide.