Provide Effective Feedback and Guidance and Assistance
Download as PPTX, PDF5 likes2,557 views
This document discusses providing effective feedback and guidance in user interfaces. It covers acceptable response times, dealing with time delays, blinking for attention, and using sound to provide feedback. It also reviews different types of guidance and assistance, including preventing errors, instructions or prompting, help facilities, contextual help, task-oriented help, reference help, wizards, and hints or tips. The types of guidance aim to help users complete tasks and troubleshoot problems through step-by-step instructions, references, and brief contextual information. Design guidelines are provided for implementing each type effectively.
Provide Effective Feedback and Guidance and Assistance
- 1. STEP 9 Provide Effective Feedback and Guidance and Assistance Angga Nugraha (G64124001) Didi Rachmadi (G64124023) Feri F Silaen (G64124074) M.Beben Priana (G64124033) Tri Puguh Santoso (G64124014) 1
- 2. Topics In this step, the following feedback topics are discussed: • Acceptable response times. • Dealing with time delays. • Blinking for attention. • The use of sound. This will be followed by a review of guidance and assistance, including: • Preventing errors and problem management. • The types of guidance and assistance to provide are : o Instructions or prompting. o A Help facility. o Contextual Help. o Task-oriented Help. o Reference Help. o Wizards. o Hints or tips. 2
- 3. Providing the Proper Feedback Response Time : • Less than 1 or 2 seconds. • 2 to 4 seconds. • 4 to 15 seconds. • Greater than 15 seconds. • Constant delays are preferable to variable delays. 3
- 4. Acceptable Response Time Regarding Response Time : • The optimum response time is dependent upon the task . • Satisfaction with response time is a function of expectations. • Dissatisfaction with response time is a function of one’s uncertainty about delay. • People will change work habits to conform to response time. • Constant delays are preferable to variable delays. • More experienced people prefer shorter response times. • Very fast or slow response times can lead to symptoms of stress. 4
- 6. Web Page Download Times Page Downloading : • Maximum downloading time should be about 10 seconds. • Images should be: o Small o Lean. o Reusable. o Contain pixel height and width dimensions in a tag. • Use thumbnail images to preview larger images. • Use simple background images. 6
- 7. Web Page Download Times(cont.) Thumbnail Image 7
- 8. Dealing with time delays Button click acknowledgement – Acknowledge all button click by visual or aural feedback 8
- 9. • Waits up to 10 seconds – “busy” signal >> Hourglas • Waits of 10 to 1 minute – Longer than 10 s to complete >> Rolling barber’s pool, progres indicator percent completed message, etc Dealing with time delays(cont.) 9
- 10. • Waits over 1 minute – Present estimate – Display elapsed time message – When completed present acknowledgement that it is completed >> tone – If operation is very time – consuming, allow users to start new activity while waiting and breaking operation into subtask and providing progress indicator Dealing with time delays(cont.) 10
- 11. Subtask progress indicator Dealing with time delays(cont.) 11
- 12. Invisible operations – Operation not visible to the user is completed, present acknowledgement >> message, tone Dealing with time delays(cont.) 12
- 13. Progress indicator – Long rectangular bar – Dynamically fill the bar – Fill it with a color from left to right or bottop to up Dealing with time delays(cont.) 13
- 14. Percent complete message – Indicate the percent of the operation that is complete Dealing with time delays(cont.) 14
- 15. Elapsed time message – The amount of elapsed time that the opartion is consuming – Useful if • The length of the operation is not known • Long time to complete Dealing with time delays(cont.) 15
- 16. Web page download – For page requiring download time greater than 5 second, give user thing to do while waiting Dealing with time delays(cont.) 16
- 17. Blinking for attention • Attract attention by flashing an indicator when application is inactive but must display a massage to the user. – If window, flash the title bar – If minimized, flash its icon Active Inactive 17
- 18. • Provide an additional massage indication (one or two beeps) – Useful if: • the window or icon is hidden • The user attention is frequently away from the screen Blinking for attention(cont.) 18
- 19. • Display the message – When the application is activated – When requested by the user Blinking for attention(cont.) 19
- 20. Use of sound • Always use in conjuction with a visual indication • Use no more than 6 different tones • Do not use – Jingle or loud signals • Use tone consistently – Unique, similar tone for similar situation • Frequencies 500 – 1000 Hz 20
- 21. • Allow to user adjust volume or turn off • Use sounds sparingly – Annoying to any people – Possibility will be ignored – Are not reliable • Some people are hard of hearing Use of sound(cont.) 21
- 22. • To minor and obvious mistake • When something unexpected happens • Whe a long process is finished • Where visual attention is direct away from the screen Use of sound(cont.) 22
- 23. Preventing Error Error and Slip Studies have found error rates in commands, tasks, or transactions as high as 46 percent. Errors can be classified as slips or mistakes. • A slip is automatic behavior gone awry. • A mistake results from forming a wrong model or goal and then acting on it. 23
- 24. Detection an Error • For conversational dialogs, validate entries as close to point of entry as possible • Leave window open • Maintain the item in error on the screen • Visually highlight the item in error • Display an error message in a window • Handle errors as gracefully as possible • Use auditory signals conservatively Preventing Error(cont.) 24
- 25. Prevention an Error • Disable inapplicable choices • Use selection instead of entry controls • Use aided entry • Accept common misspellings, whenever possible • Provide a common action mechanism • Before an action is performed, - Permit it to be reviewed - Permit it to be changed or undone • Provide an automatic and continuous Save function Preventing Error(cont.) 25
- 26. Correction an Error • At window-level validation, use a modeless dialog box to display an error list. - Highlight first error in the list. - Place cursor at first control with error. - Permit fixing one error and continuing to next error. • Always give a person something to do when an error occurs. - Something to enter/save/reverse. - A Help button. - Someone to call. Preventing Error(cont.) 26
- 27. • New users must go through a learning process that involves developing a conceptual or mental model to explain the system’s behavior and the task being performed. • Although it is desirable that the human-computer interface be so self-evident and intelligent that people never experience difficulties, this goal will not be achieved in the foreseeable future. Providing Guidance and Assistance 27
- 28. Instructions or Prompting • Instructional or prompting information is placed within the body of a screen. • It may take the form of messages or other advice, such as the values to be keyed into a field. 28
- 29. • Inexperienced users find prompting a valuable aid in learning a system. Instructions or Prompting(cont.) 29
- 30. • Experienced users, however, often find prompting undesirable. It slows them down, adds noise to the screen, and may reduce the amount of working information that can be displayed at one time. Instructions or Prompting(cont.) 30
- 31. • Because instructions or prompting can easily create screen noise, be cautious in placing it on a screen. Instructions or Prompting(cont.) 31
- 32. Help Facilities • The overall objective of a Help facility is to assist people in remembering what to do. • Its benefits include improving the usability of a system. • Typical methods of invoking Help include through a typed command, by pressing a Help key or button, or by selecting a Help option from a multiple-item menu. 32
- 33. • Kind The two most common reasons people use Help are: - Confusion exists about something located on the screen, and - information about a specific function is needed. Help Facilities Guidelines • Training Inform users of the availability and purpose of various types of Help. 33
- 34. • Availability If no Help is available for a specific situation, inform the user of this and provide directions to where relevant Help may exist. Help Facilities Guidelines(cont.) 34
- 35. • Structure The Help response should be as specific as possible, tailored to the task and the user’s current position. When accessed, the Help facility should be aware of the kind of difficulties a person is having and respond with relevant information Help Facilities Guidelines(cont.) 35
- 36. • Interaction A Help facility should be retrievable simply, quickly, and consistently by a key action, selection, or command. Help Facilities Guidelines(cont.) 36
- 37. • Content - Minimize Help’s length. - Provide step-by-step interface procedures to assist the user with specific problems. - Provide procedural demonstrations of interface procedures to aid quick learning of simple operations. - Provide information to help users select between multiple interface methods. • Style. Provide easy browsing and a distinctive format. Often the exact location of information needed to answer a question cannot be definitely established. Help Facilities Guidelines(cont.) 37
- 38. • Consistency. The Help design philosophy should be consistent with the philosophy used in other parts of the system. • Title. For easy identification, place the word “Help” in all Help screen titles. Help Facilities Guidelines(cont.) 38
- 39. Contextual Help • Contextual Help provides information within the context of a task being performed, or about a specific object being operated upon. • Common kinds of contextual Help include Help command buttons, status bar messages, and ToolTips. • Command. 39
- 40. Help Command Button • Description: -A command button. • Purpose: -To provide an overview of, summary assistance for, or explanatory information about the purpose or contents of a window being displayed. • Design guidelines: -Present Help in a secondary window or dialog box. Contextual Help(cont.) Help command button. 40
- 41. Status Bar Message • Description: -An abbreviated, context-sensitive message related to the screen item with the focus. -Appears in window’s status bar when the primary mouse button is pressed over an item (or keyboard focus is achieved). Contextual Help(cont.) 41
- 42. • Purpose: - To provide explanatory information about the object with the focus. - Use to: o Describe the use of a control, menu item, button, or toolbar. o Provide the context of activity within a window. o Present a progress indicator or other forms of feedback when the view of a window must not be obscured. - Do not use for information or access to functions essential to basic system operations unless another form of Help is provided elsewhere in the Help system. - If extended Help is available and must be presented, place “Press F1 for Help” in bar. Contextual Help(cont.) 42
- 43. • Writing guidelines - Be constructive, not simply descriptive. - Be brief, but not cryptic. - Begin with a verb in the present tense. - If a command has multiple functions, summarize them. - If a command is disabled, explain why. Contextual Help(cont.) Status bar message. 43
- 44. ToolTip • Description: - A small pop-up window that appears adjacent to control. - Presented when the pointer remains over a control a short period of time. • Purpose: - Use to display the name of a control when the control has no text label. Contextual Help(cont.) 44
- 45. What’s This? Command • Description: - A command located on the Help drop-down menu on a primary window. - A button on the title bar of a secondary window. - A command on a pop-up menu for a specific object. - A button on a toolbar. • Purpose: - Use to provide contextual information about any screen object. Contextual Help(cont.) 45
- 46. • Design guidelines: - Phrase to answer the question “What is this?” - Indicate the action associated with the item. - Begin the description with a verb. - Include “why,” if helpful. - Include “how to,” if task requires multiple steps. - For command buttons, use an imperative form: “Click this to....” Contextual Help(cont.) 46
- 47. Task-Oriented Help • Description: - A primary window typically accessed through the Help Topics browser. - Includes a set of command buttons at the top; at minimum o A button to display the Help Topics browser dialog box. o A Back button to return to the previous topic. o Buttons that provide access to other functions such as Copy or Print. 47
- 48. • Purpose: - To describe the procedural steps for carrying out a task. - Focuses on how to do something. • Design guidelines: - Provide one procedure to complete a task, the simplest and most common. - Provide an explanation of the task’s goals and organizational structure at the start. - Divide procedural instructions into small steps. - Present each step in the order to be executed. - Label each step. Task-Oriented Help(cont.) 48
- 49. - Explicitly state information necessary to complete each step. - Provide visuals that accurately depict the procedural steps. - Accompany visuals with some form of written or spoken instructions. - Begin any spoken instructions simultaneously with or slightly after a visual is presented. - Segment any animation to focus attention on specific parts. - Segment instructions. - Delay the opportunity to perform the procedure until all the procedure’s steps have been illustrated. Task-Oriented Help(cont.) 49
- 50. • Presentation guidelines: - The window should consume a minimum amount of screen space, but be large enough to present the information without scrolling. - Normally, do not exceed four steps per window. - Use a different window color to distinguish task-oriented Help windows from other windows. • Writing guidelines: - Write simply and clearly, following all previously presented guidelines. - Focus on how information, rather than what or why. Task-Oriented Help(cont.) 50
- 51. • Description: - An online reference book. - Typically accessed through a o Command in a Help drop-down menu. o Toolbar button. • Purpose: - To present reference Help information, either o Reference oriented, or o User guide oriented. Reference Help 51
- 52. • Design guidelines: - Provide a consistent presentation style, following all previously presented guidelines. - Include a combination of contextual Help, and task-oriented Help, as necessary. - Include text, graphics, animation, video, and audio effects, as necessary. - Make displayed toolbar buttons contextual to the topic being viewed. Reference Help(cont.) 52
- 53. • Presentation guidelines: - Provide a nonscrolling region for long topics to keep the topic title and other key information visible. • Writing guidelines: - Write simply and clearly, following all previously presented guidelines. - Provide meaningful topic titles. Reference Help(cont.) 53
- 55. Wizards Description : • A series of presentation pages displayed in a secondary window. • Include - Controls to collect input. - Navigation command buttons. • Typically accessed through. - Toolbar buttons. - Icons. 55
- 56. Purpose : • To perform a complex series of steps. • To perform a task that requires making several critical decisions. • To enter critical data and for use when the cost of errors is high. • To perform an infrequently accomplished task. • The necessary knowledge or experience to perform a task is lacking. • Not suited to teaching how to do something. Wizards (cont.) 56
- 57. Design guidelines : 1. Provide a greater number of simple screens with fewer choices, rather than a smaller number of more complex screens with too many options or too much text. 2. Provide screens of the exact same size. 3. Include on the first page • A graphic on the left side to establish a reference point or theme. • A welcoming paragraph on the right side to explain what the wizard does. 4. Include on subsequent pages • A graphic for consistency. • Instructional text. • Controls for user input. 5. Maintain consistent the locations for all elements. 6. Make it visually clear that the graphic is not interactive. • Vary from normal size or render it as an abstract representation. Wizards (cont.) 57
- 58. Design guidelines : • Include default values or settings for all controls when possible. • For frequently used wizards, place a check box with the text “Do not show this Welcome page again” at the bottom of the Welcome page. • Include a Finish button at the point where the task can be completed. • Do not require the user to leave a wizard to complete a task. • Make sure the design alternatives offered yield positive results. • Make certain it is obvious how to proceed when the wizard has completed its process. Wizards (cont.) 58
- 59. Presentation guidelines : • Display the wizard window so it is immediately recognized as the primary point of input. • Present a single window at one time. • Do not advance pages automatically. Writing guidelines: • Clearly identify the wizard’s purpose in title bar. • At the top right of the wizard window, title the Welcome page “Welcome to the Wizard Name Wizard.” •• Use mixed case in headline style and no ending punctuation. • Write simply, concisely, and clearly, following all previously presented guidelines. • Use a conversational rather than instructional style. • Use words like “you” and “your.” • Start most questions with phrases like “Which option do you want . . .” or “Would you like. . . .” Wizards (cont.) 59
- 61. Hints or Tips Description : A command button labeled Hints or Tips. Purpose: To provide a few important contextual, but specific, items of information related to a displayed screen. 61
- 62. Design guidelines : • Provide guidance on only two or three important points. • Locate the button near where its guidance applies. • Write concisely and to the point. Hints or Tips (cont.) 62
- 63. Hints or Tips (cont.) 63
- 64. That’s All Thank You For Your Attention :) 64