HOWTO Build Effective Just-In-Time Web-Based Training

Author: Harlow Pinson
Last Updated: 02/25/2005 11:15 pm

Summary

This HOWTO describes an approach to developing web-based just-in-time training (JIT) and provides some useful links and examples.

Details

Mark Salisbury's Question:

"What are differences in approaching the design of a web-based "just-in-time" (JIT) course as opposed to developing a stand up course?"

In answering, we should first determine which approach is more appropriate for delivery to a given audience:

In what domain is web-based JIT training most effective?

In procedural domains, where a task is clearly defined and relatively short.
In fuzzy domains, where a task clearly defined but open to interpretation and discussion.
Example: Learning to upload a file to a web portal.

In what domain is stand-up training most effective?

In a procedural domain, where tasks are long, complicated, poorly defined, and open to discussion.
Examples: Learning to use the Dreamweaver HTML editor to create a small business website.

What does "effective" mean?

Effective, in regards to:

Successful (measurable) end-user task performance;
Low development costs;
Short development time;
and adaptability to procedural change.

Assuming that a JIT web training approach is called for...

Set a goal, objectives, and design and modify training as appropriate.

I informally and occasionally formally use the following development methodologies:

Evolutionary Design approach (also know as the cascading or waterfall design approach);
Design Patterns;
Modified ISD for setting the goal and the objectives, modified as appropriate for the selected domain;
and, Rapid Prototyping.

Only then, and not before, choose a technology appropriate for delivery.

Web Toolkit for delivering JIT training for procedural domains:

HOWTO
- A HOWTO is a web-document that describes a sequential process or procedure.
FAQ
- Stands for Frequently Asked Questions. A FAQ is a web document that summarizes questions about a subject that are asked on a regular basis and that have clear answers. The format is question and answer, and the document evolves over time.
Web Conferencing
- A web-browser-based presentation, controlled by a presenter, and pushed to client participants, who in addition to seeing the presentation live, participate in real-time chat with the presenter and other participants. Scary if you like control.
- Examples: Macromedia Breeze, WebEX
Blog
- A Web Log, or "Blog", containing journal entries by a presenter, arranged in chronological order, that Blog readers may or may not be able to comment on. Blogs use text. graphics, audio, and video to make their points.
- Example: Philip Greenspun's Blog

Web Toolkit for delivering JIT training for fuzzy domains:

WIKI
- A WIKI is a collaborative web-environment for informally sharing knowledge on a topic. All users have the ability to add, edit, or delete anything.
- Examples: WikiPedia, the WikiWikiWeb.
Forums
- Forums are threaded topical dialogs that participants willingly subscribe to. Once subscribed to a topic, participants are notified by email of responses to that topic.
- Examples: Chiff and Fipple Uilleann Bagpipe Forum, Toyota 4Runner Forum.
Chat
- Real-time text messaging between two or more users. Peer-to-peer file sharing and email are integrated into the best chat systems.
- Example: AOL Instant Messenger, GAIM, IRC Chat.

Technologies I generally do not use for JIT training:

Multimedia technology:

Flash, Authorware, Toolbook, Director, etc... Training development with these tools is too expensive, time consuming, and the results are relatively inflexible in regards to fast and cost effective change.
Development with these tools requires highly specialized (expensive) developers.
Delivery of training built with these tools requires proprietary architectures at the browser.

Case Study: The HOWTO

A HOWTO is a web-document that describes a sequential process or procedure. For example, instructions on how to post an item to a shared web calendar. Think of a cookbook recipe. For example:

HOWTO Set Preferences (in the Plone Content Management System) (Requires login.)

Typically, a HOWTO is text-only, however it may be augmented by graphics, audio, and video. For example:

http://www.yotatech.com/showthread.php?t=43186&highlight=rebuild

The written style of a HOWTO document is friendly and informal.

A HOWTO is short.

A HOWTO is accurate. Procedures have been tested by the author and at least on other person, and revisions are made as needed.

A HOWTO evolves. It is not static Procedures may change over time, or simply need correction.

Writing a HOWTO implies a commitment to update for the life of the HOWTO. Take comments seriously and fix your incorrect procedures!

A HOWTO conforms to web standards (HTML). It easy to update and change using nothing more complicated that an HTML or text editor.

A HOWTO has a consistent format. Templates are very useful for producing consistent looking HOWTO documents. A HOWTO typically follows a simple format, which includes minimal version control:

Title
Author(s)
Author(s) email contact information
Date written or last modified
What the HOWTO applies to (for example, version 1.0 of software x)
Summary
Procedure
Other
References

User comments may be incorporated into the HOWTO dynamically. This is very effective for identifying less than clear instruction. For example:

http://zope.org/Documentation/Books/ZopeBook/2_6Edition/InstallingZope.stx

A HOWTO may be made available in one or more languages, using internationalization technologies.

A HOWTO may be proprietary, or made available under open source licensing (free as in speech) licensing.

Exercise: Create a HOWTO

Task: As a class, in small groups, or individually, create a written HOWTO on a topic of your choice. The format of the HOWTO should allow reuse as a template.

Credits
• Making a Difference!

New Comix (juxtoposition of images and words...)
• what a quiet stiff
• Cat Garza
• Electric Sheep
• Demian 5
• Modern Tales
• Scott McCloud

Exits
• The Late Session
• Irish Step Dancers of New Mexico
• The Session
• Chiff and Fipple
• Concertina.net
• O'Neill's Music of Ireland and Allan's Irish Fiddler
• Shanties and Songs of the Sea
• Zope
• Plone
• Nissan Versa Forums
• Yotatech 4Runner Forums
• KLR 650 Forums
• Sherline
• Reddit

Forums
• Uilleann Bagpipe Forum
• Poststructural Whistle Board
• Concertina Makers