I appreciate your explanation of text-based storyboarding before prototyping. It makes a lot of sense to strip down the content to words and objectives, scope and sequence, before presenting visuals.
Love this! I learned this lesson the hard way recently by asking for content feedback on a draft PPT that included design elements. As you can imagine, the SMEs could not focus on content, no matter how much I pushed, and I realized the mistake I made.
Great tip! I like the idea of getting them to first focus on the content before worrying about visuals. Attractive visuals won’t matter if you have bad content that doesn’t achieve the learning objective(s). I’ll be remembering this tip as I move forward through learning about ID. Thank you!
Hi Tim, I'm a newbie to ID. I now see that I am experiencing as you say doing rapid prototypes and the SME's are commenting on the wrong things. Thanks, I will back up and use a text-based storyboard going forward on this project.
Really enjoyed your reasoning behind having a text only Storyboard... I had never quite thought of it that way and now I can see that that is exactly where my SME's end up focusing - on the look and feel of the placeholder button! Really great video. Thanks!
I am a sucker for a beautifully designed storyboard, but I can see your side very clearly- content is so important and it may get lost in the details for sure. If a learning object is going in the course, I do like to see the cover sheet or first slide as a graphic inserted in the storyboard to see if I like the look of the material.
Makes total sense. I also think it depends on who you're working with. If you're working with stakeholders who are familiar with the design and development process, then I think it makes sense to deliver a storyboard that is more visual.
Great video. I use to create a storyboard in Word, but create one in Power Point. You could probably use both. A storyboard in Word to give your stakeholders a quick review. Get feedback and change things - quick. Another in Power Point to rapidly prototype before you actually build.
I'm a big fan of storyboards that look like the course, provided in one way or another. My main preference is to build (or mock up in PPT) a prototype of the look and feel and the main interactions. I just find that the Word scripting/design docs never speak to the client. But once they see what the course will look like and how the interactions will go, they're fine to then help flesh out content in Word. Seeing is believing! :-)
very well explained! i agree its best to just show them a written storyboard. ive had the same experiences as you if i show them visuals.
Till recently, I've not done any storyboarding, but after this explanation, I'll make it an essential phase.
I appreciate your explanation of text-based storyboarding before prototyping. It makes a lot of sense to strip down the content to words and objectives, scope and sequence, before presenting visuals.
Love this! I learned this lesson the hard way recently by asking for content feedback on a draft PPT that included design elements. As you can imagine, the SMEs could not focus on content, no matter how much I pushed, and I realized the mistake I made.
Great tip! I like the idea of getting them to first focus on the content before worrying about visuals. Attractive visuals won’t matter if you have bad content that doesn’t achieve the learning objective(s). I’ll be remembering this tip as I move forward through learning about ID. Thank you!
Thanks, Brandy! I'm glad you enjoyed the video! Thanks for watching!
Hi Tim, I'm a newbie to ID. I now see that I am experiencing as you say doing rapid prototypes and the SME's are commenting on the wrong things. Thanks, I will back up and use a text-based storyboard going forward on this project.
Excellent video Tim! I have used Storyboards for a number of years. It's necessary for all of the issues you mention in this video.
Thanks for watching!
Really enjoyed your reasoning behind having a text only Storyboard... I had never quite thought of it that way and now I can see that that is exactly where my SME's end up focusing - on the look and feel of the placeholder button! Really great video. Thanks!
Thanks for watching, Emma! I'm glad you found the video helpful!
Emma that is exactly what I thought. Excellent idea and now I know the reasoning behind it, this is my go-to for SME's.
Before I saw this, I used index cards with each concept on a separate card. Then I laid them all out and grouped them into a logical flow.
I am a sucker for a beautifully designed storyboard, but I can see your side very clearly- content is so important and it may get lost in the details for sure. If a learning object is going in the course, I do like to see the cover sheet or first slide as a graphic inserted in the storyboard to see if I like the look of the material.
Makes total sense. I also think it depends on who you're working with. If you're working with stakeholders who are familiar with the design and development process, then I think it makes sense to deliver a storyboard that is more visual.
Great video. I use to create a storyboard in Word, but create one in Power Point. You could probably use both. A storyboard in Word to give your stakeholders a quick review. Get feedback and change things - quick. Another in Power Point to rapidly prototype before you actually build.
Thanks! I think the best storyboard tool is the one that works for you and your reviewers...so if that's PowerPoint, great!
I'm a big fan of storyboards that look like the course, provided in one way or another. My main preference is to build (or mock up in PPT) a prototype of the look and feel and the main interactions. I just find that the Word scripting/design docs never speak to the client. But once they see what the course will look like and how the interactions will go, they're fine to then help flesh out content in Word. Seeing is believing! :-)
Nice job, Tim!
Thanks, Michael!
On Point... Nice work Fam!!!
Thanks
u read my mind
Tim, do you have any samples of a storyboard layout you would give to your SMEs?