RITE Method
RITE Method, for Rapid Iterative Testing and Evaluation, typically referred to as "RITE" testing, is an iterative usability method. It was defined by Michael Medlock, Dennis Wixon, Bill Fulton, Mark Terrano and Ramon Romero. It has been publicly championed by Dennis Wixon while working in the games space for Microsoft. It has many similarities to "traditional" or "discount" usability testing. The tester and team must define a target population for testing, schedule participants to come into the lab, decide on how the users' behaviors will be measured, construct a test script and have participants engage in a verbal protocol (e.g. think aloud). However it differs from these methods in that it advocates that changes to the user interface are made as soon as a problem is identified and a solution is clear. Sometimes this can occur after observing as few as one participant. Once the data for a participant has been collected the usability engineer and team decide if they will be making any changes to the prototype prior to the next participant. The changed interface is then tested with the remaining users. The philosophy behind the RITE method is described as: "1) once you find a problem, solve it as soon as you can, and 2) make the decision makers part of the research team." In this way it is a bridge between a strict research method and a design method...and in many ways it represents a participatory design method. Since its official definition and naming its use has rapidly expanded to many other software industries.
RITE Method, for Rapid Iterative Testing and Evaluation,[1] typically referred to as "RITE" testing, is an iterative usability method. It was defined by Michael Medlock, Dennis Wixon, Bill Fulton, Mark Terrano and Ramon Romero. It has been publicly championed by Dennis Wixon[2] while working in the games space for Microsoft.
It has many similarities to "traditional"[3] or "discount"[4] usability testing. The tester and team must define a target population for testing, schedule participants to come into the lab, decide on how the users' behaviors will be measured, construct a test script and have participants engage in a verbal protocol (e.g. think aloud). However it differs from these methods in that it advocates that changes to the user interface are made as soon as a problem is identified and a solution is clear. Sometimes this can occur after observing as few as one participant. Once the data for a participant has been collected the usability engineer and team decide if they will be making any changes to the prototype prior to the next participant. The changed interface is then tested with the remaining users.
The philosophy behind the RITE method is described as: "1) once you find a problem, solve it as soon as you can, and 2) make the decision makers part of the research team."[5] In this way it is a bridge between a strict research method and a design method...and in many ways it represents a participatory design method. Since its official definition and naming its use has rapidly expanded to many other software industries.[6]
See also
[edit]- Acceptance testing
- Human–computer interaction
- Human factors
- Interaction design
- Software testing
- Usability
- Usability testing
- User-centered design
References
[edit]- ^ Medlock MC, Wixon D, Terrano M, Romero R, Fulton B (July 2002). Using the RITE method to improve products: A definition and a case study. Usability Professionals Association. Vol. 51. Orlando Florida. pp. 1963813932–562338474.
- ^ Wixon D (July 2003). "Evaluating usability methods: why the current literature fails the practitioner". Interactions. 10 (4): 28–34. doi:10.1145/838830.838870. S2CID 17052230.
- ^ Dumas J, Redish JC (1993). A Practical Guide to Usability Testing. Norwood, N.J.: Ablex.
- ^ Nielsen J (September 1989). Usability engineering at a discount. Proceedings of the third international conference on human-computer interaction on Designing and using human-computer interfaces and knowledge based systems (2nd ed.). Boston, Massachusetts, United States. pp. 394–401.
- ^ Drachen A, Mirza-Babaei P, Nacke L, eds. (2018-03-22). Games User Research. Vol. 1. Oxford University Press. doi:10.1093/oso/9780198794844.001.0001. ISBN 978-0-19-879484-4.
- ^ Medlock MC, Wixon D, McGee M, Welsh D (January 2005). "The rapid iterative test and evaluation method: Better products in less time.". In Bias G, Mayhew D (eds.). Cost-justifying usability. San Francisco: Morgan Kaufmann. pp. 489–517.
 | This software-engineering-related article is a stub. You can help Wikipedia by adding missing information. |