Introducing UserZoom’s single UX metric for experience benchmarking: the qxScore

If you’re looking for a simple way to show stakeholders that your product is definitively getting better through user research efforts, let us introduce you to the qxScore and the UZIndex!

For some time now, UX practitioners have struggled to come up with a single experience benchmarking score to share with their team and with stakeholders. Something that would allow teams to measure experience consistently and quantitatively, and most of all, be easily understood at a glance.

Unfortunately, it’s not as simple a task as one might assume. Questions that come up when brainstorming something like this tend to be:

What metrics should be included? How can we create a repeatable, apples-to-apples benchmarking score? How can we make it simple and easy to understand for even the least UX savvy executive?

Well, at UserZoom we do a lot of UX benchmarking. So much so that we have had ample time to ponder this very question, which is how the concept of a quality of experience score (qxScore) came to be in the first place.

What is the qxScore?

Here at UserZoom we have created our own UX scorecard program called the qxScore. Its purpose is to create a single benchmarking score for your product.

This is an experience score that combines various measurements, collecting both behavioral data (such as task success) and attitudinal data (such as ease of use, trust and appearance).

Once you’ve entered your results into our UX scorecard calculator we’ll generate a qxScorecard that looks like this:

The number in the circle, 72, is the single experience score for this particular product. The final score if you will. Going deeper, you can see the individual scores for component areas such as Trust and Appearance. Trust is strong, but Appearance needs some work.

Easy, right?

What are the benefits of using the qxScore?

The qxScore is a simple, clear and persuasive tool for communicating user research results to stakeholders and the team.

Being able to take the results to them and show that, using the previous example, their experience score was 72 out of 100 makes it easy for even the least UX savvy stakeholders to grasp the state of their product.

Why is this so important?

Well, for starters, getting executive buy-in for research can be difficult when they don’t clearly understand the results. Being able to quickly and easily get your point across to stakeholders – we had a qxScore of 72 and now it’s an 84 after our latest iteration – means it should help with getting future buy-in for benchmarking.

Second, it helps the team and the company at large understand where to focus and what to prioritize sans gut feelings.

UX Benchmarking 101

For an in-depth and entertaining guide to measuring UX, check out our free-to-download, 42 page guide to running both longitudinal and competitive benchmarking.