There isn't anything magical about wizards - at least, not the ones used in the performance technology field. A wizard performs complicated computer tasks, leaving only simple, decision-making tasks to the user. Performance technologists use wizards when their intended user group doesn't necessarily need to know the steps associated with a particular task.

Some well known examples of wizards include software installation wizards and document template wizards. For example, while a person using Microsoft Word's agenda wizard answers a series of questions to supply the content, the wizard organizes and formats the content into an agenda Word document.

You'll find several examples of wizards in software programs. However, as you'll seen in additional wizard examples, wizards are finding their way online.

There are certain situations when using a wizard is ideal.

EET Article Submission Wizard

How many times have you had to reinstall software? Unless you are having problems with your computer, probably rarely. Instead of having to remember where to install files in particular directories, a wizard can perform the task automatically.

Unless you're an accounting whiz, preparing taxes can be intimidating. Now online tax preparation sites offer tools to simplify the task of performing such tasks as determining your best withholding options. See the H&R block's withholding calculator example (a form of an online wizard) as an example.

Sometimes it is more important for person to succeed in a task, or learn it immediately, than to know the tasks how's and why's. When this is the case, a wizard can perform the task initially and a person can learn how to complete the task later.

Keep these guidelines in mind when you are creating a wizard (Carliner, 1998):

Limit information on a screen. One question per wizard screen is ideal, but if some questions are related, you can place at least two or three questions on a screen.

Wizard should include 10 or less questions. The less questions a person has to answer to complete a task the better. If you have more than 10 questions consider creating another wizard and linking it to the overall wizard.

Ask for information once. If you build a wizard to collect a person's name or some other piece of information, ask for it only once. Asking people to supply the same information more than once will only annoy them.

Use easy to understand language. Avoid jargon at all costs. In most instances, your users will be novices who will not understand specific terms.

Provide previews. Allow a person to see a preview of the final product before finishing the wizard.

Users can complete task without any training. The whole purpose of a wizard is complete the task quickly with minimal knowledge from a person. Make the wizard easy enough to complete without having to train a person.

For more guidelines, see Bollaert's articles in More Information.

H&R Block's Withholding Calculator
This "wizard" calculates estimated withholdings. Do you see the gray navigational bar on the right-hand side of the wizard? This is a launchpad. A launchpad provides novices with a preview of their progress in completing a task using the wizard.

Cool Tools
Check out these wizards in the web design section of the Builder web site (http://www.builder.com). These javascripts perform complicated programming tasks for you, allowing you to easily add javascript to your website.

Bollaert, J. (2001, September). Crafting a wizard: Fifteen dos and don'ts for designing wizards that make complex tasks easier for your users. Retrieved from http://www-106.ibm.com/developerworks/library/us-wizard/?article=wir.

Bollaert, J. (2002, January). More Web-based wizard tips and tricks: Guidelines to help you develop and design your own wizards. Retrieved from http://www-106.ibm.com/developerworks/library/us-wizard2/?dwzone=usability.

Carliner, S. (1998, July). Designing Wizards. Training & Development. (pg. 62 - 63). Electronic copy. Retrieved from ASTD store at http://store.astd.org on August 6, 2002.

Wickham, D. P. (2001, November). Empowering users with launchpads: Link wizards and dialogs together to help users get through complex tasks. Retrieved from http://www-106.ibm.com/developerworks/usability/library/us-launch/?article=wir.

John Emenecker