Flowchart
What to fix after five usability tests
A decision path for each round of a small usability test
A decision path for founders after a round of five usability sessions on an MVP. Fix anything that stops two or more people finishing the core task, then problems three or more people hit, note the one-offs, and run five new people through the same tasks until a round turns up nothing new. It keeps small tests honest by counting people rather than vivid moments. Koji reports who finished and who got stuck on each task, which makes the first two questions quick to answer.
Where this appears
What's in this flowchart
Start: Five sessions done
- Did two or more people fail the core task?
- No: go to 2.
- Yes: Fix the blocker first. Hold new traffic until a second round passes. Then go to 4.
- Did three or more hit the same problem?
- No: go to 3.
- Yes: Fix it this round. Then go to 4.
- Note the one-off problems. Watch for them in the next round.
- Run five more people. Same tasks, same words, new people.
- Did the new round turn up anything new?
- No: go to 6.
- Yes: go back to 1.
- Finish: Test the next flow. Or ask whether people come back in week two.
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
html
<a href="https://www.koji.so/visuals/what-to-fix-after-five-usability-tests"><img src="https://www.koji.so/visuals/what-to-fix-after-five-usability-tests/what-to-fix-after-five-usability-tests.png" alt="Flowchart for what to fix after five usability tests: three questions, two fixes, a retest loop, ending in testing the next flow." width="1200" height="1403" /></a>
<p>Source: <a href="https://www.koji.so/visuals/what-to-fix-after-five-usability-tests">What to fix after five usability tests</a>, Koji</p>
