First round of testing, coming up!

I have completed the script for the first round of testing for our Smugmug Web site. Our primary objective is to test what people think about the site, and to see if our tagging system is efficient. What I have found useful prior to this round of formal testing is to look at photos and have people describe what they see.

Hopefully within the week I will have my testing results.

Usability Testing

Gaffney, G. Information & Design,www.infodesign.com.au 1999

Key Words: walk-through, usability testing, guidelines

Usability testing is a technique for ensuring that the intended users of a system can carry out the intended tasks efficiently, effectively and satisfactorily. It can be carried out at any point in the design process; however, in the early stages a "walk through" is best.

Usability tests should be attended by:

• representative user
• test host
• a developer

6-8 test sessions usually uncovers the majority of significant issues.  However, even one test is better than none.

Required Materials

• formal script (to treat all participants the same way)
• pre-evaluation questionnaire (to check there profile)
• a list of tasks (and criteria)
• logging sheets (to record timing, events, actions, comments, concerns)
• post-evaluation questionnaire (to measure user satisfaction)

Guidelines

• run a pilot test
• make sure participants are put at ease
• do not prompt participants unless clearly indicated
• record in as much detail as possible
• do not interrupt (if there are other observers)

Research-Based Web Design & Usability Guidelines


Citation: Research-Based Web Design & Usability Guidelines. 2011.

http://www.usability.gov/pdfs/chapter18.pdf

Key words: usability testing, observations, iterative approach, performance usability


This chapter is about (main discussion):
Creating prototypes, testing the prototypes, and then making changes based on the test results. The “test and make changes” process is repeated until the Web site meets usability goals. When these goals are met, the iterative process ends.

The author argues that:
the iterative design process helps to substantially improve the usability of web sites. Studies show that improvements made between original websites and redesigned ones “resulted in 30% more task completions, 25% less time to complete the tasks, and 67% greater user satisfaction. A second study reported that 8/10 tasks were performed faster on the website that had been iteratively designed. Lastly, a third study found that 46% of the original set of issues were resolved by making design changes to the interface.” (http://www.usability.gov/guidelines/guidelines_book.pdf 18:1)


The authors make the following statements or sites the following references on support of his/ her argument (provide 2-3 quotes):
it is best to perform iterative cycles of usability testing over the course of the web site’s development, as this allows developers the chance to observe and listen to many users.
http://www.usability.gov/guidelines/guidelines_book.pdf (18:6)
Performance usability testing with users early in the design process with a small number of diverse users (about 6 users ranging from novice to expert) is sufficient to identify problems with the info architecture and overall design issues. Once this has been completed, quantitative testing (measuring times, failure to find content, etc.) can be conducted. Try to achieve 95% confidence level in usability tests http://www.usability.gov/guidelines/guidelines_book.pdf (18:6)

The authors conclude that:
developing and testing prototypes through and iterative design approach creates the most useful and usable website.

The authors feel that:
“the iterative design process helps to substantially improve the usability of Web sites.”

References: http://www.usability.gov/guidelines/guidelines_book.pdf