Added by Geoff Sauer on Dec 17, 2003.
Average rating: 3.67/5.00 (n=3, std dev: 0.58)
 


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.
 
  View all 48 works by Carliner, Saul  
  View all 18 works published by Saul Carliner Studio  

Please share your rating/opinion of "Designing Wizards".
 PoorExcellent 
The link to this work seems to be broken.

Copyright © 2001-09 by the EServer. All rights reserved.Add a Work | Update this Work | Discussion Forum | Habitués