Live data from Hacker News

You Only Need to Test with 5 Users (2000)

nngroup.com

111–112 of 112 posts

Re: You Only Need to Test with 5 Users (2000)

#111
post #63

This has been questioned (5 user theory). From 2008 research paper: http://www.simplifyinginterfaces.com/wp-content/uploads/2008... Excerpt: Historic reason: Both Nielsen (1993) and Virzi (1992) were writing in a climate in which the concepts of usability were still being introduced..They were striving to lighten the requirements of usability testing in order to make usability practices more attractive to those worki…

A few weeks ago, I tested an app with 50 users from different backgrounds, affinities, abilities ... etc.

Towards the end, we realized the past 20 or so tests have been a waste of time. Issues and improvements that arose from the first 20sh tests kept repeating themselves throughout every remaining session.

This sure increases confidence in your data, but really when you're in an MVP stage or you don't have much funding, you're better off testing with around 15 to 20 people and fix the issues that they find, because most likely, those issues are in fact very problematic and deserve more priority. More users will just yield more granular bugs and issues that you can schedule for later.

Re: You Only Need to Test with 5 Users (2000)

#112
Some key questions:

1. How extensively do those 5 people test the software? Do they test all features or just part of the software?

2. What is the background of those 5 people testing the software? Do they understand UX/good UI design and how well?

3. Are these 5 people just random users or professional test engineers?

4. How passionate are these 5 people about the product/service they are testing? How meaningful is it for them that the product actually works _really well_?

5. What is the quality level of feedback these 5 people can provide? Is it like "meh, this is ugly" or is it detailed, concrete and contains practical improvement ideas that can be easily implemented?

Post reply on HN