What's your review process like?

Curious: What's your review process like, in general (or even, what's your ideal review process)? 

Generally, I work with the SME on a ppt until the last possible moment. I don't tend to storyboard, since the ppt is the storyboard. We tinker with the narration in the slide notes, I build out the look of the slides as much as I can in ppt, include notes on animation or layers in text boxes off to the side in the slides. Once the content it approved, I move it into storyline, which is generally about when the narration is recorded. There's another round of review after audio is synced with the Storyline project, repeat until perfected.

But I'm curious about what other people do. What's the value of using a storyboard vs ppt? Do you prefer to build out the course in Storyline, and if so why?  I'm always open to improving my procedures and would love to hear how other people do it. Cheers!

10 Replies
Arturo Aguilera

Katie,

PPT offers the option to share the storyboard with SMEs where Storyline storyboards would be very difficult to share (especially with SMEs that are geaographically disperse). I follow your process, but what add is an internal peer review. This review is for anyone that is not familiar to the content and may provide feedback on things that I have missed. Ideally, look for another instructional designer with great attention to detail. Of course, welcome all feedback and try no to justify your design decisions, but rather think if it would make sense to make the change.

I hope this helps.

Cary Glenn

I build the course in Storyline and will then publish it to html and word. I send the files to the SME and my manager for approval, sometimes I will also send it out to other people within the company for testing. I like the system it is quick and streamlined. \

I have had times where I had to send courses out to a SME, the SME's manager, a technical writer, another developer, and my manager. That was unwieldy, especially because I had a different style of design and development than existed in that group. 

Cary Glenn

Sometimes, I do a rough draft in word. Sometimes, I'll jot down subject headings on sticky notes and then shuffle the information around to find the best way to present it. Usually, I will write the narration in the notes section of Storyline. Then, I'll publish in Word, do an edit there, and then copy and paste the new narration back into Storyline.

I am lucky, I develop Health, Safety, and Environment training, and some technical training. Much of the content is available in the HSE manual, or in legislation. I also have SME's in the same office as me so I don't have to chase them down.

Nicole Legault

Hey Katie!

Great topic and question, thanks for posing it here This reminded me of a blog post I put together a few months ago that has a section about what Review Process people use when working with their SMEs to develop e-learning: Forums Compilation> Working with Subject Matter Experts. You might be able to glean some insights from some of the past forum discussions that are listed there! =) 

Cindy Pandke`

We have been working on our process review over the last couple of years.  We now use a document we call the Design Document (project details, project team, approvers, reviewers, reasoning, scope, out of scope, risks, dependencies, tools, deliverables/dates, sign-off).  Our initial meetings gather any information for this document that we haven't already received.  We do have a 4 phase sign-off. 

Phase 1 - sign off on the design document

Phase 2 - sign off on the storyboard

Phase 3 - sign off on the module

Phase 4 - sign off on LMS testing and launch

We usually do not proceed to the next phase until complete sign-off is received (via email usually).  Project team must have a project lead that will be our main SME.

Initial storyboard can come through PowerPoint, Word or Storyline depending on the complexity of the project and if you are doing the instructional design or both the instructional design/development.  We also have a graphic designer on staff.

First pass is general outline, then screen by screen detail is added. 

Sign-off on storyboard is received

Black & white prototype is created (either in PPT or in Storyline - some use Articulate Studio '13)

Then full graphic design is done

SME and project team will get several interactions (back-forth process for accuracy of content/interactions).  Once we are close to having a completed module, we go through a full SME review followed by a user testing (test for timing, learning ability, functionality).

Sign-off on module is received

We then do full LMS testing for accuracy of status completion

Sign-off is then received from LMS Administrator.  We are then scheduled to launch. 

We only launch new modules on the last week of each month.

Formalizing the process is working for us and keeps everyone on the same page.

howard pearson

My process initially involves a lot of mapping. 

I action map to establish the objectives and then submit them for sign off. 

  • I then create a content map to give them a visual overview of the course, it's chapters and running order and then a design map to give them a feel for the design. 
  • I then storyboard including thumbnail images and submit for sign off. 
  • Once that is signed off I build. 
  • Once built i publish on my website and also on word doc. I send them a link to the course and the document and ask them to record any comments on the document in red.