Fewer surprises,
not fewer checks

01Situation

The loop nobody owned

In regulated onboarding, some cases always need more information; that's the nature of KYC. Customers submitted documents, analysts reviewed them, and when something was unclear the case went back to the customer: a feedback loop. Each loop meant another email, another wait, another chance to give up.

02Problem

"Operational" friction that was product-critical

Loops were treated as a compliance workflow, invisible to product metrics. But they created uncertainty, drove up contact ratio, and caused customers to drop out before activation. Customers who entered a loop often failed to return in the same week, dragging down KYC completion and wallet load.

03Goal

Make loops visible, then make them rarer

Reframe feedback loops as a product metric with owners, causes and targets, then cut avoidable loops without loosening a single regulatory control.

06Diagnosis

Measure the loop like a funnel step

We instrumented where loops happened, why (loop reasons), how many communications each customer received, whether they returned after being asked for more, and how loops correlated with KYC completion and wallet load. The pattern was clear: weeks with spiking loops were the weeks cohort completion sank into the low/mid-40s. The single biggest driver was surprise, not scrutiny.

07Decision making

Don't optimise the UI in isolation

The easy play was polishing the upload screens. But loop causes lived across policy (what we ask for), operations (how we ask), and product (when we ask). I pushed for the harder, joined-up route: change the request patterns themselves, with KYC/CDD at the table, because a beautiful form that triggers three clarification emails still loses the customer.

08Solution

Five moves against avoidable loops

09Trade-offs

The best UX isn't fewer checks

We consciously did not reduce regulatory scrutiny to lift conversion. That trade wasn't on the table. We also accepted heavier coordination cost: policy-plus-product changes move slower than UI tweaks, but they're the ones that survive an audit and a quarter.

10Impact

A compliance workflow became a product lever

Loops went from anecdote to instrumented metric with named causes and owners. Avoidable loops became fixable; unavoidable ones became predictable for the customer. Completion pressure eased where loop reasons were addressed, and the contact ratio stopped climbing.

11Learning

Customers complete what they understand

In regulated onboarding, the best UX is not fewer checks, it's fewer surprises. Customers complete when they know what's needed, why it's needed, and what happens next.