Home → Insights

Why Compliance and UX Are Not Opposites

There is a belief in financial services that compliance and good customer experience are fundamentally in tension. That regulation adds friction. That the legal team and the design team are always fighting over the same screen. That the reason your digital loan application drops off before completion is because of what the regulators require — not how those requirements were built.

It is a belief so widely held that most digital transformation projects start from it. Compliance requirements go to one team. The customer journey goes to another. They meet at the end, and one side wins.

The result, almost always, is that the customer loses.

The framing is the problem

When I audit digital journeys, I score five dimensions: customer experience quality, compliance alignment, accessibility, efficiency, and brand trust. One of the most consistent patterns across the institutions I have assessed is this: journeys that score poorly on compliance almost always score poorly on customer experience too.

Not despite the compliance steps. Because of how they were designed.

When compliance is treated as a constraint that gets added at the end — a series of boxes to tick before launch — it shows in the journey. It shows in KYC steps that appear without explanation. In consent screens that read like legal briefs. In document requests that surface halfway through an application when the customer has already invested time and built expectation.

Each of those moments is a decision point. And most customers, encountering them without context, make the same decision: to leave.

The difference is intention

Consider a KYC verification step. Every regulated institution needs one. The question is not whether the step exists — it is how it is introduced, explained, and resolved.

A KYC step that appears without warning, with a clinical instruction to upload a government-issued document and nothing else, feels like an interrogation. It signals: this process was designed for our compliance team, not for you.

The same step — with two sentences that explain why the information is needed, how long it takes, and how it will be protected — feels different. It signals competence and care. It gives the customer a reason to continue.

The regulatory requirement has not changed. Only the design has.

The same principle applies to data consent screens, terms and conditions, affordability assessments, and every other point where a regulated institution must ask something of its customers. These are not obstacles in the customer journey. They are moments in it. And like every other moment, they can be handled well or handled badly.

What good compliance design actually looks like

The highest-scoring journeys I have seen — across banking, credit unions, and insurance — share a common characteristic. Compliance requirements are woven into the experience rather than bolted onto it.

What does that mean in practice? It means that document requirements are communicated at the start of an application, not revealed in step seven. It means that consent language is written for the person completing the form, not the person reviewing the audit. It means that when something is required by regulation, the institution says so — because transparency about why a step exists is one of the most effective trust signals a digital journey can offer.

It also means that the compliance team and the design team are in the same conversation from the beginning — not meeting at the end to negotiate what stays and what gets cut.

What the audit reveals

One of the more valuable outputs of a structured digital journey audit is the relationship between dimension scores. When compliance and customer experience are treated as separate problems, the scores diverge. When they are designed together, they tend to rise together.

This is not a coincidence. A journey that explains its compliance steps clearly is, by definition, communicating well with its customers. A journey that surfaces requirements at the right moment is, by definition, reducing cognitive load and abandonment risk. A journey where regulatory disclosures are written in plain language is, by definition, more accessible to the members it is trying to serve.

Compliance done well is not a compromise on customer experience. It is an expression of it.