Storyboard Templates for E-Learning #48: Challenge | Recap
Challenge of the week
This week your challenge is to share an example of your preferred e-learning storyboard, blueprint, or scr...
Published 11 years ago
Version 1.0
Blog Post
Late entry, I know! I'm going back through challenges to re-energize my creativity.
This is a storyboard template that I created for a specific client. The client had very clear branding and ideas about 508 compliance. I started with their presentation template, took out things that didn't apply to e-learning, added e-learning specific stuff like the course introduction section and developer notes, and then created a slide for every activity we could use (and variants of them!). This worked well for the project because we had hundreds of courses that had to follow the same rules and include the same components. Additionally, the team member who wrote the storyboard may or may not have been the person who developed the Storyline file. So, developing activity styles and components up front saved us a ton of time. There is a corresponding Storyline template and instructions for converting storyboards into WBTs using the template. This method wouldn't work for every project, but made this one very efficient.
http://s3.amazonaws.com/ElearningChallenges/048/TEMPLATE_Storyboard.potx
Personally, I like using PowerPoint to storyboard. My clients are visual, non-technical people, so it works well. That being said I don't hand over a PPT file. In my experience that's a recipe for disaster. I print the Notes view as a PDF and provide that.
For interactivity, I include developer notes. What will happen when the user hovers, clicks, drags, etc. What will the result be? What's the intention?
Here are my top three storyboard tips for new course creators:
1) Know your audience. In the case of storyboards, that's your SME or client. Are they visual or technical? Develop your storyboard in a format that allows your audience to focus on what they need to review.
2) Consistency in visuals, specifically if you are using PowerPoint. Graphically, you want a consistent look and feel. But you also want the visuals in the storyboard to be as close to the final product as possible.
3) Not every word in the audio has to be represented on screen. Not every on screen element needs to be address in the audio. The audio and visual elements should complement each other.
This is a storyboard template that I created for a specific client. The client had very clear branding and ideas about 508 compliance. I started with their presentation template, took out things that didn't apply to e-learning, added e-learning specific stuff like the course introduction section and developer notes, and then created a slide for every activity we could use (and variants of them!). This worked well for the project because we had hundreds of courses that had to follow the same rules and include the same components. Additionally, the team member who wrote the storyboard may or may not have been the person who developed the Storyline file. So, developing activity styles and components up front saved us a ton of time. There is a corresponding Storyline template and instructions for converting storyboards into WBTs using the template. This method wouldn't work for every project, but made this one very efficient.
http://s3.amazonaws.com/ElearningChallenges/048/TEMPLATE_Storyboard.potx
Personally, I like using PowerPoint to storyboard. My clients are visual, non-technical people, so it works well. That being said I don't hand over a PPT file. In my experience that's a recipe for disaster. I print the Notes view as a PDF and provide that.
For interactivity, I include developer notes. What will happen when the user hovers, clicks, drags, etc. What will the result be? What's the intention?
Here are my top three storyboard tips for new course creators:
1) Know your audience. In the case of storyboards, that's your SME or client. Are they visual or technical? Develop your storyboard in a format that allows your audience to focus on what they need to review.
2) Consistency in visuals, specifically if you are using PowerPoint. Graphically, you want a consistent look and feel. But you also want the visuals in the storyboard to be as close to the final product as possible.
3) Not every word in the audio has to be represented on screen. Not every on screen element needs to be address in the audio. The audio and visual elements should complement each other.