How to evaluate product UX: 7 steps

Assess your UX by identifying relevant metrics and research methodology. Monitor these indicators in each new version of the product using the same research method.

UX assessment (aka benchmarking) is the process of assessing the user experience when using a product or service using certain metrics and comparing their relative performance to standards. You can determine these metrics using quantitative usability testing, analytics, or surveys.

Consider doing a comparative study if you want to:

Track the overall progress of a product or service;
Compare your UX with an earlier version, competitor, industry benchmark, or goal defined by stakeholders;
Demonstrate the value of the UX effort and your work.

At a high level, benchmarking is a method of assessing the overall performance of a product. Comparative studies are usually conducted at the end of each design cycle before starting the next.

Benchmarking is often a whole complex of activities, rather than a one-off event: many organizations repeatedly do analytics after the release of new versions of their projects. Benchmarking provides accountability and measures progress.

Process overview

In this article, we’ll walk you through a high-level, seven-step process for creating a test program. He will require overtime to figure out what and how to measure. However, once you define the research structure, the process repeats itself, requiring much less effort.

Step 1. Selecting the measurement object

Focus on the key metrics that best reflect the quality of the UX you’re measuring. Look for metrics that fit your UX and company goals.

However, before you decide which metrics to select, you must set the context for your research. In other words, consider questions like:

What product are you focusing on? (website, application, etc.)
Which user group will you target?
What tasks or functions do you want to measure?


Define the main tasks that users are solving with your products. If your organization does not have existing core tasks, you can start by documenting (most) the tasks in the product. Then prioritize the list of tasks and select about 5–10 of them that will be most important to your users.

The table below lists several possible product and task scenarios. Each product has only one task assigned, but in real life you will probably have more than one task.

Now that you have a list of tasks, how can you measure them? Google’s HEART platform provides an overview of the different types of metrics that can be collected and analyzed. The following table represents the adaptation of the structure of the UHPUE:

Note that the task execution time as a measure of engagement should be high (for example, the time spent reading articles on a newspaper website), while the task execution time as a performance indicator should be low. In other words, the same change can be successful or not very successful, depending on what is being measured.

Choose metrics that will matter in the long run, since ideally you will collect them repeatedly over the years. Try to sample 2–4 metrics from different aspects of your UX.

Here are some metrics you can track for the tasks in the previous example.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store