{"id":730,"date":"2012-02-16T10:29:15","date_gmt":"2012-02-16T18:29:15","guid":{"rendered":"http:\/\/www.nadynerichmond.com\/blog\/?p=730"},"modified":"2012-02-16T10:29:15","modified_gmt":"2012-02-16T18:29:15","slug":"the-difference-between-good-user-research-and-great-user-research","status":"publish","type":"post","link":"https:\/\/www.nadynerichmond.com\/blog\/2012\/02\/16\/the-difference-between-good-user-research-and-great-user-research\/","title":{"rendered":"the difference between good user research and great user research"},"content":{"rendered":"<p>This morning, my team discussed the benefits and drawbacks of large-scale A\/B testing. \u00a0Websites like Google and Amazon often use A\/B testing where they randomly show some of their users a new version of a webpage, and measure whether the outcomes are different: a better click-through rate, for example. \u00a0There&#8217;s a lot be learned in this kind of testing. \u00a0It&#8217;s a powerful method for websites to learn about how design changes, both major and minor, can impact how users complete their task.<\/p>\n<p>However, it doesn&#8217;t give you a complete picture. \u00a0It tells you what happened, but it doesn&#8217;t tell you why it happened. \u00a0One of the differences between good user research and great user research is in what you learn and how you can apply that information in the future.<\/p>\n<p>In good user research, you learn that something happened. \u00a0Maybe you&#8217;ve learned that a user is completely blocked from finishing a task. \u00a0Maybe you&#8217;ve learned that users can complete their task 20% faster. \u00a0Maybe you&#8217;ve learned that, while they&#8217;re not doing anything faster, their satisfaction ratings are higher than usual. \u00a0Each and every one of these findings is important.<\/p>\n<p>Each and every one of those findings can be made better if you know the reason behind it. \u00a0Sometimes it&#8217;s reasonably obvious, but oftentimes it&#8217;s not<sup class='footnote'><a href='#fn-730-1' id='fnref-730-1' onclick='return fdfootnote_show(730)'>1<\/a><\/sup>. \u00a0When you know the reason why a change has improved or degraded the user&#8217;s experience, you have a better opportunity to innovate in the future. \u00a0You only have data. \u00a0You don&#8217;t have insight.<\/p>\n<p>Good user research allows you to react. \u00a0It allows you to evolve your designs. \u00a0With good user research, you will make improvements. \u00a0Your application will be better.<\/p>\n<p>Great user research allows you to learn more about your users. \u00a0It gives you insight into how they think and what they&#8217;re trying to accomplish. \u00a0It allows you to make intuitive leaps and to truly innovate. \u00a0With great user research, your greater understanding of your users will allow you to make improvements to your whole business, not just your application. \u00a0Your business will be better.<\/p>\n<div class='footnotes' id='footnotes-730'>\n<div class='footnotedivider'><\/div>\n<ol>\n<li id='fn-730-1'> And sometimes you think that the answer is obvious, but it turns out that the obvious answer isn&#8217;t the correct answer. <span class='footnotereverse'><a href='#fnref-730-1'>&#8617;<\/a><\/span><\/li>\n<\/ol>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>This morning, my team discussed the benefits and drawbacks of large-scale A\/B testing. \u00a0Websites like Google and Amazon often use A\/B testing where they randomly show some of their users a new version of a webpage, and measure whether the outcomes are different: a better click-through rate, for example. \u00a0There&#8217;s a lot be learned in &hellip; <a href=\"https:\/\/www.nadynerichmond.com\/blog\/2012\/02\/16\/the-difference-between-good-user-research-and-great-user-research\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">the difference between good user research and great user research<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-730","post","type-post","status-publish","format-standard","hentry","category-ux"],"_links":{"self":[{"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/posts\/730","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/comments?post=730"}],"version-history":[{"count":1,"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/posts\/730\/revisions"}],"predecessor-version":[{"id":731,"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/posts\/730\/revisions\/731"}],"wp:attachment":[{"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/media?parent=730"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/categories?post=730"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nadynerichmond.com\/blog\/wp-json\/wp\/v2\/tags?post=730"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}