From ee41670721d774ab20f8dc36c052c8ff88319999 Mon Sep 17 00:00:00 2001 From: Chris Murray <39704901+chris-at-jobber@users.noreply.github.com> Date: Sat, 26 Jan 2019 00:53:10 -0700 Subject: [PATCH] Fix typo, add detail to article (#27098) Subdivide number of users and testing methodology into sections under a "Suggested Best Practices" section. --- .../product-design/usability-testing/index.md | 20 ++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/guide/english/product-design/usability-testing/index.md b/guide/english/product-design/usability-testing/index.md index 32485f8037..1c92286a9e 100644 --- a/guide/english/product-design/usability-testing/index.md +++ b/guide/english/product-design/usability-testing/index.md @@ -17,9 +17,23 @@ Designers should pay attention to the following potential issues: 4) The user indicates something that doesn't make sense to them 5) The user suggests a change to the design -It is also important to keep in mind that with more participants, more issues will be discovered through usability testing. It may also be beneficial to record participants' faces and audio, as well as the screen and any finger presses within a mobile application, if applicable. +### Suggested Best Practices -#### Citations +Every organization's processes will be different, but these suggested best practices are a good reference if you're just getting started with user testing. + +#### Number of users + +It is important to consider the number and type of testers. 1–3 is likely too small of a test group to catch all of your key issues. Conversely, the returns are diminishing after 8–10 users have tested your design; at this point, the most important issues will have been identified consistently. You should strive to test with a diverse group of users, as different perspectives and backgrounds can drive differing outcomes that are key to note at this stage. + +#### Observation methods + +For best results, a facilitator and an observer should run the test. The facilitator outlines the test objectives and conveys the tasks to be done; the observer records the user's reactions to using the design. It may also be beneficial to record participants' faces and audio, as well as the screen and any finger presses within a mobile application, if applicable. This can allow for a second look to better understand why a user reacted the way they did. + +#### Demonstrating value + +If there is hesitation within your organization around the idea of bringing in users for testing, reinforce the greater risk of shipping an unusable product. Catching usability bugs early on saves time and money, and greatly reduces the risk of delivering painful experiences to your users. + +### Citations Martin, Bella, and Bruce M. Hanington. Universal methods of design 100 ways to research complex problems, develop innovative ideas, and design effective solutions. Rockport Publishers, 2012. - +Laura Klein - [UX for Lean Startups](http://shop.oreilly.com/product/0636920026242.do)