Rapid e-Learning Storyboard using PowerPoint

I've seen a lot of messages in the past few weeks about how people create e-Learning storyboards. My favorite method when building scenarios or course mockups is to use PowerPoint. I've created a template based on the method I use and am releasing it to the community. Take a look and let me know what you think. 

Here are a few things I like about this approach:

1. It's a much more visual method than a traditional Word-based storyboard

2. It's set up so that you naturally tell a story

3. The layouts allow you to swap out backgrounds very quickly

4. Most of the assets you need are on every slide (just off the viewing area)

5. You can move very quickly into production

I look forward to your feedback. Enjoy!

11 Replies
Michelle Reeder

Does anyone else have a sample or screen shots of a PPT storyboard they would mind sharing? I have to create one and I need something simple yet robust enough to have a place to describe content, voice over, interactions, etc. I want to be able to put the images right on the screen.

I am curious how in depth to go with describing animation/interactions or to use create or prototype them right in the storyboard?

Any and all input is appreciated. Up until now I have only done rapid prototyping but it can be very arduous for extensive content changes.

Thanks.

Michelle

Sheila Bulthuis

I can't post them because they have client-proprietary content, but I can try to describe what i do in this sort of situation:  On the screen I have images or descriptions of images; if the courses is image-dependent in terms of content, I try to have at least rough mockups of the images themselves.  Also text if that will be on the screen as well.  In the Notes section I put the narration script.  Below the script i make programming notes - but really minimal and simple, and only for stuff the client might actually care about at this point. (Not like the storyboards back in the day where an ID did a full detailed SB and then handed it off to a programmer!)  So it might be things like "the learner will be able to click the different people to hear their examples" or "the bottom half of the image won't appear until the narrator says [whatever]]".  But only for the stuff that I think might matter to the client (depends on the client) - I usually don't include too much info about animations, etc. at this point, but i do usually include a brief note about interactions, although I don't build them all the way out.

Although I love rapid prototyping, I've found this approach really helpful when the client doesn't seem quite sure about their content, or when they tend to have a lot of content changes/edits.  If i'm building the course in Storyline, I do all this in storyline and export.  It's a nice middle ground between true storyboarding and true rapid development - at least in my opinion.

Hope that's at least a little helpful!