I believe storyboarding is a waste of time. I prefer to develop the course in storyline and do any edits if required by the client. What are your thoughts? Do you think they are important? Why or why not?
When you are developing courses upto 10 slides or pages, yes you can think so but imagine when there are courses containing 40-50 pages, Indeed you will need to develop SB.
It will help you to outline your idea/content flow. Diving directly in to development may seams time saving but it will narrow up scope of enhancement somewhere. And after developing everything if there is any drastic change come from other end, you will need to redo most of the work. So its better have SB's in place.
Hi Parashuram, Storyboarding can be an important step of the process, depending on what you are trying to do. If they are short courses you can probably get away with just rapid development as you are doing. We create storyboards because:
We need to tell a story and there is enough content that we need to think it through and define it out in detail.
Our clients need to approve the story and the text before it is created (because if we put a ton of hours into a project and it isn't the direction the client wants or the content is incredibly technical and we aren't a subject matter expert, we might have to start over if the client isn't satisfied, losing lots of time and money).
We use the storyboard to define the voice over script and have it approved as well.
We use storyboards as a checklist so we can make sure we have told all elements of the story.
If others are working on the project, the developers need a storyboard to bring the course to life. Without a storyboard, we would have an inconsistent mess of a course.
There are other reasons, but generally, "storyboard" is a vague term and I do recommend writing down your plan of action, content, knowledge checks, etc... if you want to turn it into a formal storyboard, you can if it is needed.
I agree with @Phil - I like to prototype what the course will actually look like (with smaller images, text, no audio, etc.) and describe how to slide will progress in the slide notes, along with the voice over audio. It makes so much more sense to me than to storyboard in PPT or Word, then rebuild the entire course in the tool.
I think too, the clients get a better visualization of the entire flavor of the course - the look and feel with the content.
I also agree with @David! All of these bullet points can be covered in a prototype too. If you're handing the storyboard off to a developer, then yes a very detailed storyboard would be needed. I do it all, so it maximizes my workflow and efficiency.
I will say too that while we storyboard we create design concepts and on bigger projects we may mockup a little of the course or a knowledge check so everyone can get a good feel for the direction. We tend to do bigger projects and have a development team. Smaller projects can be roughed together in Storyline and it becomes the high level storyboard.
I will say too that while we storyboard we create design concepts and on bigger projects we may mockup a little of the course or a knowledge check so everyone can get a good feel for the direction. We tend to do bigger projects and have a development team. Smaller projects can be roughed together in Storyline and it becomes the high level storyboard.
I am totally agree with David. Small project can be developed directly in development tool. But in case of large projects where multiple people are involved, SB will be great guideline to get desired output.
9 Replies
Hi RK,
Welcome to community.
When you are developing courses upto 10 slides or pages, yes you can think so but imagine when there are courses containing 40-50 pages, Indeed you will need to develop SB.
It will help you to outline your idea/content flow. Diving directly in to development may seams time saving but it will narrow up scope of enhancement somewhere. And after developing everything if there is any drastic change come from other end, you will need to redo most of the work. So its better have SB's in place.
I try not to ever use Storyboarding, I much prefer the rapid prototyping model I find it the most efficient and cost effective way to work.
Hi Parashuram,
Storyboarding can be an important step of the process, depending on what you are trying to do. If they are short courses you can probably get away with just rapid development as you are doing. We create storyboards because:
There are other reasons, but generally, "storyboard" is a vague term and I do recommend writing down your plan of action, content, knowledge checks, etc... if you want to turn it into a formal storyboard, you can if it is needed.
Hope that helps.
I agree with @Phil - I like to prototype what the course will actually look like (with smaller images, text, no audio, etc.) and describe how to slide will progress in the slide notes, along with the voice over audio. It makes so much more sense to me than to storyboard in PPT or Word, then rebuild the entire course in the tool.
I think too, the clients get a better visualization of the entire flavor of the course - the look and feel with the content.
I also agree with @David! All of these bullet points can be covered in a prototype too. If you're handing the storyboard off to a developer, then yes a very detailed storyboard would be needed. I do it all, so it maximizes my workflow and efficiency.
I will say too that while we storyboard we create design concepts and on bigger projects we may mockup a little of the course or a knowledge check so everyone can get a good feel for the direction. We tend to do bigger projects and have a development team. Smaller projects can be roughed together in Storyline and it becomes the high level storyboard.
Great discussion! Thank you to everyone for chiming in with their opinions and input. :)
Thanks all for your thoughts.
I am totally agree with David. Small project can be developed directly in development tool. But in case of large projects where multiple people are involved, SB will be great guideline to get desired output.
This discussion is closed. You can start a new discussion or contact Articulate Support.