Building Trust Through Design for Financial Services

Financial regulations exist for good reason: to protect consumers, prevent fraud, and ensure market stability. But for UX professionals in the financial sector, these necessary guardrails often feel like insurmountable obstacles to creating seamless user experiences. How do we balance strict compliance requirements with the user-friendly experiences consumers increasingly demand?

‍

The Compliance vs. UX Tension

‍

The fundamental challenge lies in the seemingly contradictory goals of regulatory compliance and frictionless UX:

• Regulations demand verification steps, disclosures, documentation, and formality
• Good UX principles favor simplicity, speed, clarity, and minimal friction

This tension creates the "compliance paradox": the very features that make financial services trustworthy from a regulatory perspective often make them frustrating from a user perspective.

‍

Research Driven Compliance Design

‍

Addressing regulatory challenges in financial UX requires more than intuition, it demands systematic research to understand user perceptions, identify friction points, and validate solutions. Optimal's research platform offers powerful tools to transform compliance from a burden to an experience enhancer:

‍

Evaluate Information Architecture with Tree Testing

‍

Regulatory information is often buried in complex navigation structures that users struggle to find when needed:

‍

Implementation Strategy:

• Test how easily users can find critical compliance information
• Identify optimal placement for regulatory disclosures
• Compare different organizational approaches for compliance documentation

‍

Test Compliance Flows with First-Click Testing

‍

Understanding where users instinctively look and click during compliance-critical moments helps optimize these experiences:

‍

Implementation Strategy:

• Test different approaches to presenting consent requests
• Identify optimal placement for regulatory disclosures
• Evaluate where users look for more information about compliance requirements

‍

Understand Mental Models with Card Sorting

‍

Regulatory terminology often clashes with users' mental models of financial services:

‍

Implementation Strategy:

• Use open card sorts to understand how users categorize compliance-related concepts
• Test terminology comprehension for regulatory language
• Identify user-friendly alternatives to technical compliance language

‍

Key Regulatory Considerations Affecting Financial UX

‍

KYC (Know Your Customer) Requirements

‍

KYC procedures require financial institutions to verify customer identities, a process that can be cumbersome but is essential for preventing fraud and money laundering.

‍

Design Opportunity: Transform identity verification from a barrier to a trust-building feature by:

• Breaking verification into logical, manageable steps
• Setting clear expectations about time requirements and necessary documents
• Providing progress indicators and save-and-resume functionality
• Explaining the security benefits of each verification step

‍

Data Privacy Regulations (GDPR, CCPA, etc.)

‍

Modern privacy frameworks grant users specific rights regarding their data while imposing strict requirements on how financial institutions collect, store, and process personal information.

This poses a specific ux challenge: privacy disclosures and consent mechanisms can overwhelm users with legal language and interrupt core user journeys.

‍

Design Opportunity: Create privacy experiences that inform without overwhelming:

• Layer privacy information with progressive disclosure
• Use visual design to highlight key privacy choices
• Develop privacy centers that centralize user data controls
• Implement "just-in-time" consent requests that provide context

‍

AML (Anti-Money Laundering) Compliance

‍

AML regulations require monitoring unusual transactions and sometimes interrupting user actions for additional verification.

‍

Design Opportunity: Design for transparency and education:

• Provide clear explanations when additional verification is needed
• Offer multiple verification options when possible
• Create educational content explaining security measures
• Use friction strategically rather than uniformly

‍

Strategies for Compliance-Centered UX Design

‍

1. Bring Compliance Teams into the Design Process Early

‍

Rather than designing an ideal experience and then retrofitting compliance, involve your legal and compliance teams from the beginning. This collaborative approach can identify creative solutions that satisfy both regulatory requirements and user needs.

‍

2. Design for Transparency, Not Just Disclosure

‍

Regulations often focus on disclosure, ensuring users have access to relevant information. But disclosure alone doesn't ensure understanding. Focus on designing for true transparency that builds both compliance and comprehension.

‍

3. Use Progressive Complexity

‍

Not every user needs the same level of detail. Design interfaces that provide basic information by default but allow users to explore deeper regulatory details if desired.

‍

4. Transform Compliance into Competitive Advantage

‍

The most innovative financial companies are finding ways to turn compliance features into benefits users actually appreciate.

‍

Measuring Success: Beyond Compliance Checklists

‍

Traditional compliance metrics focus on binary outcomes: did we meet the regulatory requirement or not? For truly successful compliance-centered UX, consider measuring:

• Completion confidence - How confident are users that they've completed regulatory requirements correctly?
• Compliance comprehension - Do users actually understand key regulatory information?
• Trust impact - How do compliance measures affect overall trust in your institution?
• Friction perception - Do users view necessary verification steps as security features or annoying obstacles?

‍

The financial institutions that will thrive in the coming years will be those that stop viewing regulations as UX obstacles and start seeing them as opportunities to demonstrate trustworthiness, security, and respect for users' rights. By thoughtfully designing compliance into the core experience, rather than bolting it on afterward, we can create financial products that are both legally sound and genuinely user-friendly.

‍

Remember: Compliance isn't just about avoiding penalties, it's about treating users with the care and respect they deserve when entrusting you with their financial lives. And with the right research tools and methodologies, you can transform regulatory requirements from experience detractors into experience enhancers.

‍

‍

Knowing and understanding why and how your users use your product can be invaluable for getting to the nitty gritty of usability. Where they get stuck and where they fly through. Delving deep with probing questions into motivation or skimming over looking for issues can equally be informative.

‍

Usability testing can be done in several ways, each way has its benefits. Put super simply, usability testing literally is testing how useable your product is for your users. If your product isn't useable users will not stick around or very often complete their task, let alone come back for more.

‍

‍

What is usability testing?

‍

Usability testing is a research method used to evaluate how easy something is to use by testing it with representative users.

‍

These tests typically involve observing a participant as they work through a series of tasks involving the product being tested. Having conducted several usability tests, you can analyze your observations to identify the most common issues.

‍

We go into the three main methods of usability testing:

1. Moderated and unmoderated
2. Remote or in person
3. Explorative, assessment or comparative

‍

‍

1. Moderated or unmoderated usability testing

‍

Moderated usability testing

Moderated usability testing is done in-person or remotely by a researcher who introduces the test to participants, answers their queries, and asks follow-up questions. Often these tests are done in real time with participants and can involve other research stakeholders. Moderated testing usually produces more in-depth results thanks to the direct interaction between researchers and test participants. However, this can be expensive to organize and run.

‍

Top tip: Use moderated testing to investigate the reasoning behind user behavior.

‍

Unmoderated usability testing

‍
Unmoderated usability testing is done without direct supervision; likely participants are in their own homes and/or using their own devices to browse the website that is being tested. And often at their own pace.  The cost of unmoderated testing is lower, though participant answers can remain superficial and making follow-up questions can be difficult.

‍

Top tip: Use unmoderated testing to test a very specific question or observe and measure behavior patterns.

‍

‍

2. Research or in-person usability testing

‍

Remote usability testing

‍
‍Remote usability testing is done over the internet or by phone. Allowing the participants to have the time and space to work in their own environment and at their own pace. This however doesn’t give the researcher much in the way of contextual data because you’re unable to ask questions around intention or probe deeper if the participant makes a particular decision. Remote testing doesn’t go as deep into a participant’s reasoning, but it allows you to test large numbers of people in different geographical areas using fewer resources.

‍

Top tip: Use remote testing when a large group of participants are needed and the questions asked can be direct and unambiguous.

‍

In-person usability testing

‍
‍In-person usability testing, as the name suggests, is done in the presence of a researcher. In-person testing does provide contextual data as researchers can observe and analyze body language and facial expressions. You’re also often able to converse with participants and find out more about why they do something. However, in-person testing can be expensive and time-consuming: you have to find a suitable space, block out a specific date, and recruit (and often pay) participants.

‍

Top tip: In-person testing gives researchers more time and insight into motivation for decisions.

‍

‍

3. Explorative, Assessment or comparative testing

‍

These three usability testing methods generate different types of information:

‍

Explorative testing

‍
‍Explorative testing is open-ended. Participants are asked to brainstorm, give opinions, and express emotional impressions about ideas and concepts. The information is typically collected in the early stages of product development and helps researchers pinpoint gaps in the market, identify potential new features, and workshop new ideas.

‍

Assessment research

‍
‍Assessment research is used to test a user's satisfaction with a product and how well they are able to use it. It's used to evaluate general functionality.

‍

Comparative research

‍
‍Comparative research methods involve asking users to choose which of two solutions they prefer, and they may be used to compare a product with its competitors.

‍

Top tip: Depending on what research is being done, and how much qualitative or quantitative data is wanted.

‍

‍

Which method is right for you?

‍

Whether the testing is done in-person, remote, moderated or unmoderated will depend on your purpose, what you want out of the testing, and to some extent your budget. 

‍

Depending on what you are testing, each of the usability testing methods we explored here can offer an answer. If you are at the development stage of a product it can be useful to conduct a usability test on the entire product. Checking the intuitive usability of your website, to ensure users can make the best decisions, quickly. Or adding, changing or upgrading a product can also be the moment to check on a specific question around usability. Planning and understanding your objectives are key to selecting the right usability testing option for your project.

‍

Let's take a look at a couple of examples of usability testing.

‍

‍

1. Lab based, in-person moderated testing - mid-life website

‍

Imagine you have a website that sells sports equipment. Over time your site has become cluttered and disorganized, much like a bricks and mortar store may. You’ve noticed a drop in sales in certain areas. How do you find out what is going wrong or where users are getting lost? Having an in-person, lab (or other controlled environment), moderated usability test with users you can set tasks, watch (and record) what they do.

‍

The researcher can literally be standing or sitting next to the participant throughout, recording contextual information such as how they interacted with the mouse, laptop or even the seat. Watching for cues as to the comfort of the participant and asking questions about why they make decisions can provide richer insights. Maybe they wanted purple yoga pants, but couldn’t find the ‘yoga’ section which was listed under gym rather than a clothing section.

‍

Meaning you can look at how your stock is organised, or even investigate undertaking a card sort. This provides robust and fully rounded feedback on users behaviours, expectations and experiences. Providing data that can directly be turned into actionable directives when redeveloping the website. 

‍

‍

2. Remote, moderated assessment testing - app product development

‍

You are looking at launching an app for parents to access for information and updates for the school. It’s still in development stage and at this point you want to know how easy the app is to use. Setting some very specific set tasks for participants to complete the app can be sent to them and they can be left to complete (or not). Providing feedback and comments around the usability.

‍

The next step may be to use first click testing to see how and where the interface is clicked and where participants may be spending time, or becoming lost. Whilst the feedback and data gathered from this testing can be light, it will be very direct to the questions asked. And will provide data to back up (or possibly not) what assumptions were made.

‍

‍

3. Moderated, In-person, explorative testing - new product development

‍

You’re right at the start of the development process. The idea is new and fresh and the basics are being considered. What better way to get an understanding of what your users’ truly want than an explorative study.

‍

Open-ended questions with participants in a one-on-one environment (or possibly in groups) can provide rich data and insights for the development team. Imagine you have an exciting new promotional app that you are developing for a client. There are similar apps on the market but none as exciting as what your team has dreamt up. By putting it (and possibly the competitors) to participants they can give direct feedback on what they like, love and loathe.

‍

They can also help brainstorm ideas or better ways to make the app work, or improve the interface. All of this done, before there is money sunk in development.

‍

‍

Usability testing summary: When to use each method (and why)

‍

Key objectives will dictate which usability testing method will deliver the answers to your questions.

‍

Whether it’s in-person, remote, moderated or comparative with a bit of planning you can gather data around your users very real experience of your product. Identify issues, successes and failures. Addressing your user experience with real data, and knowledge can but lead to a more intuitive product.

When it comes to financial services, user experience goes way beyond just making things easy to use. It’s about creating a seamless journey and establishing trust at every touchpoint. Think about it: as we rely more and more on digital banking and financial apps in our everyday lives, we need to feel absolutely confident that our personal information is safe and that the companies managing our money actually know what they're doing. Without that trust foundation, even the most competitive brands will struggle with customer adoption.

‍

Why Trust Matters More Than Ever

‍

The stakes are uniquely high in financial UX. Unlike other digital products where a poor experience might result in minor frustration, financial applications handle our life savings, investment portfolios, and sensitive personal data. A single misstep in design can trigger alarm bells for users, potentially leading to lost customers.

‍

Using UX Research to Measure and Build Trust

‍

Building high trust experiences requires deep insights into user perceptions, behaviors, and pain points. The best UX platforms can help financial companies spot trust issues and test whether their solutions actually work.

‍

Identify Trust Issues with Tree Testing

‍

Tree testing helps financial institutions understand how easily users can find critical information and features:

‍

• Test information architecture to ensure security features and privacy information are easily discoverable
• Identify confusing terminology that may undermine user confidence
• Compare findability metrics for trust-related content across different user segments

‍

Optimize for Trustworthy First Impressions with First-Click Testing

‍

First-click testing helps identify where users naturally look for visual symbols and cues that are associated with security:

‍

• Test where users instinctively look for security indicators like references to security certifications
• Compare the effectiveness of different visual trust symbols (locks, shields, badges)
• Identify the optimal placement for security messaging across key screens

‍

Map User Journeys with Card Sorting

‍

Card sorting helps brands understand how users organize concepts. Reducing confusion, helps your financial brand appear more trustworthy, quickly:

‍

• Use open card sorts to understand how users naturally categorize security and privacy features
• Identify terminology that resonates with users' perceptions around security

‍

Qualitative Insights Through Targeted Questions

‍

Gathering qualitative data through strategically placed questions allows financial institutions to collect rich, timely insights about how much their customers trust their brand:

‍

• Ask open ended questions about trust concerns at key moments in the testing process
• Gather specific feedback on security terminology understanding and recognition
• Capture emotional responses to different trust indicators

‍

What Makes a Financial Brand Look Trustworthy?

‍

Visual Consistency and Professional Polish

‍

When someone opens your financial app or website, they're making snap judgments about whether they can trust you with their money. It happens in milliseconds, and a lot of that decision comes down to how polished and consistent everything looks.Clean, consistent design sends that signal of stability and attention to detail that people expect when money's involved.

‍

To achieve this, develop and rigorously apply a solid design system across all digital touchpoints including fonts, colors, button styles, and spacing, it all needs to be consistent across every page and interaction. Even small inconsistencies can make people subconsciously lose confidence.

‍

Making Security Visible

‍

Unlike walking into a bank where you can see the vault and security cameras, digital security happens behind the scenes. Users can't see all the protection you've built in unless you make a point of showing them.

‍

Highlighting your security measures in ways that feel reassuring rather than overwhelming gives people that same sense of "my money is safe here" that they'd get from seeing a bank's physical security.

‍

From a design perspective, apply this thinking to elements like:

‍

• Real time login notifications
• Transaction verification steps
• Clear encryption indicators
• Transparent data usage explanations
• Session timeout warnings

‍

You can test the success of these design elements through preference testing, where you can compare different approaches to security visualization to determine which elements most effectively communicate trust without creating anxiety.

‍

Making Complex Language Simple

‍

Financial terminology is naturally complex, but your interface content doesn't have to be. Clear, straightforward language builds trust so it’s important to develop a content strategy that:

‍

• Explains unavoidable complex terms contextually
• Replaces jargon with plain language
• Provides proactive guidance before errors occur
• Uses positive, confident messaging around security features

‍

You can test your language and navigation elements by using tree testing to evaluate user understanding of different terminology, measuring success rates for finding information using different labeling options.

‍

Create an Ongoing Trust Measurement Program

‍

A user research platform enables financial institutions to implement ongoing trust measurement across the product lifecycle:

‍

Establish Trust Benchmarks

‍

Use UX research tools to establish baseline metrics for measuring user trust:

‍

• Findability scores for security features
• User reported confidence ratings
• Success rates for security related tasks
• Terminology comprehension levels

‍

Validate Design Updates

‍

Before implementing changes to critical elements, use quick tests to validate designs:

‍

• Compare current vs. proposed designs with prototype testing
• Measure findability improvements with tree testing
• Evaluate usability through first-click testing

‍

Monitor Trust Metrics Over Time

‍

Create a dashboard of trust metrics that can be tracked regularly:

‍

• Task success rates for security related activities
• Time-to-completion for verification processes
• Confidence ratings at key security touchpoints

‍

Cross-Functional Collaboration to Improve Trust

‍

While UX designers can significantly impact brand credibility, remember that trust is earned across the entire customer experience:

‍

• Product teams ensure feature promises align with actual capabilities
• Security teams translate complex security measures into user-friendly experiences
• Marketing ensures brand promises align with the actual user experience
• ‍Customer service supports customers when trust issues arise

‍

Trust as a Competitive Advantage

‍

In an industry where products and services can often seem interchangeable to consumers, trust becomes a powerful differentiator. By placing trust at the center of your design philosophy and using comprehensive user research to measure and improve trust metrics, you're not just improving user experience, you're creating a foundation for lasting customer relationships in an industry where loyalty is increasingly rare.

‍

The most successful financial institutions of the future won't necessarily be those with the most features or the slickest interfaces, but those that have earned and maintained user trust through thoughtful UX design built on a foundation of deep user research and continuous improvement.

‍

‍