Testing with Preely
Our platform supports various types of user tests, here you get a quick overview.
In a usability test your participant complete different tasks while using your prototype. The tasks should be as realistic as possible and something that your end-users would be presented to, if the products was launched.
The tasks can be very specific (e.g. You are visiting our website for the first time, you have some questions regarding our services and want to contact us, find our email address) or very open (e.g. One of your friends has sent you a link to a website, open the link and take a look around), depending on the assumptions you are testing.
With a usability test you can identify:
- Problems in your solution/product/service
- Areas of improvements in your solution/product/service
- Your participant’s mental models of your solution/product/service
In a five second test, the test participant is shown a design or screenshot for exactly five seconds and afterward asked to answer questions about the experience and design.
With a five second test you can identify:
- How your UI design communicates your message
- How easy the offering or purpose of the product is identified
- The overall impression of your design
In a first-click test, the first click of multiple test participants is collected to analyze if your participants can find what they are looking for and if they can navigate your website, app or other digital products.
Using this information, you can start improving user flows and positioning of navigation items to create a smooth and intuitive experience for your users.
In a browsability test, your test participants browse around in your prototype for a certain amount of time, afterwards you can ask them questions about the experience and design of your prototype.
With a browsability test you can identify:
- What catches the participant’s attention
- If your UI design communicates your message and brand promise
- How easy the site is to navigate
- The overall impression of your prototype
Navigation tests are great for when you want to know how participants navigate your prototype. In a navigation test your participants are given a scenario to set the scene and then asked to complete different tasks in your prototype.
With a navigation test, you can:
- Understand your participants’ mental models
- Identify if your prototype is meeting your participants’ expectations about how it should work
- Identify if icons and labels in menus or on buttons are easily understood
- Investigate your prototype’s hierarchical structure and information architecture and get ideas for how to improve it
- Identify your participants’ cognitive strain by how much reading, remembering, and decisions making required before archiving the overall goal
Preference tests can be used when you want participants to choose between design variations, you want to hear which design your participants thinks communicate your message best, which design participants judges as most modern, etc. You just need to show them the design and afterwards ask them.
Examples of questions a preference test can answer:
- Which design they prefer
- Which design that looks the most trustworthy
- Which design that looks the most modern
- Which design that looks the easiest to use
Preely offers two ways of setting up a preference test, either: 1. Here you ask your participants to click on the design they prefer; 2.Here you show your design and afterwards ask the questions you want aswered.
When you want to test two (or more) versions of your design or prototype, you can conduct an AB test. An AB test could e.g. be on different layouts, placement of text, color, but also greater workflows, designs, etc.
Things to do before conducting the AB test:
- Define which variables you are testing in your design (the difference between A and B)
- Identify which metrics you want to focus on – is it performance metrics (which ones?) or self-reported metrics (which ones?)
- Consider if you need a within- or between subject design for your test (see Within- & Between Subject)
- For proper statistical analysis, you need to have at least 15 participants per version.
Let us know if you are missing any test types on the platform.