Designers and developers can get quick, targeted feedback on their designs using a range of tools like design surveys, click tests, navigation tests, and preference tests.

These type of tools can test the usability, effectiveness, and overall user experience of digital products and designs.

We’ll outline some examples of tests and how to think about testing your product in general.

Instructions & Framing

When creating a test, you’ll want to give the testers a brief scenario of what is happening. Due to the nature of this platform and testing, you’ll be getting feedback from people who may or may not be actual users (although they might be at some point depending on the platform you’re testing).

Depending on the flow you want feedback on, a customer may also need to have the scenario set up for them.

Example

Scenario:
Your mobile device has recently been damaged. You have device protection insurance.

You'll be asked the following:

  1. General questions about plans and claims
  2. A click test
  3. Preference test with follow up questions

Types of Questions

These are some of the more common types of questions you can set up:
  1. Linear Scale
  2. Single choice / Multiple Choice
  3. Short / Long response

Navigation / Click Test

A navigation or click test can provide feedback around:

  • Accuracy
  • Navigating from point A to point B
  • Clear Calls to Action
  • Content
  • Time on task

You can ask follow up questions regarding the users experience while going through the test.

Preference Tests

Typically used to understand preferences and attitudes towards different design options. The goal of preference testing is to determine which option users prefer and to identify any trends or patterns in their preferences.

Some common use cases for preference testing include:

  • Branding and visual identity
  • User interface design
  • Content and messaging
  • Product features

Final Thoughts

There’s a lot of complexity that you can set up in UsabilityHub like creating questions that are dependent on each other, creating long tests, etc. But it’s typically better to keep things simple. It’ll get you better results that are easy to interpret and have more actionable insights into the problems you’re trying to solve.

UX Practice Home