RITE Method

Description

A usability testing approach where the team fixes the prototype as soon as a problem is clearly identified, often after one participant, then tests the fix with the next.

RITE was developed at Microsoft Games Studios to speed up iteration in usability testing. Instead of running all sessions on a fixed prototype and reporting at the end, the product team observes each session together, agrees on problems and fixes those with clear causes and solutions immediately, sometimes after a single participant. The next participants test the revised version, which shows whether the fix works and whether it introduced new problems. Rigour comes from having decision-makers present, explicit criteria for when to change (obvious cause, clear fix, low cost) versus wait for more data, and logging every change and its outcome across sessions. The method trades statistical comparison for learning speed and works best with prototypes that can be changed quickly.

Attributes

Loss type
Renamed
Effort
Days

Steps

  1. Agree a test plan, task set and decision criteria for when a problem is fixed immediately versus after more sessions.
  2. Ensure decision-makers (designers, developers, product owner) observe every session.
  3. Run a session, then debrief immediately to list problems and decide which to fix now.
  4. Update the prototype before the next session for problems with clear causes and solutions.
  5. Continue with the next participant, checking whether fixes work and new problems appear; typical studies run 6-15 participants.
  6. Log every change, its rationale and subsequent results, and report the problem and fix trajectory.

Sources

  • Moderated Usability Tests
  • Using the RITE method to improve products (Medlock et al.)
  • Drachen, A., Mirza-Babaei, P. & Nacke, L. (eds), Games User Research (2018)

Also known as

  • Rapid Iterative Testing and Evaluation
  • RITE testing

Categories

  • User Research
  • Usability & Evaluation