User-Testing Techniques - Site Reviews

Accurately measuring reader-friendliness is a complex task for any Website. Usability testing techniques have been applied with some success to Web pages. But formal usability tests are difficult to set up, and very expensive to conduct (often prohibitively so). And the diversity of the audience of Internet sites probably limits the utility of formal usability testing of many Web pages. Happily, inspection-based usability evaluation is generally as effective as formal, experimental testing, and it is much easier (and less costly) to conduct. This series focuses on inspection-based usability assessment. A site review is basically an unstructured inspection by a third party, typically focusing on the site's usability and aesthetics. It's a difficult but worthwhile effort for serious-minded authors to seek out reviewers who are willing to invest the time to undertake a serious review of your site, offering constructive suggestions for improvement.

Sullivan, Terry. All Things Web (1996). Articles>Usability>Methods>Web Design

When Good Design => Bad Product

The prototypes looked great and tested well. The programmers did their usual competent job of implementation. The result was a disaster. What went wrong? Someone forgot the last, critical step.

Tognazzini, Bruce. Nielsen Norman Group (2003). Design>Usability>Methods

Who Is "The User" Anyway?

As we have pointed out before, understanding the user is a pre-requisite of high quality interface design, whether online or offline. This means taking the time to find out what motivates typical user groups, what they expect from a given site or application, and how they prefer to work (or play). The alternative to proper user profiling is simply plucking an imaginary 'user' out of the air - usually to add weight to personal preferences or prejudices. The latter situation often consists of a so-called expert dismissing design features because 'the user wouldn't like it', when he or she is really saying 'I don't like it'. This common reference to a single undefined 'user' conjures up amusing images of a God-like entity casting judgment on interfaces from on high. In the real world, as we know, things are a little more complex. If 'the user' is frequently invoked but never defined, it may be time to rethink your usability strategy. Of course, after profiling has taken place, or when talking in generalities, there is nothing wrong with 'the user' being used as a convenient shorthand. But during specific projects it is essential to think in terms of real people rather than abstracts. This approach creates both better design and makes usability more understandable, in concrete terms, for others involved in the development process.

Farrell, Tom. Frontend Infocentre (2001). Design>Usability>Methods>Personas

Switching Between Tools in Complex Applications  

Usability practice needs a procedure to identify, record, count, and highlight tool switch events for study. This paper describes one that supports the trained observers on which User-Centered Design relies to detect problems and causes, and evaluate design changes.

Schroeder, Will. Journal of Usability Studies (2008). Articles>Usability>User Centered Design>Methods