Sep 24, 2009

Storyboard vs. Stakeholders, Round 1

I led a storyboard review meeting with several of the stakeholders of a "using e-mail" project I am working on. The feedback was very good and was a reminder as to why you review the storyboard before starting development.

I had split the course into two sections: 1) e-mail policies and legal concerns; and 2) simple etiquette. As seems to happen in many of the review meetings I have, the discussion didn't go in the direction I thought it would. I thought discussion would center around the content contained in each slide (which it did eventually). Instead, if started with questioning the organization of the project into two sections. I was pleased to see this topic come up because it is good to catch significant contextual issues early in the project. Without context, learners will be confused about the purpose of the training.

While one suggestion to combine the two sections into one section was appealing (and would be acceptable). The decision was made to keep the sections separate but to try to answer the question "how does this relate to e-mail" in the policy section more obvious for the learners.

It turns out that I did not have to make significant changes to the content of the storyboard. But there were significant changes to the context in which the learning experience will occur. That is good to know before starting development.

What are some of the things that show up at your storyboard review meetings?

Sep 19, 2009

It's not Voodoo, It's JavaScript

Have you ever wanted to use JavaScript in Lectora? There are a couple of tricks you'll need to know. Check out my post It's not Voodoo, It's JavaScript on the Integrated Learning Services blog.

Sep 16, 2009

Storyboard and Blogger's Block

I'm writing a storyboard for a course I'm designing. Although I'm more of a web developer than an instructional designer I'm stepping in to fill a need at my company. I am a little bummed that it takes time away from the development side of things. However, I really enjoy using my creativity to come up with a way to teach a topic that is engaging and helps the learner make memory connections to the content. I'm using PowerPoint to layout the flow of the course using a storyboard format. The first slide in my storyboard template contains the following note:
  • The web-based self-paced course should not be designed to behave like a PowerPoint presentation.
  • Use this template as a place to outline the course, course interactions, and indicate sequencing. Each page should show what learners will see, hear, and do.
  • This storyboard will serve as the playbook for all the members of the team during development.
  • Use the notes section for development notes and to indicate feedback the learner will receive.
These are the most important things I want to remind whoever is writing the storyboard. Do you use similar reminders? What's on your list?

FYI: It appears I've had blogger's block for the last couple of months. But instead of trying to write through it, I just stopped making posts to this blog. I will try to blog through it in the future to avoid large gaps without a new post. :(