Hypotheses are a necessary tool for site testing. A hypothesis can be thought of as a short story that predicts how users will react when a site change is introduced.<\/p>\n\n\n\n
Hypotheses are valuable because they keep you focused. If you can\u2019t say what impact you expect a change will have or why you believe the change will work, it\u2019s a good time to dig into the evidence and make sure you really understand what\u2019s going on. Writing a hypothesis is an early test of your idea to ensure it holds together before pushing changes live on the site. Hypotheses also make it easier to prioritize tests and share ideas with other people in the company.<\/p>\n\n\n\n
The elements of a hypothesis include: the area or functionality; what you want to change; why it matters to your audience; the metric you\u2019re tracking; and the predicted outcome.<\/p>\n\n\n\n
Let\u2019s run through a quick example of how this all comes together.<\/p>\n\n\n\n
Suppose you run a social media platform. You want your audience to interact with the platform more frequently both as creators and viewers of content. You believe the best way to accomplish this is to increase the number of photos people upload.<\/p>\n\n\n\n
Area or functionality:<\/em> Your audience\u2019s interaction with the site\u2019s interface, specifically uploading images.<\/p>\n\n\n\n What you want to change:<\/em> The strength of the button for image uploads so people are more likely to see it.<\/p>\n\n\n\n Why it matters to the audience:<\/em> Focus groups have indicated that customers love sharing photos over the social media network as it is quicker and easier than writing an update but it still feels like keeping in touch. However usability tests have shown that customers have trouble finding the button with which to upload photos. (Why you think it matters won\u2019t be in the final hypothesis statement but it\u2019s a very important step when building hypotheses. If you can\u2019t convincingly explain why you think an audience will react well to the change you are proposing, your hypothesis is more likely to fail.)<\/p>\n\n\n\n Metric:<\/em> The number of photo uploads divided by the number of total updates on the social media platform. Right now, photo uploads account for 3% of all updates.<\/p>\n\n\n\n Predicted outcome:<\/em> A 5% increase in photo uploads.<\/p>\n\n\n\n Pulling all these pieces together, the hypothesis is: \u201cMaking the photo upload button stronger will increase photo uploads by 5%.\u201d<\/p>\n\n\n\n If you have a great idea but are having trouble creating the elements of a hypothesis, it may be because you need to narrow down what you\u2019re testing. It is hard to create an effective hypothesis, and effective site tests, around an idea that is too broad. Another possibility is that your idea is sound but you need to refine it a bit more before you can act on it. By digging into available evidence, you can develop more insight into what will work and why.<\/p>\n","protected":false},"excerpt":{"rendered":" Hypotheses are a necessary tool for site testing. A hypothesis can be thought of as a short story that predicts how users will react when a site change is introduced. Hypotheses are valuable because they keep you focused. If you can\u2019t say what impact you expect a change will have or why you believe the change will work, it\u2019s a… Read More »How to Construct a Hypothesis for Site Testing<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"default","neve_meta_container":"default","neve_meta_enable_content_width":"off","neve_meta_content_width":70,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"off","neve_meta_disable_footer":"off","neve_meta_disable_title":"off"},"categories":[2],"tags":[9,6,5,8],"_links":{"self":[{"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/posts\/41"}],"collection":[{"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/comments?post=41"}],"version-history":[{"count":2,"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/posts\/41\/revisions"}],"predecessor-version":[{"id":43,"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/posts\/41\/revisions\/43"}],"wp:attachment":[{"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/media?parent=41"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/categories?post=41"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/grayson.consulting\/blog\/wp-json\/wp\/v2\/tags?post=41"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}