E-Learning Storyboard Examples #251: Challenge | Recap
Whether you prefer scripts, blueprints, or rapid prototypes, chances are you’re using some type of storyboard to plan and organize you...
Published 6 years ago
Version 1.0
Blog Post
Hello,
I'm currently working on that question to scale bigger projects.
1) How do you define scripting, storyboarding, and prototyping? Which method do you prefer?
a) Spontaneous answer
I would say scripting is the first step, storyboarding the second and prototyping the third if we want the FULL process. Of course it always depends on the time and budget you have. These steps allow us to validate we share the same vision with the client.
b) Deeper thoughts
Scripting/Storyboarding/Prototyping could also be independant from one another. And we could use different methods to get results before starting the development.
Storyboard > Usually if it's the same person that do the design and the development the storyboard could be done through Articulate 360 to gain time in the process.
Scripting > Could be done with after a meeting with the client/SME as a brief design with graphics/schemes
Prototyping > Could be done with the client as a Sprint Design
2) Do you use different types of storyboards? When do you use each?
I would use either PTT if the project needs a "template" and guidance for further projects or Articulate if I'm in charge of development.
3) How do you storyboard interactivity?
UI of the slide + comments on a box in the slide ? Using a specific color for interactivity ?
4) What are your top three storyboard tips for new course creators?
* Make sure it's understandable for who it's adressed (client? Developer?)
* Make it visual (explain clearly how it works, what is the logic underneath)
* If it's required by the project, add a script or graphics that explains the storyboard from a big picture standpoint (game design graphics are a good example)
I'm currently working on that question to scale bigger projects.
1) How do you define scripting, storyboarding, and prototyping? Which method do you prefer?
a) Spontaneous answer
I would say scripting is the first step, storyboarding the second and prototyping the third if we want the FULL process. Of course it always depends on the time and budget you have. These steps allow us to validate we share the same vision with the client.
b) Deeper thoughts
Scripting/Storyboarding/Prototyping could also be independant from one another. And we could use different methods to get results before starting the development.
Storyboard > Usually if it's the same person that do the design and the development the storyboard could be done through Articulate 360 to gain time in the process.
Scripting > Could be done with after a meeting with the client/SME as a brief design with graphics/schemes
Prototyping > Could be done with the client as a Sprint Design
2) Do you use different types of storyboards? When do you use each?
I would use either PTT if the project needs a "template" and guidance for further projects or Articulate if I'm in charge of development.
3) How do you storyboard interactivity?
UI of the slide + comments on a box in the slide ? Using a specific color for interactivity ?
4) What are your top three storyboard tips for new course creators?
* Make sure it's understandable for who it's adressed (client? Developer?)
* Make it visual (explain clearly how it works, what is the logic underneath)
* If it's required by the project, add a script or graphics that explains the storyboard from a big picture standpoint (game design graphics are a good example)