30 likes | 226 Views
Wizard. Good for automating infrequent tasks need not to be learned helping new or casual users do complex tasks by giving new users a successful first experience with the AP, encouraging htem to graduate to the regular interface not for frequent tasks or teaching users how to do a task
E N D
Wizard • Good for • automating infrequent tasks need not to be learned • helping new or casual users do complex tasks • by giving new users a successful first experience with the AP, encouraging htem to graduate to the regular interface • not for frequent tasks or teaching users how to do a task • Guidelines • make sure that you really need one • rigidity and a slow pace • if users rely on a wizard too much, indicates an overly complicated interface, not a good wizard design
Wizard Guidelines • Programming • a single secondary window with replaced contents • typical wizard components (handout) • Graphical feedback in wizards • on the left side of the window • Writing the wizard text • use simple, jargon-free language • present options as questions • provide short conceptual tips • wherever possible, suggest the actions that the user might take after finishing the task
Wizard Guidelines • Designing the flow • find the obvious route • add a roadmap • as simple as listing the steps on the first panel • putting the steps on a list reappearing at the beginning of each section, finished steps marked • Usability • test for time savings • times to complete and to learn tasks with/without the wizard • test how quickly experienced users become frustrated with the pace of the wizard and the restricted set of choices • test whether you need help buttons