KR: Provide a rapid usability testing framework that acts as a leading indicator for SUS => 4/4, 100%
Background
This KR provides teams with a valid framework to use when testing for usability in a fast and rapid manner: Rapid Iteration Testing and Evaluation (RITE). This process can be used on nearly any experience measuring usability, including SUS-related usability improvements, thereby reducing the overall usability testing timeframe. Additionally, when executed properly, RITE results in a final design or experience that has been fully tested and ready to be shipped. This means that items that were RITE tested have a higher level of confidence that they truly are a usable experience.
The proposed process
The key element of the process is iterative usability testing using RITE. RITE is a type of usability testing where a solution to a usability problem is continuously being evaluated. Due to the continuous evaluation a smaller sample size per iteration is used. In addition identified usability problems are addressed before a new iteration starts.
RITE likely runs more than one milestone. The proposed process aims at giving teams a structure and familiarizing them with the principles of RITE, but flexibility to adapt it to a timeline that works for them.
RITE should not be conducted if the problem space is not clearly defined. If you can’t confidently tell what kind of usability problem occurs to users and why they are experiencing it, run a usability test first.
Challenges
- RITE testing requires time dedication during the testing window and tight collaboration.
- Globally distributed teams may find RITE challenging due to its' synchronous nature, but it can certainly be done asynchronously, too.
Open questions
- TBD
Checklist
-
Review process proposal with Director of Product Design -
Add documentation about RITE to handbook -
Share process with GitLab teams -
Find at least one team that is piloting the process in Q2 and adjust documentation/process as needed