We currently have 5 templates available that help provide structure based on where you’re at in your process so it’s easier to hop right in. You can access these templates by selecting the down arrow right next to the "Create Test" button:
Read on to learn about when and why to use each template, how each works, and some useful recommendations.
When to use: You have multiple variations of an interface, and are trying to determine which is more effective.
How it Works >2 test types, Click (with multiple variations) and Preference
- Click Test (Multi-variate): Click where you would expect to proceed to the checkout screen". This helps you determine the user's success rate and response time. Make sure that all the screens you upload have the context needed to execute the task you give.
- Preference: Put the same variations from the Click Test into a preference test. This helps us understand their aesthetic preference. Placing this question second prevents exposure bias that may muddy the results of the Click Test.
Why to use: When you want to determine which variation of your design is more effective and usable by a user, you want to gauge two things: their ability to take action successfully and what is easiest for them to comprehend. Multi-variate testing can give you trends in how well a user can use your designs, without the danger of them being biased by the other design, then a preference test lets the user choose their preferred layout after gaining context from the tasks they did.
Recommend: You'll want to compare two key metrics on the multivariate click test: success percentage and response time. How did one stack up against the other? Then take the preference choice into account and make sure to ask them why they chose their preference! Quantitative data becomes much more impactful when it's accompanied by qualitative data.
When to use: You've just launched a new product, service, or website, and you would like to get direct feedback from your users.
How it Works > 3 test types, Free Response, Multiple Choice, NPS
- Free Response: Upload an image of your newly completed product or site. Ask the users to interpret what they see on the page, describe what they see and what actions they can take.
This allows you to see if users comprehend the context of the page before given any tasks or questions that might give them a hint.
- Multiple Choice Ask for specific feedback on the image from the previous question (Free Response). Multiple choice allows you to get structured feedback that will help you quantify the reactions you get.
- NPS Utilize the NPS to understand the likelihood that users will use and recommend your product or service.
Why to use: You just launched so your done now, right? NOPE. Now is the time to refine, and this template will get you started with a whole slew of new feedback to use in the next iteration.
Recommend: Apply images for direct context on your survey questions, or simply poll your audience from a contextual source. This can be a great tool when leveraging it against a customer list, or when providing a survey link on your website. (Can't upload your customer lists? Reach out to us to learn more about it: [email protected])
When to use: When you want to determine how visual or hierarchical changes affect your users as they use or view your designs.
How it Works >6 questions, utilizing 2 test types, Click and Preference
- Click Test: Upload a screen and ask users to perform a task that helps them get perspective and context. ex: you may want to ask your users to find something really obscure on the page so you know they'll have spent some time considering the page.
- Preference: Upload the different versions of your views that have the changes you are trying to test for. Make sure you have specific items you are trying to test for (i.e. Color, hierarchy, menu layouts, etc.).
- Preference: More variations of the same view, with discrete changes.
- Click Test: Next, upload a new screen (not the same as before). Like before, this click test is designed to build context for the following preference questions.
- Preference: Upload the variations of the screen from the Click test. You should be testing the same kind of changes you tested for in the first two preference tests, just in a new screen.
- Preference: More variations of the same view, with discrete changes.
Why to use: By setting context, then asking for preference around a focused set of changes the feedback you receive will likewise be more focused. Testing the same kinds of changes across multiple screens helps you better understand what aspects of the changes were truly effective.
Recommend: Keep the differences between variations narrow and focused. You want your users commenting on specific changes, not sweeping revolutions.
This allows you to make informed decisions on each individual change with clear data to back you up
When to use: When you aren't sure whether users will understand the page correctly or lose the context of a page.
How it Works >4 questions, utilizing 2 test types, Free Response and Click
- Free Response: Upload a screen and ask your users to describe what they see.
- Click Test: First impression in hand, give the testers a directive to complete with the same screen from the Free Response question. Pay careful attention to how their initial perception differs from their response to the directive.
- Free Response: Upload a new screen and ask user to describe what they see.
- Click Test: Same as last time around, ask a directive or series of directives about the screen from the Free Response. You can repeat this combination as many times as you like.
Why to use: By asking users to describe the screen before giving them any directive, it gives them a chance to process what’s going on in isolation. This gives us a chance to audit what bias they bring with them, and also helps us make sure they understand the context better when given a specific directive later.
Recommend: Don't use this test method if you are trying to diagnose response time. This test is especially helpful if you are attempting to evoke more thoughtful responses to your directives.
When to use: You have multiple states of a screen, or UI based workflow and you want to gauge a user's ability to execute actions throughout the entire flow.
How it Works >At least 3 questions, all Click Test types
- Click Test: Upload a screen and give the tester a flow based directive, ex: “Add 'Super Flow Diapers' to your cart”. This allows us to determine ability and speed to complete the first task in a flow.
- Click Test: Upload the next screen in the sequence and give the user another directive. NOTE: it's best to keep these "flow" tests focused on a discrete set of tasks to get the best results. If you have interactions/flows you need to test, try creating another test.
- Click Test: Upload the last screen in the sequence and provide the final directive. NOTE: You can add as many click questions as required to test your flow.
Why to use: To understand how users traverse through your app/website in simple and complex scenarios. This template is especially useful for workflows.
Recommend: Don't be narrowly focused solely on completion success, but also keep in mind how long it took users to find the desired interaction.
It will be simulated, but you can take an approximation of overall flow time from this sort of test as well.
Don't hesitate to reach out if you've got any additional questions!
The Helio Team