Studies : RITE Method

RITE (Rapid Iterative Testing and Evaluation) Method

The RITE (Rapid Iterative Testing and Evaluation) Method of user testing is a practice that has been used for years by usability practicioners for years but has remained largely undefined. It is a highly effective method for identifying and correcting problems quickly and effectively.

The primary motivation behind user testing is to improve a product quickly and easily and get it back out to the consumer. Unfortunately this motivation is not always enough and many times user testing results are not implemented. There are four primary reasons for this:

1. Disbelief: Members on a development team may not believe in the results or find them worthy of correcting.
2. Lack of resources: Developers are not always available to improve existing functions and when given a choice will most often add another feature rather than correct an existing one.
3. Late feedback: Providing feedback to development teams after important decisions have been made usually results in the feedback not being followed.
4. Uncertainty: If the development team is not certain that a proposed solution will fix a problem, they are much less likely to implement it.

Much like a traditional usability test, the RITE Method requires that a population be identified, decisions about how to measure the testing are made, a test script is written and participants follow a "think aloud" protocol. The primary difference in RITE testing and traditional testing is the timing. As soon as a problem is identified, even if only by one user, a change is made and applied to the final solution for the remainder of the tests.

Flaws discovered by participants in the test and categorized in an effort to understand which changes can be made quickly and which must be postponed based on other user feedback. The four categories are:

1. Issues with obvious cause/solution that are easily implemented
   Action: This category is quickly implemented and tested on the next user
2. Issues with obvious cause/solution that are not easily implemented
   Action: Modifications are made as quickly as possible and added to user testing as soon as completed
3. Issues with no obvious cause/solution
   Action: More data is collected to determine if the error can be upgraded to a 1 or 2
4. Issues related to external problems (such as testing environment)
   Action: More data is collected to determine if the error can be upgraded to a 1 or 2

Prior to beginning a RITE Method of user testing, certain ground rules must be established and ageed upon by the development team. There must be agreement about which tasks are essential for each user to complete successfully, how quickly the revisions can and should be implemented, and how many participants should be tested after the modifcation has been made. The results should be interpreted, categorized into one of the four classifications listed above and acted upon quickly.

The RITE Method can be a successful model for user testing when understood and implemented properly. As a business solution it can identify and correct a majority of flaws quickly and efficiently, getting the product out the door and saving time and money expenses in the long run.

This method of usability testing should also be used carefully as there are potential pitfalls in the testing. Such rapid changes or making too many changes at one time may cloud issues as to the true cause/solution of problems or may generate larger problems further down the road. It is important to conduct follow up testing as well to ensure that the changes made solved the problem.

The RITE Method is one of many techniques to test users and the effectiveness of computer systems, the type of testing should be considered carefully by the usability team and there should perhaps be multiple types of usability tests conducted.

Medlock, M. C., Wixon D., Terrano, M., Romero R., Fulton B. (2002). "Using the RITE Method to improve products: a definition and a case study." Usability Professionals Association, Orlando FL July 2002.