One of the fundamental things drummed into people who have embarked down the path of the eLearning developer is the need to start your development project with a detailed and well planned storyboard. From this document/PowerPoint/flowchart/drawing, your content can be planned, screens can be devised, interactions envisaged and source material can be sculpted so as to reduce cognitive load and therefore improve knowledge transfer and/or application.

The development of a Storyboard is seen as a fundamental task which takes time to get right and can make or break the content for the audience and the designer.

eLearning has certainly followed through with this belief in the compulsory nature of the Storyboard, making it a standard line item on any build estimate.

Lion StoryboardHowever I question this logic. Is a Storyboard required for all content development? Especially in the light of today’s amazing content development tools, such as Articulate Studio or Storyline 2, do we really need to build a complete static plan for the content under development, or can we just go straight to building direct from the source materials?

To me this approach makes perfect sense for a number of reasons:

  1. It cuts down on the overall project time. If you storyboard content into PowerPoint, you still have to develop all of the content slides, mock up the interactions and re-engineer the text and audio to work for an online audience. Then once you have sign off you have to rebuild all of the same screens again. (A bit like double handling).
  2. It lets the client see a living and breathing version of the content at the first review.
  3. With a storyboard, you may have 2 or more review cycles prior to commencing a build and even once it is signed off and the first actual content version is delivered things can still be lost in translation, where reviewers are unable to imagine interactivities until they actually see them working.
  4. Source materials are often highly dynamic in their actual content, most due to normal business pressures when policies, wording, branding and even SME subjectivity can change on a week by week basis. In such an environment a project may spend weeks or months in a constant revolving feedback loop before it can even be signed off.
  5. Screen design can be signed off much more efficiently. By showing a client a branded set of indicative content slides, built from their own source materials and including intended interactions allows the client reviewers to judge the content and interactive design based on a tangible output.
  6. It saves the client money. Bottom line is that it is faster to develop initially and much quicker and easier to review and these factors together mean that the client still gets the same great output at up to half the cost.

Now before eLearning designers and developers light their flaming brands, take up their pitchforks and form a ravening mob out for justice, please let me say that Storyboarding is a fundamental tool for the development of eLearning and there are times when it is not just beneficial but also crucial.

Getting a quality eLearning outcome with any of the following would be either very difficult to near impossible without a storyboard:

  • When building a complex branching scenario when user decisions can lead them through a complex path in the content and when decision feedback and consequences can be felt at any stage of the content journey
  • When there are custom design elements that require several iterations
  • When the source material provided is provided in such a technical format that time needs to be spent with the SME to de-code it then to reconstruct it in eLearning appropriate format. Mostly so that the SME can see how the information flows and links.
  • Where the navigational elements of the course allow the learners to select multiple paths through the content to reach a common goal.

The above is not an exhaustive list but there are certain times when a storyboard is an absolute must. Lion Co required an extensive branched scenario using a comic style design theme to show their team how to have successful challenging conversations. The solution was to storyboard in Microsoft Powerpoint (see image above), which allowed for a fast and effective client review of the content (they made changes to the conversation transcript themselves and text) and then we simply imported the file into Articulate Storyline to build the course.  But, how often really are courses like this developed? We estimate around three projects in every ten.

The rest of the time, the eLearning development tool themselves, such as Articulate Studio or Storyline 2 give us the ability to design and build a living breathing functioning storyboard from the outset.

B Online Learning develops all of our client’s content to their exact specifications, where that includes storyboard development or not. What we always do when commencing a development project is to give the client an honest appraisal of what is actually required.  For us it’s all about what is the best possible solution, not just ticking the boxes and racking up the invoice line items.

Ben Saunders About Ben Saunders
For the past 10 years Ben has been immersed in the world of learning and communication (and training and development), from planning and design to build and implementation, from both the client and vendor perspectives. His experience bridges the gaps between business expectation, technology and learning theory, importantly this allows Ben to translate and articulate business needs into defined learner outcomes. He has experience with various LMS implementations including Moodle, Docebo, Plateau, SABA, DOTS as well as bespoke solutions. Ben is a Solutions Designer and Certified Articulate Trainer with B Online Learning.