• Save
The 10 Usability Commandments
Upcoming SlideShare
Loading in...5
×
 

The 10 Usability Commandments

on

  • 1,019 views

This presentation recaps Jakob Nielsen’s Ten Usability Heuristics and includes examples of each principle.

This presentation recaps Jakob Nielsen’s Ten Usability Heuristics and includes examples of each principle.

Statistics

Views

Total Views
1,019
Views on SlideShare
1,014
Embed Views
5

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 5

http://www.linkedin.com 5

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 “ feedback” 1.1 BaseCamp by 37signals The upload button is enabled, until clicked. Then it is replaced with a progress indicator until the file has finished uploading 1.2 Picnik Progress message and indicator shows while the application loads 1.3 Tick A feedback message is displayed when an action is performed 1.4 Windows Live Account Password strength is shown as the password is entered
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 2. Match between system and the real world (METAPHOR) The system should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order. 2.0 iTunes Organized as a library that contains your media library: music, movies, shows, audibooks. Beneath the Library is the Store where you can buy more media to put in your Library. 2.1 Mindomo The branches and hierarchy of a mind map can be easily reorganized visually in a non-linear manner. An outline would never work, but this matches the paradigm exactly.
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 Users often choose system functions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Supports undo and redo and a clear way to navigate. 3.0 CollabFinder Search is easy to open, enter info, execute or cancel. 3.1 Wufoo Clearly marks where the person is and where they can go by showing the selection in each menu 3.2 Pages (Apple’s Word Processing Product) Cell editing shows row and column ids, and the cells used in the equation. The equation can be saved or canceled. 3.3 Balsamiq Undo and Redo buttons are available in the toolbar, and can also be accessed with the standard keyboard shortcuts
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 4. Consistency and standards (CONSISTENCY) Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions. 4.0 Gmail When Gmail was designed, they based the organizational folders on the same ones used in client email applications: Inbox, Drafts, Sent Mail. 4.1 Microsoft Office Word, Excel, and PowerPoint all use the same style toolbar with the same primary menu options: Home, Insert, Page Layout… Consistency results in efficiency and perceived intuitiveness.
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 5. Error prevention (PREVENTION) Even better than good error messages is a careful design, which prevents a problem from occurring in the first place. 5.0 Yammer Disables the update button after it is clicked, so the person cannot update the post twice by accident 5.1 Example from “Web form Design:Filling in the Blanks” by Luke W. Make the primary action prominent with a larger click area. Cancel and secondary actions are just shown as links 5.2 Google Auto Recommend The auto recommend feature cuts down on mis-spellings 5.2 Wikpedia Auto focus on input prevents a common source of frustration, typing only to realize nothing is displayed because the field did not have focus
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 . Recognition rather than recall (MEMORY) Minimize the user’s memory load. Make objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate. 6.0 Quanta IDE Type ahead for coding in a development environment 6.1 Keynote (shown us powerpoint font examples) Previews the fonts you can pick from, instead of just the font name
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 7. Flexibility and efficiency of use (EFFICIENCY) Accelerators — unseen by the novice user — may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions. 7.0 OmniFocus List of keyboard shortcuts and accelerators 7.1 Numbers- Apple’s Spreadsheet product Previews common function results on the left when a column is selected, more efficient that clicking on an action in the toolbar
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 8. Aesthetic and minimalist design (DESIGN) Dialogues should not contain information, which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility. Visual layout should respect the principles of contrast, repetition, alignment, and proximity. 8.0 Kontain (latest version shown as well, more streamlined!) Kontain’ search menu exemplifies the four principles of visual design: Contrast: bold text is used for the two labels in the search Repetition: the orange, blue, and green text match the media types Alignment : strong left alignment of text, right aligned drop down Proximity: a light rule is used to separate tags from the other options 8.1 Harvest (not shown; timesheet example) Sufficient padding and spacing keep this timesheet from being a visual nightmare. Header and footer rows, as well as the summary column use subtly different colors to indicate they are distinct from the content
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 Yaddy note: error states are super important!! 9. Help users recognize, diagnose, and recover from errors (RECOVERY) Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution. 9.0 Digg Provides immediate feedback with specific instructions 9.1 Humorous ‘ Page Not Found’ Error Uses a funny image and copy, but provides viable alternatives (article listings and blog link) and a course of action (report it)
  • http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 Yaddy note: Types of help~ ~contextual ~video ~intuitive ~aggregate 10. Help and documentation (Help) Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large. 10.0 Picnik Contextual help (this is an example of help in the ‘Collages’ module) tips in Picnik are clear and easy to navigate 10.1 GoodBarry Embedded videos can be used to showcase features as well as get people started using the product 10.2 Zenoss Help tips are displayed on hover, answering the most likely questions about a field or instructions 10.3 BaseCamp by 37signals Help opens a new browser window/tab with a full set of help resources: search, FAQ, video tutorials, customer forums

The 10 Usability Commandments The 10 Usability Commandments Presentation Transcript

  •  
    • Visibility of System Status
    • Match Between System & the Real World
    • User Control and Freedom
    • Consistency and Standards
    • Error Prevention
    • Recognition Rather Than Recall
    • Flexibility and Efficiency of Use
    • Aesthetic and Minimalist Design
    • Help Users Recognize, Diagnose, and Recover from Errors
    • Help and Documentation
    The Ten Usability Heuristics Source(s): “6 Tips for a Great Flex UX ,” Theresa Neil, http://designingwebinterfaces.com/6-tips-for-a-great-flex-ux-part-5 ;
  • 1. Visibility of System Status
    • The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
  • 2. Match Between System and The Real World
    • The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
  • 3. User Control and Freedom
    • Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
  • 4. Consistency and Standards
    • Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
  • 5. Error Prevention
    • Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
  • 6. Recognition rather than recall
    • Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
  • 7. Flexibility and Efficiency of Use
    • Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
  • 8. Aesthetic and Minimalist Design
    • Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
  • 9. Help Users Recognize, Diagnose, and Recover from Errors
    • Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
  • 10. Help and Documentation
    • Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.