RITE Method: Difference between revisions

Edit links
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Included a section on the philosophy of RITE from the book chapter by Michael Medlock on RITE in the book Games User Research
Yugyr (talk | contribs)
8 edits
m Added a citation of a recent application of the RITE method in research.
Line 1: Line 1:
'''RITE Method''', for '''Rapid Iterative Testing and Evaluation''',<ref>Medlock, M.C., Wixon, D., Terrano, M., Romero, R., and Fulton, B. (2002). [http://download.microsoft.com/download/5/c/c/5cc406a0-0f87-4b94-bf80-dbc707db4fe1/mgsut_MWTRF02.doc.doc] Using the RITE method to improve products: A definition and a case study. Presented at the Usability Professionsals Association 2002, Orlando Florida.</ref> 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<ref>Dennis Wixon, Evaluating usability methods: why the current literature fails the practitioner, interactions, v.10 n.4, July + August 2003</ref> while working in the games space for [[Microsoft]]. It has many similarities to "traditional"<ref>Dumas J., and Redish J.C. (1993). A Practical Guide to Usability Testing. Ablex, Norwood, N.J.</ref> or "discount"<ref>Jakob Nielsen, 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.), p.394-401, September 1989, Boston, Massachusetts, United States</ref> [[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."<ref>{{Cite book|url=https://oxford.universitypressscholarship.com/view/10.1093/oso/9780198794844.001.0001/oso-9780198794844|title=Games User Research|date=2018-03-22|publisher=Oxford University Press|isbn=978-0-19-879484-4|editor-last=Drachen|editor-first=Anders|volume=1|language=en|doi=10.1093/oso/9780198794844.001.0001|editor-last2=Mirza-Babaei|editor-first2=Pejman|editor-last3=Nacke|editor-first3=Lennart}}</ref> 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.<blockquote>''"As Researchers you get a lot of fundamental training on what constitutes actionable proof. That fundamental training focuses on 'completing your research' before drawing conclusions. In publishing RITE we wanted Researchers to acknowledge that in the correct circumstances you can make strong and accurate conclusions and 'complete research' quite quickly. Perhaps more importantly, the standard literature (of the time) on usability testing was indexed on accurate identification of problem areas. '''The key word in the RITE acronym is Iterative.''' Through iteration you can prove that something is fixed, which we felt was a more important way to think about research findings. '''Find a thing. That's nice. Find and fix it. Far better.'''" —'' Ramon Romero<ref>{{Cite web|title=RITE Method: Comprehensive guide for Rapid Iterative Testing and Evaluation|url=https://www.hellopingpong.com/blog/rite|access-date=2020-07-07|website=www.hellopingpong.com}}</ref></blockquote>Initially it was documented as being used in the PC games business, but in all truth it has probably been in use "unofficially" since designers started prototyping products and watching users use the prototypes.{{Citation needed|date=April 2010}} Since its official definition and naming its use has rapidly expanded to many other software industries.<ref>Medlock, M.C., Wixon, D., McGee, M., & Welsh, D. (2005). The Rapid Iterative Test and Evaluation Method: Better Products in Less Time. In Bias, G., & Mayhew, D. (Eds.), ''Cost Justifying Usability'' (pp. 489-517). San Francisco: Morgan Kaufmann</ref>
'''RITE Method''', for '''Rapid Iterative Testing and Evaluation''',<ref>Medlock, M.C., Wixon, D., Terrano, M., Romero, R., and Fulton, B. (2002). [http://download.microsoft.com/download/5/c/c/5cc406a0-0f87-4b94-bf80-dbc707db4fe1/mgsut_MWTRF02.doc.doc] Using the RITE method to improve products: A definition and a case study. Presented at the Usability Professionsals Association 2002, Orlando Florida.</ref> 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<ref>Dennis Wixon, Evaluating usability methods: why the current literature fails the practitioner, interactions, v.10 n.4, July + August 2003</ref> while working in the games space for [[Microsoft]]. It has many similarities to "traditional"<ref>Dumas J., and Redish J.C. (1993). A Practical Guide to Usability Testing. Ablex, Norwood, N.J.</ref> or "discount"<ref>Jakob Nielsen, 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.), p.394-401, September 1989, Boston, Massachusetts, United States</ref> [[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."<ref>{{Cite book|url=https://oxford.universitypressscholarship.com/view/10.1093/oso/9780198794844.001.0001/oso-9780198794844|title=Games User Research|date=2018-03-22|publisher=Oxford University Press|isbn=978-0-19-879484-4|editor-last=Drachen|editor-first=Anders|volume=1|language=en|doi=10.1093/oso/9780198794844.001.0001|editor-last2=Mirza-Babaei|editor-first2=Pejman|editor-last3=Nacke|editor-first3=Lennart}}</ref> 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.<blockquote>''"As Researchers you get a lot of fundamental training on what constitutes actionable proof. That fundamental training focuses on 'completing your research' before drawing conclusions. In publishing RITE we wanted Researchers to acknowledge that in the correct circumstances you can make strong and accurate conclusions and 'complete research' quite quickly. Perhaps more importantly, the standard literature (of the time) on usability testing was indexed on accurate identification of problem areas. '''The key word in the RITE acronym is Iterative.''' Through iteration you can prove that something is fixed, which we felt was a more important way to think about research findings. '''Find a thing. That's nice. Find and fix it. Far better.'''" —'' Ramon Romero<ref>{{Cite web|title=RITE Method: Comprehensive guide for Rapid Iterative Testing and Evaluation|url=https://www.hellopingpong.com/blog/rite|access-date=2020-07-07|website=www.hellopingpong.com}}</ref></blockquote>Initially it was documented as being used in the PC games business, but in all truth it has probably been in use "unofficially" since designers started prototyping products and watching users use the prototypes.{{Citation needed|date=April 2010}} Since its official definition and naming its use has rapidly expanded to many other software industries,<ref>Medlock, M.C., Wixon, D., McGee, M., & Welsh, D. (2005). The Rapid Iterative Test and Evaluation Method: Better Products in Less Time. In Bias, G., & Mayhew, D. (Eds.), ''Cost Justifying Usability'' (pp. 489-517). San Francisco: Morgan Kaufmann</ref> including interface design research.<ref>{{Cite journal |last=Tennant |first=Ryan |last2=Tetui |first2=Moses |last3=Grindrod |first3=Kelly |last4=Burns |first4=Catherine M |date=2023 |title=Multi-Disciplinary Design and Implementation of a Mass Vaccination Clinic Mobile Application to Support Decision-Making |url=https://ieeexplore.ieee.org/document/9963920/ |journal=IEEE Journal of Translational Engineering in Health and Medicine |volume=11 |pages=60–69 |doi=10.1109/JTEHM.2022.3224740 |issn=2168-2372 |pmc=PMC9842226 |pmid=36654771}}</ref>


== References ==
== References ==

Revision as of 23:49, 19 February 2023

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.

"As Researchers you get a lot of fundamental training on what constitutes actionable proof. That fundamental training focuses on 'completing your research' before drawing conclusions. In publishing RITE we wanted Researchers to acknowledge that in the correct circumstances you can make strong and accurate conclusions and 'complete research' quite quickly. Perhaps more importantly, the standard literature (of the time) on usability testing was indexed on accurate identification of problem areas. The key word in the RITE acronym is Iterative. Through iteration you can prove that something is fixed, which we felt was a more important way to think about research findings. Find a thing. That's nice. Find and fix it. Far better." — Ramon Romero[6]

Initially it was documented as being used in the PC games business, but in all truth it has probably been in use "unofficially" since designers started prototyping products and watching users use the prototypes.[citation needed] Since its official definition and naming its use has rapidly expanded to many other software industries,[7] including interface design research.[8]

References

  1. ^ Medlock, M.C., Wixon, D., Terrano, M., Romero, R., and Fulton, B. (2002). [1] Using the RITE method to improve products: A definition and a case study. Presented at the Usability Professionsals Association 2002, Orlando Florida.
  2. ^ Dennis Wixon, Evaluating usability methods: why the current literature fails the practitioner, interactions, v.10 n.4, July + August 2003
  3. ^ Dumas J., and Redish J.C. (1993). A Practical Guide to Usability Testing. Ablex, Norwood, N.J.
  4. ^ Jakob Nielsen, 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.), p.394-401, September 1989, Boston, Massachusetts, United States
  5. ^ Drachen, Anders; Mirza-Babaei, Pejman; Nacke, Lennart, 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.
  6. ^ "RITE Method: Comprehensive guide for Rapid Iterative Testing and Evaluation". www.hellopingpong.com. Retrieved 2020-07-07.
  7. ^ Medlock, M.C., Wixon, D., McGee, M., & Welsh, D. (2005). The Rapid Iterative Test and Evaluation Method: Better Products in Less Time. In Bias, G., & Mayhew, D. (Eds.), Cost Justifying Usability (pp. 489-517). San Francisco: Morgan Kaufmann
  8. ^ Tennant, Ryan; Tetui, Moses; Grindrod, Kelly; Burns, Catherine M (2023). "Multi-Disciplinary Design and Implementation of a Mass Vaccination Clinic Mobile Application to Support Decision-Making". IEEE Journal of Translational Engineering in Health and Medicine. 11: 60–69. doi:10.1109/JTEHM.2022.3224740. ISSN 2168-2372. PMC 9842226. PMID 36654771.{{cite journal}}: CS1 maint: PMC format (link)

See also


Stub icon

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=RITE_Method&oldid=1140407759"