5 ways to measure UX return on investment

Usability testing is one of the best ways to measure how easy and intuitive to use something is by testing it with real people. You can read about the basics of usability testing here.

‍

Earlier this year, a small team within Optimal Workshop completely redesigned the company blog. More than anything, we wanted to create something that was user-friendly for our readers and would give them a reason to return. I was part of that team, and we ran numerous sessions interviewing regular readers as well as people unfamiliar with our blog. We also ran card sorts, tree tests and other studies to find out all we could about how people search for UX content. Unsurprisingly, one of the most valuable activities we did was usability testing – sitting down with representative users and watching them as they worked through a series of tasks we provided. We asked general questions like “Where would you go to find information about card sorting”, and we also observed them as they searched through our website for learning content.

‍

By stripping away any barriers between ourselves and our users and observing them as they navigated through our website and learning resources, as well as those of other companies, we were able to build a blog with these people’s behaviors and motivations in mind.

‍

Usability testing is an invaluable research method, and every user researcher should be able to run sessions effectively. Here are 5 tips for doing so, in no particular order.

‍

1. Clarify your goals with stakeholders

‍

Never go into a usability test blind. Before you ever sit down with a participant, make sure you know exactly what you want to get out of the session by writing down your research goals. This will help to keep you focused, essentially giving you a guiding light that you can refer back as you go about the various logistical tasks of your research. But you also need to take this a step further. It’s important to make sure that the people who will utilize the results of your research – your stakeholders – have an opportunity to give you their input on the goals as early as possible.

‍

If you’re running usability tests with the aim of creating marketing personas, for example, meet with your organization’s marketing team and figure out the types of information they need to create these personas. In some cases, it’s also helpful to clarify how you plan to gather this data, which can involve explaining some of the techniques you’re going to use.

‍

Lastly, find out how your stakeholders plan to use your findings. If there are a lot of objectives, organize your usability test so you ask the most important questions first. That way, if you end up going off track or you run out of time you’ll have already gathered the most important data for your stakeholders.

‍

2. Be flexible with your questions

‍

A list of pre-prepared questions will help significantly when it comes time to sit down and run your usability testing sessions. But while a list is essential, sometimes it can also pay to ‘follow your nose’ and steer the conversation in a (potentially) more fruitful direction.

‍

How many times have you been having a conversation with a friend over a drink or dinner, only for you both to completely lose track of time and find yourselves discussing something completely unrelated? While it’s not good practice to let your usability testing sessions get off track to this extent, you can surface some very interesting insights by paying close attention to a user’s behavior and answers during a testing session and following interesting leads.

‍

Ideally, and with enough practice, you’ll be able to answer your core (prepared) questions and ask a number of other questions that spring to mind during the session. This is a skill that takes time to master, however.

‍

3. Write a script for your sessions

‍

While a usability test script may sound like a fancy name for your research questions, it’s actually a document that’s much more comprehensive. If you prepare it correctly (we’ll explain how below), you’ll have a document that you can use to capture in-depth insights from your participants.

‍

Here are some of the key things to keep in mind when putting together your script:

‍

• Write a friendly introduction – It may sound obvious, but taking the time to come up with a friendly, warm introduction will get your sessions off to a much better start. The bonus of writing it down is that you’re far less likely to forget it!
• Ask to record the session – It’s important to record your session (whether through video or audio), as you’ll want to go back later and analyze any details you may have missed. This means asking for explicit permission to record participants. In addition to making them feel more comfortable, it’s just good practice to do so.
• Allocate time for the basics – Don’t dive into the complex questions first, use the first few minutes to gather basic data. This could be things like where they work and their familiarity with your organization and/or product.
• Encourage them to explain their thought process – “I’d like you to explain what you’re doing as you make your way through the task”. This simple request will give you an opportunity to ask follow-up questions that you otherwise may not have thought to ask.
• Let participants know that they’re not being tested – Whenever a participant steps into the room for a test, they’re naturally going to feel like they’re being tested. Explain that you’re testing the product, not them. It’s also helpful to let them know that there are no right or wrong answers. This is an important step if you want to keep them relaxed.

‍

It’s often easiest to have a document with your script printed out and ready to go for each usability test.

‍

4. Take advantage of software

‍

You’d never see a builder without a toolbox full of a useful assortment of tools. Likewise, software can make the life of a user research that much easier. The paper-based ways of recording information are still perfectly valid, but introducing custom tools can make both the logistics of user research and the actual sessions themselves much easier to manage.

‍

Take a tool like Calendly, for example. This is a powerful piece of scheduling software that almost completely takes over the endless back and forth of scheduling usability tests. Calendly acts as a middle man between you and your participants, allowing you to set the times you’re free to host usability tests, and then allowing participants to choose a session that suits them from these times.

‍

Our very own Reframer makes the task of running usability tests and analyzing insights that much easier. During your sessions, you can use Reframer to take comprehensive notes and apply tags like “positive” or “struggled” to different observations. Then, after you’ve concluded your tests, Reframer’s analysis function will help you understand wider themes that are present across your participants.

‍

There’s another benefit to using a tool like Reframer. Keeping all of your notes in place will mean you easily pull up data from past research sessions whenever you need to.

‍

5. Involve others

‍

Usability tests (and user interviews, for that matter) are a great opportunity to open up research to your wider organization. Whether it’s stakeholders, other members of your immediate team or even members of entirely different departments, giving them the chance to sit down with users will show them how their products are really being used. If nothing else, these sessions will help those within your organization build empathy with the people they’re building products for.

‍

There are quite a few ways to bring others in, such as:

‍

• To help you set up the research – This can be a helpful exercise for both you (the researcher) and the people you’re bringing in. Collaborate on the overarching research objectives, ask them what types of results they’d like to see and what sort of tasks they think could be used to gather these results.
• As notetakers – Having a dedicated notetaker will make your life as a researcher significantly easier. This means you’ll have someone to record any interesting observations while you focus on running the session. Just let them know what types of notes you’d like to see.
• To help you analyze the data – Once you’ve wrapped up your usability testing sessions, bring others in to help analyze the findings. There’s a good chance that an outside perspective will catch something you may miss. Also, if you’re bringing stakeholders into the analysis stage, they'll get a clearer picture of what it means and where the data came from.

‍

There are myriad other tips and best practices to keep in mind when usability testing, many of which we cover in our introductory page. Important considerations include taking good quality notes, carefully managing participants during the session (not giving them too much guidance) and remaining neutral throughout when answering their questions. If you feel like we’ve missed any really important points, feel free to leave a comment!

‍

Read more

‍

• Usability testing 101 – About to run your first usability test? Check out our handy 101 guide. You’ll also learn how you can use our qualitative research tool Reframer most effectively.
• What is usability testing? – Learn about the concepts of usability testing and how you can develop a plan for your own testing sessions.
• How to run fast and affordable usability tests with hard-to-reach, high-earning users – Finding the right participants for your usability tests can seem pretty tricky. Here’s how you can get the right people for your particular project.

There’s not much a parent won’t do to ensure their child has the best chance of succeeding in life. Unsurprisingly, things are much the same in product development. Whether it’s a designer, manager, developer or copywriter, everyone wants to see the product reach its full potential.

‍

Key to a product’s success (even though it’s still not widely practiced) is UX research. Without research focused on learning user pain points and behaviors, development basically happens in the dark. Feeding direct insights from customers and users into the development of a product means teams can flick the light on and make more informed design decisions.

‍

While the benefits of user research are obvious to anyone working in the field, it can be a real challenge to convince others of just how important and useful it is. We thought we’d help.

‍

Define user research

‍

If you want to sell the importance of UX research within your organization, you’ve got to ensure stakeholders have a clear understanding of what user research is and what they stand to gain from backing it.

‍

In general, there are a few key things worth focusing on when you’re trying to explain the benefits of research:

‍

• More informed design decisions: Companies make major design decisions far too often without considering users. User research provides the data needed to make informed decisions.
• Less uncertainty and risk: Similarly, research reduces risk and uncertainty simply by giving companies more clarity around how a particular product or service is used.
• Retention and conversion benefits: Research means you’ll be more aligned with the needs of your customers and prospective customers.

‍

Use the language of the people you’re trying to convince. A capable UX research practice will almost always improve key business metrics, namely sales and retention.

‍

The early stages

‍

When embarking on a project, book in some time early in the process to answer questions, explain your research approach and what you hope to gain from it. Here are some of the key things to go over:

‍

• Your objectives: What are you trying to achieve? This is a good time to cover your research questions.
• Your research methods: Which methods will you be using to carry out your research? Cover the advantages of these methods and the information you’re likely to get from using them.
• Constraints: Do you see any major obstacles? Any issues with resources?
• Provide examples: Nothing shows the value of doing research quite like a case study. If you can’t find an example of research within your own organization, see what you can find online.

‍

Involve others in your research

‍

When trying to convince someone of the validity of what you’re doing, it’s often best to just show them. There are a couple of effective ways you can do this – at a team or individual level and at an organizational level.

‍

We’ll explain the best way to approach this below, but there’s another important reason to bring others into your research. UX research can’t exist in a vacuum – it thrives on integration and collaboration with other teams. Importantly, this also means working with other teams to define the problems they’re trying to solve and the scope of their projects. Once you’ve got an understanding of what they’re trying to achieve, you’ll be in a better position to help them through research.

‍

Educate others on what research is

‍

Education sessions (lunch-and-learns) are one of the best ways to get a particular team or group together and run through the what and why of user research. You can work with them to work out what they’d like to see from you, and how you can help each other.

‍

Tailor what you’re saying to different teams, especially if you’re talking to people with vastly different skill sets. For example, developers and designers are likely to see entirely different value in research.

‍

Collect user insights across the organization

‍

Putting together a comprehensive internal repository focused specifically on user research is another excellent way to grow awareness. It can also help to quantify things that may otherwise fall by the wayside. For example, you can measure the magnitude of certain pain points or observe patterns in feature requests. Using a platform like Notion or Confluence (or even Google Drive if you don’t want a dedicated platform), log all of your study notes, insights and research information that you find useful.

‍

Whenever someone wants to learn more about research within the organization, they’ll be able to find everything easily.

‍

Bring stakeholders along to research sessions

‍

Getting a stakeholder along to a research session (usability tests and user interviews are great starting points) will help to show them the value that face-to-face sessions with users can provide.

‍

To really involve an observer in your UX research, assign them a specific role. Note taker, for example. With a short briefing on best-practices for note taking, they can get a feel for what’s like to do some of the work you do.

‍

You may also want to consider bringing anyone who’s interested along to a research session, even if they’re just there to observe.

‍

Share your findings – consistently

‍

Research is about more than just testing a hypothesis, it’s important to actually take your research back to the people who can action the data.

‍

By sharing your research findings with teams and stakeholders regularly, your organization will start to build up an understanding of the value that ongoing research can provide, meaning getting approval to pursue research in future becomes easier. This is a bit of a chicken and egg situation, but it’s a practice that all researchers need to get into – especially those embedded in large teams or organizations.

‍

Anything else you think is worth mentioning? Let us know in the comments.

‍

Read more

‍

• Selling your design recommendations to clients and colleagues – Guest writer Jeff Tang outlines some of his techniques for presenting UX recommendations and answering objections.
• Quantifying the ROI of UX – Ashlea McKay delves into one of the toughest UX questions to answer: “What do we get for our money?”
• How to lead a UX team – With user-centered design growing in organizations around the world, we’ll need capable leaders to run UX teams.
• How do I explain what UX is? – Ashlea McKay covers how you can explain UX to people who may not necessarily have familiarity with the field.

In the realm of financial services, complexity isn't just a challenge, it's the default state. From intricate investment products to multi-layered insurance policies to complex fee structures, financial services are inherently complicated. But your users don't want complexity; they want confidence, clarity, and control over their financial lives.

‍

‍

How to keep things simple with good UX research 

‍

Understanding how users perceive and navigate complexity requires systematic research. Optimal's platform offers specialized tools to identify complexity pain points and validate simplification strategies:

‍

Uncover Navigation Challenges with Tree Testing

‍

Complex financial products often create equally complex navigation structures:

‍

How can you solve this? 

‍

• Test how easily users can find key information within your financial platform
• Identify terminology and organizational structures that confuse users
• Compare different information architectures to find the most intuitive organization

‍

‍

Identify Confusion Points with First-Click Testing

‍

Understanding where users instinctively look for information reveals valuable insights about mental models:

‍

How can you solve this? 

‍

• Test where users click when trying to accomplish common financial tasks
• Compare multiple interface designs for complex financial tools
• Identify misalignments between expected and actual user behavior

‍

‍

Understand User Mental Models with Card Sorting

‍

Financial terminology and categorization often don't align with how customers think:

‍

How can you solve this? 

• Use open card sorts to understand how users naturally group financial concepts
• Test comprehension of financial terminology
• Identify intuitive labels for complex financial products

‍

‍

‍

‍

Practical Strategies for Simplifying Financial UX

‍

1. Progressive Information Disclosure

‍

Rather than bombarding users with all information at once, layer information from essential to detailed:

‍

• Start with core concepts and benefits
• Provide expandable sections for those who want deeper dives
• Use tooltips and contextual help for terminology
• Create information hierarchies that guide users from basic to advanced understanding

‍

‍

2. Visual Representation of Numerical Concepts

‍

Financial services are inherently numerical, but humans don't naturally think in numbers—we think in pictures and comparisons.

‍

What could this look like? 

‍

• Use visual scales and comparisons instead of just presenting raw numbers
• Implement interactive calculators that show real-time impact of choices
• Create visual hierarchies that guide attention to most relevant figures
• Design comparative visualizations that put numbers in context

‍

‍

3. Contextual Decision Support

‍

Users don't just need information; they need guidance relevant to their specific situation.

‍

How do you solve for this? 

‍

• Design contextual recommendations based on user data
• Provide comparison tools that highlight differences relevant to the user
• Offer scenario modeling that shows outcomes of different choices
• Implement guided decision flows for complex choices

‍

‍

4. Language Simplification and Standardization

‍

Financial jargon is perhaps the most visible form of unnecessary complexity. So, what can you do? 

‍

• Develop and enforce a simplified language style guide
• Create a financial glossary integrated contextually into the experience
• Test copy with actual users, measuring comprehension, not just preference
• Replace industry terms with everyday language when possible

‍

‍

‍

‍

Measuring Simplification Success

‍

To determine whether your simplification efforts are working, establish a continuous measurement program:

‍

1. Establish Complexity Baselines

‍

Use Optimal's tools to create baseline measurements:

‍

• Success rates for completing complex tasks
• Time required to find critical information
• Comprehension scores for key financial concepts
• User confidence ratings for financial decisions

‍

‍

2. Implement Iterative Testing

‍

Before launching major simplification initiatives, validate improvements through:

‍

• A/B testing of alternative explanations and designs
• Comparative testing of current vs. simplified interfaces
• Comprehension testing of revised terminology and content

‍

‍

3. Track Simplification Metrics Over Time

‍

Create a dashboard of key simplification indicators:

‍

• Task success rates for complex financial activities
• Support call volume related to confusion
• Feature adoption rates for previously underutilized tools
• User-reported confidence in financial decisions

‍

‍

‍

‍

Where rubber hits the road: Organizational Commitment to Clarity

‍

True simplification goes beyond interface design. It requires organizational commitment at the most foundational level:

‍

• Product development: Are we creating inherently understandable products?
• Legal and compliance: Can we satisfy requirements while maintaining clarity?
• Marketing: Are we setting appropriate expectations about complexity?
• Customer service: Are we gathering intelligence about confusion points?

‍

When there is a deep commitment from the entire organization to simplification, it becomes part of a businesses’ UX DNA. 

‍

‍

‍

‍

‍

Conclusion: The Future Belongs to the Clear

‍

As financial services become increasingly digital and self-directed, clarity bcomes essential for business success. The financial brands that will thrive in the coming decade won't necessarily be those with the most features or the lowest fees, but those that make the complex world of finance genuinely understandable to everyday users.

‍

By embracing clarity as a core design principle and supporting it with systematic user research, you're not just improving user experience, you're democratizing financial success itself.

‍