14 August 2016
14 August 2016
Honestly, there was a period of time that I was thinking of "Storyboarding" as a waste of time! One could jump in and transfer requirements into the contents and make adjustments on the go, quick and easy and everybody was happy. And things could be the same, if it wasn't for the "Storyboard Life Cycle" technique.
Storyboards can play various roles in different phases of your eLearning project. "Storyboard Life Cycle" technique can turn "only a storyboard" into an amazing asset of any eLearning project. For this purpose almost any storyboarding creator software can be used (I personally use Powerpoint Storyboarding, which is a great tool). Here are a few examples:
UAT process is a pain and one of the main reasons is the templates used for this purpose. They are boring and most of the time not clear enough for the users so someone must guide users through the process, which is defeating the whole purpose of the "user testing". Using "Storyboards" for this purpose and adding enough annotations and tips wherever needed, with the result that must be expected can make an interesting Visual UAT template. Users also love it as they can easily compare the implemented system to the scenario they are viewing on the visual UAT template.
Again, this is something that takes some time to develop, but you actually already have it. Making just a few modifications can turn your Visual UAT template (originally the "storyboard") into a perfect graphical user manual.
I hope you will find this useful.