eLearning Storyboards: How Much Is Enough?

eLearning Storyboards: How Much Is Enough?

eLearning Storyboards: How Much Is Enough?

Best Practices For Developing Effective eLearning Storyboards

Storyboards are defined as blueprints of the eLearning product to help the client envision what the final product will look like. The word envision leaves a lot to the imagination. The best approach is to develop a very accurate mock-up of what the final product will look like. Leave as little to the imagination as possible and have the client sign off on the design before going into development. It is much easier to make changes to a storyboard than it is to alter the development document. Here are some tips to ensure that your eLearning storyboards leave little to the imagination.

User Interface Design

The first step in developing the storyboard is to develop the User Interface (UI) in detail. The UI is the backbone of an eLearning product. UI is the form, function, and aesthetic that guides every slide within the course. The UI design should demonstrate each of the following elements.

When the UI design is complete, work with the client to get approval before moving on with the storyboard. When the UI is approved, load it into the master slides of your authoring tool. If a change is required in the UI design, it can be fixed in the master slide in turn fixing all of the other slides at the same time.

Every Slide

Yes, create a mock-up of every slide and number them. If a slide has several layers, create a mock-up of each layer and add a letter to the number i.e. 1A, 1B, 1C. Open the UI for the slide, add all of the textual information and include the following.

Congratulations! You have done a lot of work. So what is the payoff? Creating an in-depth storyboard may sound like double the work, but in the long run, it is faster and easier to solve design problems early in the process than after a round of development is complete. Handing your client a storyboard that limits ambiguity in design and function reduces revisions. Handing a complete and client approved storyboard to the developer saves time and money.

Exit mobile version