Save money and test with prototypes first

It is easier for a user to react to an existing example than to theorize what would work best. Useful results can be obtained by building a prototype site, with a minimum of text content and no graphics, for a first round of usability testing.

The prototype can then be used, before actual development begins, to gather user comments and observe the prototype's ability to lead the users through the tasks they need to perform.

Types of Prototypes

Paper prototype: Sketches or printouts of potential page layouts. Respondents may need to use a bit of imagination when assessing early-stage deliverables, but it's an excellent way to test page layouts.

Design comp: Visual designs or mockups of limited number of pages.

Wire frame: Early versions of a site with limited depth and functionality. Useful for testing processes (registration, purchase, and so on) and site flow.

Changes can be made quickly and tested again almost immediately.

Usability testing is an iterative process, which simply means test, identify problems, fix and then test again. With paper prototypes, if a term is confusing, you can cross it out and try a different one. Simple changes like these can solve many usability problems.

It saves you money and reduces investment risk.

According to Clare-Marie Karat of IBM, spending $60,000 on usability engineering throughout development resulted in savings of $6,000,000 in the first year alone.

Conducting usability tests with real users before even one line is coded saves you money. The benefits are obvious. You don't have to wait until you've released the product before finding out what the problems are.

References:

Create Mock-ups, CNET builder.com.

Ericsson, K. and Simon, H. 1980 "Verbal Reports as Data," Psychological Review,87, 3, 215-251

Ericsson, K. A. and Simon, H. A. Protocol Analysis Verbal Reports as Data (Revised Edition). The MIT Press Cambridge, MA, 1993.

Fucella, J. and Pizzolato J. IBM. A Divided Approach to Web Site Design: Separating Content and Visuals for Rapid Results.

Karat, C.-M. Business case approach to cost justification. In Cost-Justifying Usability, Edited by R. G. Bias and D. J. Mayhew, Boston: Academic Press, 1994, 45-70.

Ramey, J. University of Washington. Methods for Successful "Thinking Out Loud" Procedure.

Virzi, R., Sokolov,J. and Karis, D."Usability problem identification using both low- and high-fidelity prototypes"

About the author
	Gul Amir Khan is the Chief Usability Consultant for MicroUsability and the current President of the Usability Professional's Association (Singapore Chapter). Gul has been trained in Game Theory and Strategic Behavior Analysis and has incorporated these techniques in web usability engineering. He has conducted numerous usability projects and usability workshops across Asia.