Storyboard (abridged) May 2017 TNT SIG webinar
•Download as PPTX, PDF•
0 likes•124 views
This document discusses using storyboarding for training development. Storyboarding involves organizing thoughts and client needs by describing the components of a course, including audio narrative, on-screen text, instructions, feedback, and graphical assets. Next steps include getting client approval of the program outline, selecting modules to work on, and holding a future meeting to choose the best authoring tool.
Recommended
Recommended
More Related Content
Featured
Featured (20)
Storyboard (abridged) May 2017 TNT SIG webinar
- 1. Training and Technology An ATD Orange County Special Interest Group Storyboarding
- 2. I’m excited to see what you’ve got!
- 3. No, that’s not right… That’s WAY off… I’m concerned this training’s a bit … two-dimensional.
- 4. The Storyboard Organize your thoughts (and the clients’!) Describes the components of the course • Audio narrative • Words on the screen • Instructions • Interaction feedback • Graphical asset description
- 5. What’s Next? Client accepts Program Outline Select modules to work on Next meeting: Selecting the Right Authorware Tool
- 6. Questions? Images and icons in this presentation designed by Freepik
Editor's Notes
- Alright: we’ve created a program outline, and got approval from our clients to proceed. Are we ready to dive into Captivate or Storyline? ANIMATE Not so fast.
- How many times have you shared your course with a stakeholder, to have this result?
- My point being: before we invest the time and energy in creating the course content, we need to organize the disparate thoughts of the project requestor, the subject matter experts, and your research into a coherent narrative. The storyboard is essentially the blueprint for the course being developed. But it’s also the opportunity for you and everyone else involved to walk through the course before we start creating it. Does the narrative flow properly? When we introduce a term or topic, does the learner have the appropriate context to understand that content? Are the facts correct? I’ve been working on a project where one subject matter expert tells me something as factual. When I document it and have the project owner review the storyboard, she asks: “Why are we doing that?” Much like my client in the previous slide saying: “That’s completely wrong.” The storyboard exposed a gap between expected process and actual process that needed to be discussed before I proceeded. Imagine investing time creating the content in Captivate, only to be told that you’re demonstrating a process that’s months old. Are the instructions clear? When something as basic as “Click Next to continue” may need to be explained for some of the learners, how are we ensuring that people know what to do during an interaction? What sort of feedback are we providing? This is a huge benefit; it allows the client to review both positive and negative feedback without attempting to answer the questions incorrectly, then going back and answering them correctly… I’ve had a client go back and forth on the quiz feedback alone. What visual assets are you going to use? While I don’t recommend spending a significant amount of time finding and including the visual assets in your storyboard (it’s a big time-suck. “Looking for the right graphic” is my primary method of procrastination), I do include descriptive phrases like: “photo-realistic image of business person, neutral expression” or “screenshot of a blank spreadsheet” in the storyboard. Or “video of CEO introducing course.” When I share a storyboard with my client, it’s easier for them to mark it up. It’s easier for me to make edits. To move things around. Additionally, client edits on an eLearning draft become problematic. They frequently view the content, have an issue, and tell me what the issue is, but not where in the content they observed the error. They tend to refer to a slide by image, not by title or number. But we can sit here and complain about our clients all day. Let’s take a look at some Storyboard examples. SHARE STORYBOARD TEMPLATE 1 Basic storyboard. Focuses on the narrative, less on visual and navigation. I use this most frequently. SHARE STORYBOARD TEMPLATE 2 Storyboard for highly interactive eLearning modules. Used frequently when the content you’re creating is scenario-based, with various branching opportunities. Focus is on the visual aspect, less on the narrative. STORYBOARD TEMPLATE 3 Powerpoint Yes, Powerpoint. Decent balance between addressing what the user will see and what the user will hear. Powerpoint allows you to create handouts where the slide notes appear below each slide. Drawback: we can get tied up in the visuals. I don’t want to be spending a lot of time selecting graphics at this time. If we’re dealing with content that’s already available, then we’re probably OK. But otherwise, we’re investing time on look and feel which will very likely change if the content has to change. Drawback: Powerpoint handouts don’t naturally create spaces, like the two Word storyboards that I shared, for navigation and feedback prompts. That’s not saying you can’t put them in, but if I’m creating any sort of branching in my modules, I don’t like trying to represent that branching in a PowerPoint handout.
- What’s next? Well, the client will need to accept the program outline that we’re submitting. Once we’ve got that confirmation, we can begin working on our own storyboards. This will give you the opportunity to review the storyboard templates we’ve seen today, and figure out which makes the most sense for you to utilize. Next month, we’ll discuss the various authorware tools at our disposal. Captivate (this will give me some time to get used to the newer version), Articulate Studio, Articulate Storyline, etc, and we’ll discuss the selection process for determining which authorware is right for a project. That meeting’s already been uploaded to the ATD OC Events calendar, so you can register today.
- Questions? Thoughts? Concerns?