5 Tips for Agile and Effective Usability Testing
When approaching the development of a new website, project managers, designers, and application developers initially have little data to inform their design decisions and must rely upon research in order to construct successful user experiences. Research, however, is completely invalidated if the decisions it suggests end up being ineffective after a project launches. The fail safe for avoiding such an outcome is extensive usability testing, a portion of the development process many organizations sometimes wish to avoid due to perceived associative costs and resource drain. Usability testing, though, does not have to be expensive or take a prohibitive amount of time, and the changes that will come about due to interacting directly with users will reap benefits that far outweigh any costs in capital or time that is accrued throughout the process.
Keeping usability testing light and cost effective is key, and here are five quick tips on how to do just that:
1.) Don’t Be Overly Picky About Your “Subjects”
In an ideal situation the users selected for a usability test will be representative of the market segment the website is targeting, requiring the intervention of a head-hunting firm, in turn adding time and cost to the overall process. Those tested, however, do not have to be completely indicative of the website’s end user — anyone, simply, is better than no one. Grab someone from the office suite over, a neighbor, a friend, or even a relative if there is no other alternative. Anyone who has not been staring at the project for weeks on end will do as they are certain to catch problems in the user experience overlooked by team members who have become used to the project’s flow.
2.) Make Your Users Comfortable
Usability testing is always most effective when the users are comfortable. The key to setting users at ease is to remind them that the test concerns the website, not the user him or herself. Typically, users feel as if their technical skill is being reviewed, which is never the case (even if their base level of technical knowledge is an important factor to consider.) Nothing can invalidate usability test results quicker than a subject contracting a case of Mad Clicking Syndrome due to nerves.
Also, make sure the testing environment is comfortable. Many large organizations have constructed large testing environments fit with two-way glass and hidden cameras. These “sterile” environments only reinforce users’ feelings that they are being evaluated and may lead to throw away results. A room, any room, fit with a comfortable chair and a laptop suffices. Also be certain to only have one usability test facilitator sit with the user. Having the entire team in on the test, for instance, will simply add to the user’s nervousness and lessen the overall effectiveness of the test. So, how does the information from the test trickle down to members of the development team, then? Glad you asked!
3.) Record the Sessions
Always be certain to record the test sessions, specifically everything on-screen and all that is said by the user and test facilitator. Recording eliminates the need for multiple team members to sit in on the session — everyone can simply watch and listen later on and take their own notes, allowing for a productive post-test note-sharing and brainstorming session. Remember that users must be notified that they are being recorded beforehand, and if they object your notes alone will have to suffice for the entire team.
A full video production setup is not required to record test sessions. There are several simple solutions that can be installed on laptops to create mobile recording stations for usability testing, including CamStudio (free), My Screen Recorder, Adobe Captivate, and Techsmith’s Camtasia Studio (There are undoubtedly more — post them in the comments!).
4.) Alter and/or Create New Scenarios on the Fly
Always try to formulate new test scenarios or interview questions based on interactions with the user as it will always increase the accuracy of results. A user is more likely to use a website as they normally would if they have some sort of personal investment in the task he or she is undertaking. If your site is a travel portal, for instance, ask the user what their dream vacation is and then have them set it up using the site’s tools. You will almost immediately notice a new focus and an easing of tensions, lending to a more relaxed, and accurate testing session.
5.) Test Early and Often
One of the biggest mistakes organizations make with usability testing is that they focus on testing late in the development process when major changes are difficult and costly to implement. Usability testing should begin as soon as functionality is set and before major design elements are in place, which makes it easier to change out large portions of mark-up and code if major issues arise. If the previous 4 steps are followed the testing process will be agile and effective enough to repeat as many times as necessary to ensure an end product that provides an outstanding user experience that successfully converts.
Usability testing does not have to be overly complex or costly. With just a handful of ordinary people from down the street or next door, effective testing sessions can be conducted that will ensure that your web project will meet its goals on time and even within budget.







[...] at success. Here are 5 quick tips on how to conduct agile and effective usability testing sessions.read more | digg [...]
Pingback by 5 Tips for Agile and Effective Usability Testing | White Sands Digital — May 5, 2008 @ 4:57 pm