A storyboard is a tool used in training design. It outlines the purpose and content, including text, activities, media and audio that will be in the training. As the name suggests it tells the story about the training.
Storyboards are shared with clients to review and provide feedback on. They are also used by developers, that is the person who will build the training, which is why clear communication is important. Vague ideas and giving all creative license to a developer make the process difficult and adds time to the process, particularly when revisions are made.
To avoid lengthy revisions, a clear brief needs to be developed for the person creating the storyboard, which will then be passed on to a developer. The brief is essentially provide by the client, some will know exactly what they want, others not so much. Effective questioning during a training needs discussion is crucial to do this properly.
I worked on a project where I was told the end client didn’t know what the training objective was, and as a result shared very vague instructions, which were open to interpretation. The company I did the work for were also very vague, changed their vision numerous times, and made the work challenging because I believe they didn’t seek to clarify the clients needs.
A brief and a story board go hand in hand, especially when documentation and version controls are required. A storyboard is a great tool to use when developing training, and is critical particularly when developing adhoc training programs, when quick fixes are sought as training solutions.