prompting them only when they must make a decision. A wizard involves a structured series of dialogues that applies users’ responses to produce a result, such as installing software or writing a business letter. It is different from a tutorial and other online information in that it helps users accomplish a task, not teaches them how to do it. A wizard is a performance support tool; that is, it supports users as they perform a task. Because the system performs some of the work, it can seemingly bring a user to a higher performance level in less time than conventional training methods. But the cost can be a dumbing down of tasks. Users perform tasks without understanding them and aren’t aware of the underlying decisions. As a result, users may not be able to perform tasks if the system is down. You should use a wizard to build performance only when people can perform a task without knowing all of the steps.
Carliner, Saul. Saul Carliner Studio (2003). Design>User Interface>Wizards
Allen describes the uses, benefits, and drawbacks of 'wizards'--utilities that help users perform particular tasks.
Allen, Kristen. Intercom (2000). Design>User Interface>Wizards
There are 22 readers currently online: 0 registered users and 22 guests. Register.

![]()
![]()


![]()
![]()
![]()