LIS 640 - Wizards

When a Wizard May Help

• Users want to accomplish a goal that has many steps (e.g., installation).
• Users lack the necessary domain knowledge.
• Users must complete steps in a specific sequence.

When a Wizard May Not Help

• The audience is too advanced.
• The wizard doesn't solve the problem (or solves a problem that users don't generally have).
• The designer wants to teach.
• There was not time to test the wizard.

Traits of Successful Wizards

• Re-entrancy (usability for changing initial choices).
• Roadmaps (users know what the wizard does and when it is finished).
• Bridging of gaps in users' understanding of how to accomplish tasks with the software.
• Clarity of inputs.
• Predictability of outputs.

Sources

• User Interface Engineering. 1997. "When to Develop a Wizard". Eye for Design. http://world.std.com/~uieweb/wiz_art.htm.

Home