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
This is a great article that explains the difference and usefulness of both the storyboard and the prototype. However I use a third method when developing my story.
1) I get my general story approved. This isn't a 'word for word' script, more a general idea of the main topics.
2) I get into a developing frenzy. Using Storyline I develop as much of the course and script and lines as I can, using the main topics of the general story. I make sure to develop everything except sound to make the course come alive to the stakeholders.
3) I then print to Word to present to my Stakeholders as a storyboard. Now they can edit everything that is included in the course with one swoop. I have always felt that getting feedback about individual items could become cumbersome to SME's and Stakeholders.
At least using this method, it is really easy to edit the stylistic choices of the course and drive home the reality of the course.
1) I get my general story approved. This isn't a 'word for word' script, more a general idea of the main topics.
2) I get into a developing frenzy. Using Storyline I develop as much of the course and script and lines as I can, using the main topics of the general story. I make sure to develop everything except sound to make the course come alive to the stakeholders.
3) I then print to Word to present to my Stakeholders as a storyboard. Now they can edit everything that is included in the course with one swoop. I have always felt that getting feedback about individual items could become cumbersome to SME's and Stakeholders.
At least using this method, it is really easy to edit the stylistic choices of the course and drive home the reality of the course.
I agree with your point 1, Terry. Depending on the circumstance (e.g. how comfortable I am with the client or content), I'll make a flowchart, with each node of the flowchart representing a screen.On each node I'll just have a title (will probably become the screen title), and a sentence or two describing, in the broadest sense, what would be covered on that screen - not how it will be represented or how it will look, but the concept(s) to be addressed. I'll usually do this flowchart in Powerpoint or Visio and, for example, a 30-minute module might have around 20 nodes describing the flow.
This high-level flowchart can usually be put together very quickly (in a few hours) and is a useful tool/step that:
1. Helps get agreement that all of the material that has to be covered is represented.
2. Helps crystalise how the navigation and chunking will hang together/flow.
3. Gives me confidence that the next stage (maybe prototype, maybe storyboard, maybe direct build) won't be too far off-piste.
This high-level flowchart can usually be put together very quickly (in a few hours) and is a useful tool/step that:
1. Helps get agreement that all of the material that has to be covered is represented.
2. Helps crystalise how the navigation and chunking will hang together/flow.
3. Gives me confidence that the next stage (maybe prototype, maybe storyboard, maybe direct build) won't be too far off-piste.