If you’re new to e-learning, you may have heard people throw around terms like storyboard and prototype without daring to ask the question: What’s the difference? Well, don’t worry, we’ve got...
Published 10 years ago
Version 1.0
Blog Post
I'm with Nicole. I always build my storyboard in Storyline (for elearning at least) so I can use it as a prototype.
Here's my steps:
1. I can get approval on a design right up front by building a few slides with the look and feel and colors I want. Maybe some additional colors for stakeholders to choose from. I insert some of the content as well.
2. I build more slides with content. Not only can the SMEs check the flow, but I think it cuts down on my work. I don't have to copy, paste and format a Storyboard in Word. I do it all in one place.
3. I can make in-line changes when talking to SMEs.
4. I publish to Word when I want SMEs to have full editing capabilities avoiding the separate Storyboard again.
5. Also, I use publishing to Word for developing job aids or guides.
Here's my steps:
1. I can get approval on a design right up front by building a few slides with the look and feel and colors I want. Maybe some additional colors for stakeholders to choose from. I insert some of the content as well.
2. I build more slides with content. Not only can the SMEs check the flow, but I think it cuts down on my work. I don't have to copy, paste and format a Storyboard in Word. I do it all in one place.
3. I can make in-line changes when talking to SMEs.
4. I publish to Word when I want SMEs to have full editing capabilities avoiding the separate Storyboard again.
5. Also, I use publishing to Word for developing job aids or guides.
You are so right Troy. We follow exactly the same process as you for every development job that we undertake. One of the biggest problems with elearning is that most client don't know what they want until they see it, so we develop the prototype at the quote stage. We go tot the effort of building a 5 slide concept with client logos and branding. From a sales perspective this works very well as they feel like the course is already theirs. It does take a bit of effort, but we secure 95% of the quotes we put out because of this effort. Not only that but when you 'win' the job it is very easy for my designers to jump into the project and know form the outset what is expected of them. Funnily enough we don't 'storyboard' at all anymore (we have been in the development business for 10 years). We have found that scripting works far better than a storyboard. So we write a 'script' that take the learner on a journey, then build the graphical assets, animations and functionality to suit the 'story'.