Storyboarding to Perfection

After all the discovery work for computer-based training (CBT) is completed and the full parameters of the instruction are defined, the design process begins. Storyboards are considered the most versatile and useful method for completing this. The end product is a detailed description using both images and text to hand off to the developers. Before handoff, clients have a thorough knowledge of the solution and can affirm that it is appropriate. When handed off, a well-detailed storyboard decreases questions by developers and the likelihood of rework in the development process.

Storyboards are often ignored due to the time involved in the process and a lack of knowledge about them. What needs to be remembered is that, like in discovery, storyboarding can save massive amounts of resources during the development process. Just as discovery clearly defines design, the design clearly defines development.

Storyboards include:

• Path of the instruction
• Navigation showing the flow of the course
• Interactions the user will encounter, including links
• Learning content
• Conditional changes in the user interaction
• Display to demonstrate that expected standards for the course are integrated into the design

It is not necessary to use expensive storyboard generating programs to develop them. Programs such as Word or PowerPoint work just fine. The magic is in the “story” they tell. They document the user’s experience from beginning to end and define all the data that is displayed, captured, and manipulated.

The Process
The use of storyboards enhances “what if” thinking. The designers better see the course from the end user’s perspective. While going through the process and evaluating the results for approval, many “what if’ questions can, and usually do arise. This in itself is the true value of taking the time to go through this process. Conditions relevant to the workings of the course are made obvious and documented. Many earlier assumptions are challenged and sometimes altered or completely changed. This is the best place for that to happen.

Start the storyboards where the user begins. Follow the user’s path. If an interaction by the user can trigger more than one event to happen, different conditions are present and require documenting. Something as simple as closing the course can trigger multiple conditions. For example, if the user selects to close the course before completing a pre-assessment, the course may trigger a pop-up alerting the user that completion is required when they return. The alert may even include instructions for the return. The same user, having completed the required elements may be forced into completing a survey before they close the course. Each condition needs its own storyboard sequence. Other sequences will refer to them. The button that allows the user to close the course, shown in other sequences, will include text for the developers that this action is conditional and to refer to the conditional storyboards for closing the course.

It is easy to see how vital storyboards are to the development process. The process allows for the designer and the client to confirm that all intentions were met. If one condition is not thoroughly documented, valuable resources are lost in the development process.