Using Storyline to storyboard projects

Interesting topic. I’ve done my storyboarding right in Storyline for my last two elearning projects at Langevin Learning Services and it’s worked great for me.

Disclaimer: I do the instructional design, storyboarding and development for the e-learning, so the amount of people involved, and the tools they are familiar with themselves, are something to take into consideration when choosing your storyboarding tools.

I always do my up-front task analysis and writing in Word; that’s where I do all the editing and content organizing. Then I storyboard in Storyline. I move “chunks” of text from my Word document onto the slides in Storyline, and I put basic shapes and placeholder images. I will even do some basic linking just to make sure all the functionality I want will work out.

When the Storyline storyboard is finished I know what each slide will have on it (content wise) and how the course will flow. And then, the REAL time-saver, is that I will just create a copy of my storyboard file and develop my course right from there.  This means all the text, shapes and image placeholders are already there, I just have to style, add animations and ta-da!

Very interesting! I usually do all of my scripting in a MS Word document. I have a standard/simple template that I regularly use (here) to write all of my content. This is nice when working with SMEs, as it keeps them focused on the content and prevents them from getting hung-up on visuals, etc.

In the past when I’ve presented my content in a storyboard/wireframe format, the business partner(s) struggle looking at it as a draft. Meaning, they aren’t able to see that what I am showing them is NOT how the final product will look.

So, I typically keep my reviews of content (narration) separate from my reviews of slides (the visual stuff). It’s what works for me.

Hi, David: I used to do detailed Word-based storyboards (see attached), and then one day, it hit me:

"Dude, clients dig like 85% percent of the storyboard, so why am I going though all the extra time formatting, copying and pasting, etc., etc..." Sort of reminds of the aphorism about writing about music: "Writing about music is like dancing about architecture." (This quote is often attributed to Elvis Costello, but most likely is more the idea of Martin Mull (but I digress))

So now I rapid prototype, meaning, I build the key slides and activities in Storyline (VO and everything) and send to client and basically say, "Are we cool, so far?"

I do something similar to Tim. I have an outline document that is used to show the narration, describe interaction, and show how it alligns to the objectives. The client reviews this before I start building in storyline.

After the outline is approved, I jump right into development and skip the storyboard step altogether. If there is an interaction that I think needs more input from the client, I'll create a rough version for them to review.

One of the beautiful things about Storyline, in my opinion, is that it saves so much time because you don't have to complete a full storyboard.

Note: I do both the design and development for my courses, so this process works for me. I can see how if you are handing off development that it might need some storyboarding.

Much the same as Nicole - and I would like to add that once the first batch of text/script have been added into Storyline from there onwards I use the amazing translate feature to edit during the development and review phases. Which accepts formatting alternations as well as text changes.

http://learn.articulate.com/reviewer-edits-with-translation-feature/

Like others here, I am responsible for the whole process - design through to implementation.  I've found that prototypes work better with my SMEs than storyboards did, so I prototype in Storyline.  It's a basic product - aimed at getting the SME to focus on the content and flow.  If there is a particular interaction I want them to see I will include it  without anything fancy. If they like it then it's done - no additional development to do.  This method gives them a good idea of how the course will flow for the learner and the SME  focuses on what's important at this stage - the content.  I've found that it's been pretty effective at weeding out the 'nice to know' content too.  Once edits are noted I can develop the course and save lots of time. And, when the SME sees the first version with design elements added it's not completely new to them.

I've had a change of heart around storyboards. I used to use powerpoint, but am going to go directly to SL for rapid prototyping on next project to try it out. For SME review, I'm testing the publish to word feature, but have changed the format to a table as attached. Also, publishing a working version in scormcloud for clients to see how the interactions works.

Has anyone used this workflow? If so, share your pitfalls!

Thanks,

Holly

Holly, I like that... but where do you put the narration script (if you have one)? 

My usual workflow is slightly different:  I do an "initial storyboard" review where the narration script is pretty fleshed out, and the screen content is in a "draft" state - it's sketched out but there are lots of placeholders for images, etc.  Interactions aren't built, but are described in very general terms. At this point I just publish out to Word, with the pictures of the screens and the Notes (narration script) below them - but I like the idea of a table.  Any notes are on the screen in a color-coded box, or in the Notes section in italics/bold.  Then the reviewers make their edits/comments using Track Changes.  Once I go through this process to get the content nailed down, then I build everything out and have them review a functional version. 

Often there's another storyboard review in between, depending on how solid/stable the content was in the first review.  And sometimes, especially for new clients, I'll do a functional prototype at the very beginning, so they can see what to expect in terms of functionality, player, etc. and we can test in their LMS.

Good point Sheila - I'll add narration script in the notes and include that in the print. My current process is clunky and I'm hoping that moving to SL will make that smoother. The sample I used was Monste's template, so it looks more polished than it would actually be! 

Similar to what April describes, I have an instructional approach document that links the learning objectives to elearning specs in a table and sometimes include a sort of flowchart to that document to show how the course will progress as a first pass. Then move to the rapid prototyping in Storyline without a storyboarding step. 

For those that do this (especially if you are external), how do you manage the review cycles? What do the client's actually "sign off" on?

Truth be told, I think I'm looking for the silver bullet!

Hi Helena - it's a work-in-progress, but this is what I documented and continue to evolve. I find for clients that I'm not doing the early parts of the design process face-to-face, trying to show them how it works visually is helpful. If Storyline printed out the scene view, I think we could do the whole thing in SL with little supplemental development tools. For production purposes, I'm using the staging area of either Studio or Storyline fairly heavily. If I'm doing the work myself, it's less of an issue, but working with subcontractors necessitates more documentation.

Hope this helps

Holly

...of course love feedback from anyone in the forum on the doc, with suggestions or any other tips you've got.