My 48 Hour Rapid e-Learning Challenge

June 19, 2008

One person. One course. 48 hours.

Time to put rapid e-learning to the test. I recently got an assignment to create an e-learning course and it needs to be done fairly quickly. I need to get it done in a few weeks and I don’t want to spend more than 6 hours a day on it. On the downside, the course goals are a little fuzzy, there isn’t much existing content, and I am writing the content and developing the course on my own. On the positive side, I have a lot of autonomy to design what I want.

Here’s the plan:

I will use the Articulate suite to build the course (a tool I have used for one previous course). Because of the tight timeline, I will rely mostly on relatively simple approaches but (hopefully) engaging instructional strategies that a single, non-programmer/action scripter can do alone. To that end, I’m drawing a lot of inspiration lately from blogs like Cathy Moore (e.g. how to add emotional impact ; dump the drone), Tom Kuhmlan’s Rapid E-Learning Blog, and Jane Bozart (especially her Better Than PPT book).

Goal: A fully functioning course in 21 days (and no more than 48 hours). By “fully functioning” I mean ready for beta testing, not necessarily final release.

  • Days 1-5: content outline, design/strategy, storyboard in PPT, document my processes.
  • Days 6-10: finalize storyboard, write screen content and script, identify graphic/media
  • Days 11 – 15: Build all course screens and interactions
  • Days 16 – 20: Record audio, test, release beta for review
  • Day 21: Kaizen (improvement) – Review process for what worked, what didn’t. Look for areas of waste and inefficiencies, Improve and document process for next project.

Along the way:

In addition to developing the course, there are a few other things I will do:

  • Document lessons learned and best practices.
  • Track metrics and track data to help with future improvement projects.
  • Develop project management and process documents that can be replicated.
  • Update this blog minimum three days per week: include discoveries, general experience, review of software, etc.
  • Search out other blogs, product support site for help, and post questions as needed.

That’s it….ready, set…..

Do you have any ideas for getting set up and started on a WBT rapidly? War stories, best practices or things to avoid….any comments are appreciated. Comment here or e-mail me.

Advertisements