Winter 2008

Volume 48, Number 2

.pdf Version Masthead Archives Back Next

Technicalities Home


Columns:

Message from the Editor

President's Corner

Chapter News

STC News

Features:

Storyboarding Multimedia and E-learning

Web-based Collaboration Tools

November Chapter Meeting

January Chapter Meeting


STC RMC Home

STC International Home


Storyboarding Multimedia and E-learning

Just as no builder would dream of breaking ground on a skyscraper without a detailed blueprint, a technical communicator preparing an online training course needs to plan what it will cover. A common medium for that plan is a storyboard. In this article, we introduce the concept of storyboarding, describe its goals, show an example storyboard template, and describe some best practices for storyboarding.

According to Wikipedia, Walt Disney Studios created the first storyboards in the early 1930s, for the animated short The Three Little Pigs. Since then, storyboarding has been used to design movies, websites, software applications, and even—with a nod to fellow STC RMC senior member Al Kemp—white papers. This article concentrates on storyboarding for multimedia CBT, or e-learning. In this context, storyboarding tends to be more sequential than storyboarding for websites or software applications. Where the latter form of storyboard emphasizes visual layout, branching, and hierarchy, multimedia storyboards depict images, motion, audio, data, and mouse and keyboard action simultaneously.

Why storyboard?

The goal of a good storyboard is to represent abstract concepts such as flow, structure, and emphasis in non-linear media in a linear document. An effective storyboard conveys the content you plan to cover, and your approach to covering it, so it can easily be understood by the diverse group of people who will use it:

  • Clients and subject-matter experts, who need to approve the accuracy of your content and the details of the screen graphics before programming begins.
  • Developers, who need to know details of the interactivity or the navigation controls.
  • Yourself. Having a structured format in which to present your content can help you think through what you want to say—and provide a handy reminder that you haven’t forgotten anything.

The storyboard gives the reviewer a reading experience as close as possible to the actual dynamic multimedia experience—the sights, sounds, movement, interactions, and general learning approach—on a static piece of paper.

A simple storyboard

Figure 1 shows a storyboard page for a CBT Marc wrote about air pollution.
Storyboard
Figure 1: Storyboard page for a CBT

Plenty of off-the-shelf storyboarding tools exist, but this example was developed in Microsoft Word. While not a favorite of technical communicators, Word, through its table feature, does an adequate job. For this example Marc set up the document in landscape layout to resemble a typical computer screen, and then simply copied and pasted a blank form into each new page of the document. Using Autotext entries can make this process even more efficient.

In this example, each page represents one “screen” in the CBT, and each Word file covers one module (1-2 hours of e-learning). We generally try to keep a single Word file to 100 screens or less. If your training is graphically intensive, the files may become too big to email. In this case, you can distribute them through a website, project wiki, or FTP site—or just divide your training into smaller chunks.

The template includes the following regions:

  1. The screen ID (upper left) of this screen, which denotes Module 1, Unit 2, Topic 3, and Screen 3.
  2. The screen layout, which shows each graphic, video, or text element. It’s amazing how much detail and fidelity you can achieve with Word’s drawing tools—line, textbox, color, and shapes—plus a little patience. Of course, your final program may feature more sophisticated graphics created in Adobe Photoshop or Illustrator. If so, your storyboard should specify the graphic file name.
  3. The Dialog field, which contains the content for any audio. Either your voice talent can use the storyboard as a script as is, or you can compile these into a separate document. Again, the storyboard should specify the audio file name.
  4. The Interactivity field, which describes any user interactivity, such as clicks or text entry, and how the program responds. (In this example, the user does not interact with the screen shown.)
  5. The Presentation Order field, which specifies the sequence of any animations, pop-ups, or visual or sound effects.
  6. Finally, the Control section, which shows the navigation controls on each screen: Next, Previous, Exit, Help, and so forth.

Some Closing Tips

  • For readability, try to keep everything on one page.
  • If your design includes more than one screen type (objectives, content, quiz, scenario), specify the screen type in your template.
  • Provide a “how to read” section for reviewers. Even the savviest reviewers will initially have a hard time understanding what they are looking at or what they’re supposed to review. A labeled sample page, with explanations like those above, will help them with this learning curve.
  • When submitting a storyboard, consider how comfortable your reviewers are with editing documents online. In many cases, you may prefer that they enter their comments directly into the storyboard, with Track Changes enabled. While this method helps reviewers focus their comments, some reviewers may have difficulty using Word’s editing and table features. If so, consider having them provide comments on a hard copy of the storyboard, via an email, or in a separate document.

    In some cases, you may even consider a live, roundtable read-through of the storyboard. While time-consuming and logistically challenging, a group review can help your team iron out difficult areas, which may prevent greater delays down the road.

Developing a storyboard before jumping full-speed into development is an investment of time that will pay off, by giving your clients, SMEs, and developers a clear idea of what you plan to do… before you do it!

About the authors

Marc Lee has 10 years of experience developing CBT for government agencies and private businesses. For projects that required storyboarding, the template shown above has successfully conveyed his instructional approach and gained approval for the next phase.

John Endicott has used storyboards to create training for a diverse spectrum of clients, including New York Life, the NASD, and Hewlett Packard. He takes an iterative approach to the technique, working closely with developers to fine-tune a generic format until it meets the needs of the project at hand.

Please feel free to contact the authors if you have questions about this technique and how it might apply to your own job.

Marc Lee
STC RMC Sr. Member
Chapter President 2004-2005
Independent CBT Consultant
marc@mlmultimedia.com

John Endicott
STC RMC Sr. Member
Chapter Vice-president 2007-2008
Senior Instructional Designer
jeendicott@yahoo.com


Back Technicalities Home Next

© Copyright 2008
Rocky Mountain Chapter, Society for Technical Communication; all rights reserved.
Standard disclaimers apply.