Blog Post
TroyGreer2
10 years agoCommunity Member
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.
- LeeCorbett10 years agoCommunity MemberYou 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'.
- NicoleLegault110 years agoCommunity MemberVery helpful tips, Troy! Thanks for sharing. It can be quite insightful just to hear how someone else approaches the storyboard process. So Troy, do you include functional navigation in your prototype when you say SMEs can check the flow? Just curious!
- TroyGreer210 years agoCommunity MemberYes I do, but mostly just the click through kind so they can get to the end.
Sent from my iPhone
- Mohammad-Hassam10 years agoCommunity MemberVery Helpful. Thanks for sharing Troy. I think exporting prototype in word is much better way to present your client at first place.
- LiLi-f2eafff5-c5 years agoCommunity MemberJust curious: Have you got your content draft completed before your storyboard? In another words, do you develop your content directly during your storyboarding with functions/navigations?
I am reviewing a storyboard version of the training, but the scripts and screens don't agree. It left out some bullets/images on the screen or with different order as the content shown on the screen. It was very difficult to follow the content.
I don't want to make too many comments that sound negative to the quality of the design, but I don't like to compromise with the quality of the content, either. Have you had any experience working with different vendors like this?
Thanks.