Efficient Usability Analyzer

Five years ago I learned about 4 basic concepts that dramatically changed my approach to usability. These were that it must be fast, efficient, simple, and focused.

Fast, efficient and simple are concepts that are based on old mathematical concepts.

• Fast is connected to "GOMS keystroke model"
  "The fewer times you click on something and the fewer times you move your hand between the keyboard and the mouse, the faster it is to use".
• Efficient is connected to "Fitt's Law"
  "A large target close to you, is easier to hit than a small target far away"
• Simple is connected to "Hick's Law"
  "The fewer choices you have, the easier it is to choose between them"

Sounds simple right?

• Focus is equally simple
  "Less distractions, enables you to better focus on the task at hand"

The best part of this approach is not that it is simple. It is that you can measure how usable your product is, before you show it to other people (like in user testing).

Prior to using this concept, I made a lot products that I believed was good. But the problem was, I didn't know until I had tested it with real people. Many times I tried making something, only to see people confused by it in a user testing. This was an unacceptable situation.

The major problem with user testing is that it comes after the work phase. It is a problem because it means that you are working blindfolded. You don't know the result of your work until it has been completed. This also means that you do not have control over your project plan (or that you have to plan everything to take longer than it should).

User testing is great for getting the finer details right, not as a general usability measurement.

Instead you need a tool that help you analyze the work ahead of you - before you start doing anything. This is one of the strong points of the "Fast, Efficient, Simple and Focused" concept.

The Analyzer

I have made an Excel analyzer (freebie) to help you do this. I have been using this successfully for the last 5 years - for both analyzing the best solution to a problem or when evaluated other people's work.

For me, it has been a tremendous time saver. It has allowed me to focus more on actually solving people goals and less time one guessing what approach is best.

Download

• Usability Analyzer (Excel file - Metric)
• Usability Analyzer (Excel file - Imperial)

How to use?

You use the analyzer by entering each step you need to take to perform a certain task. When doing comparison analysis it is important that your start and end points are the same. If you start with the mouse in one analysis, you must also start with the mouse in any subsequent analysis.

See also: "AJAX Type Ahead" example below

Selectors

• Click: Indicates mouse clicks or use of the keyboard. Type in either the number of times you have to click on something (like "2" if you are double-clicking or "9" if you type the word "Usability"). If you only have to click once you can use "x" or "1"
• Hold / Release: Used to indicate press and holding your mouse button or a key on the keyboard - and releasing it later. Using the shortcut for "copy" would be "Hold (CTRL) + Click (C) + Release (CTRL)"
• Pointing: Indicates pointing your mouse cursor to a specific object (like a menu item, icon or form field etc.) You can either use pointing alone (uses GOMS) or add the distance you have to point using "Distance" and "target" (this uses FITT's and gives you a more accurate time).
• Moving:Â Indicates moving an item from one point to another. Dragging an item is indicated by "Hold + Moving + Release". As with pointing you can define the exact distance using "Distance" and "target"
• Distance: Used with either pointing or moving (cannot be used alone). Indicates the exact distance you move your mouse - measured in millimeters / inches (depending on which file you downloaded).
  Note: This is how far you move your mouse on the table, not on screen.
• Target: Used with either pointing or moving (cannot be used alone). Indicates the size of the target object (menu item, icon, object on screen etc.) - measured in millimeters / inches (depending on which file you downloaded).
  Note: This is how far you move your mouse on the table, not on screen.
• Switching: Indicates when you switch between input devices - like moving your hand from the mouse to the keyboard.
• Deciding: Indicates when you have to decide on something. Is added every time you do something new. You can either type "x" to indicate a single decision (like when you decide to click "submit") - in which case it uses GOMS to calculate the time. Or you can add a specific number of decisions, as when you got more than one choice to choose from (like when you have to select an item in a drop-down list - then it uses Hick's which is more accurate. You add a decision point every time you do something different - or when the next task involves choosing between 1 or more items.
• Waiting: Indicates the number of seconds you have to wait for the system to respond.

Example #1: AJAX Type Ahead in search

Type-ahead is popping up everywhere. We got Apple Spotlight, Google Suggest and Windows Vista's "Start Search" as well as a huge number of varies implementations in AJAX and Web 2.0 applications. But how does it actually in perform in terms of efficient usability?

Analysis parameters:

• Interface elements include: Search box, submit button, and a area for the result.
• Action start: the user start typing in the search input field
• Action end: the user reaches the destination page
• Complete input text: "GOMS Usability" (14 characters)
• Result for "GOMS Usability" is 10 pages
• The desired destination page is always the third result
• Type-ahead results: the user needs to type in "goms usabi" to get a correct match (10 characters)
• Distance from initial mouse pointer position to the third result (24mm - target: 8mm)

Base comparison, No type-ahead
Action: Type in the full search keyword, submit, activate the third result.

Instant type ahead: The results will appear immediately after each keystroke
Action: Start to type the full keyword, evaluate each result until we have a match, activate the third result

Instant type ahead - keyboard only: The results will appear immediately after each keystroke, and the result can be activated using the keyboard (key down x 3 + Enter)
Action: Start to type the full keyword, evaluate each result until we have a match, activate the third result

Delayed type-ahead: The results will appear 0.5 seconds after the user has stopped typing
Action: Type in the full search keyword, wait for the results, activate the third result.

Goggle Suggest type-ahead: The result is not the actual pages, but search terms.
Action: Start to type the full keyword, evaluate each result until we have a match, highlight the match, evaluate the results, activate the third result.

Comparison results: There isn't much to gain by using AJAX with search. All methods, except delayed type-ahead, is less efficient than a non-AJAX solution - with Google Suggest being the worst implementation of all.

Both Apple's Spotlight and Windows Vista's "Start Search" uses delayed type-ahead.

Notice: The analysis for both instant and Google Suggest has been simplified. The decision steps should have been repeated * the power of practice instead of simply grouping them together. The result is thus faster than in a correct analysis.

Example #2: AJAX Type Ahead in form fields

Another use for AJAX is to quick fill form fields, like when you add resources to tasks in a project.

Analysis parameters:

• Interface elements include a single form field
• Action start: When the user starts typing
• Action end: When the user has move to the next field (using [TAB])
• Input text is "thomas baekdal" (14 characters) or "tb" when using initials (2 characters)
• Result for "thomas baekdal" is 3 items, of which the second item is the correct one
• Type-ahead results: the user needs to type in "thoma" to get a correct match (5 characters)
• Distance from initial mouse pointer position to the second result (9mm - target: 2mm)

Base comparison: No type-ahead - full name
Action: Type in the full name of the resource, move to the next field [TAB]

Automatic type-ahead: Type in initials and automatically convert them
Action: Type in the initials, move to the next field [TAB]

Instant type-ahead: The results will appear immediately after each keystroke
Action: Start to type the full keyword, evaluate each result until we have a match, activate the second result, move the to next field.

Instant type ahead - keyboard only: The results will appear immediately after each keystroke, and the result can be activated using the keyboard (key down x 2 + Enter)
Action: Start to type the full keyword, evaluate each result until we have a match, activate the second result, move to the next field.

Comparison results: Again we see an interesting pattern. Using AJAX to create an instant type-ahead feature is directly counter-productive. It is much faster to simply do without. But, using AJAX to automate can create a much more usable experience - in this case it speeds up the process by an amazing 500%

Notice: The analysis for instant type-ahead has again been simplified.

See Also

• The Battle Between Usability and User-Experience (Baekdal.com, June 2006)

More from Baekdal

Why publishers who try to innovate always end up doing the same as always

Almost every time a news site launched something new, they also cover the same stories the same way.

27 pages

A guide to using editorial analytics to define your newsroom

Editorial analytics is the tool we use to define how to report the news.

39 pages

What do I mean when I talk about privacy and tracking?

Tracking isn't the problem, destinations are.

13 pages

Let's talk about Google's 'cookie-less' future and why it's bad

Google wants to build tracking into the browser, and then remove personal identifiers ... but is that good?

22 pages

I'm not impressed by the Guardian's OpenAI GPT-3 article

AIs can be both good and bad, but using an AI to fake some text is always bad.

14 pages

Should media be tax exempt?

Many people in the media wants newspapers to be tax exempt, but what about the rest of the media?

15 pages

More studies that don't mean what we think they mean

When a publishers says that WhatsApp converts 12 times more people than their website, what does that actually mean?

12 pages

The thing about Facebook and political advertising

Facebook said that it wouldn't block misleading political ads, so let's talk about that

21 pages

The Original Cookie specification from 1997 was GDPR compliant

Cookies today are doing all kinds of bad things, but did you know that the original creators wanted to stop that?

24 pages

The thing about the EU copyright law and Google refusing to pay

We all knew this would happen, but Google won't pay publishers for snippets.

6 pages