E-Learning Storyboard Examples #251: Challenge | Recap
Whether you prefer scripts, blueprints, or rapid prototypes, chances are you’re using some type of storyboard to plan and organize you...
Published 6 years ago
Version 1.0
Blog Post
Thanks for this week's challenge! We use a storyboard but I'm not 100% that it is exactly what we need. Like many of you, I think I would find it less time consuming to just build and get regular reviews. I suppose that would effectively mean that I would use Storyline to storyboard, as well as build.
Anyway, I'll share what we currently use.
http://finnberrys.co.uk/Documents/Storyboard.docx
Just to put this into context, here is our process (in brief):
1. Scoping call/meeting with client to discuss and establish background, objectives, structure and other big picture details. This results in our 'high level overview', which is useful for ensuring that we all know what the purpose of the training will be.
2. Storyboard - SMEs send content in various forms and formats. Sometimes this is very clear and almost like a storyboard in its own right. Other times, it's a mish-mash of documents and images, and we have to pull it all together from scratch.
At the moment, we say that once the storyboard is signed off, they cannot add or significantly change content, without incurring further costs.
3. Build - We build in Storyline/Rise. This now inevitably involves a mass copy and paste exercise from the storyboard, which doesn't feel very efficient.
My top tips for new designers would be:
1. Try a few different ways of storyboarding and use what works for you.
2. Get a balance between what you have to do to meet company processes and not wasting your time.
3. Review the process regularly in discussion with the rest of your team (assuming you have one).
Anyway, I'll share what we currently use.
http://finnberrys.co.uk/Documents/Storyboard.docx
Just to put this into context, here is our process (in brief):
1. Scoping call/meeting with client to discuss and establish background, objectives, structure and other big picture details. This results in our 'high level overview', which is useful for ensuring that we all know what the purpose of the training will be.
2. Storyboard - SMEs send content in various forms and formats. Sometimes this is very clear and almost like a storyboard in its own right. Other times, it's a mish-mash of documents and images, and we have to pull it all together from scratch.
At the moment, we say that once the storyboard is signed off, they cannot add or significantly change content, without incurring further costs.
3. Build - We build in Storyline/Rise. This now inevitably involves a mass copy and paste exercise from the storyboard, which doesn't feel very efficient.
My top tips for new designers would be:
1. Try a few different ways of storyboarding and use what works for you.
2. Get a balance between what you have to do to meet company processes and not wasting your time.
3. Review the process regularly in discussion with the rest of your team (assuming you have one).