When the screen wasn't the problem.

The reality was very different.

Over time, the onboarding journey had grown into more than twenty screens of identity verification, KYC requirements, compliance checks and product setup. Information was repeated, backend validations interrupted progress, and every additional step increased the chances that customers would leave before reaching the end.

This wasn't just a long form — it was an enterprise journey shaped by years of business rules, technical dependencies and regulatory requirements.

As completion rates declined, the obvious conclusion was that the interface had become too complicated. Simplify the screens, reduce the friction, and the problem would disappear.

The interface was part of the problem. Twenty-four screens asking for sensitive information is demanding for anyone.

But I wasn't convinced it was the whole story.

Before redesigning a single screen, I wanted to understand where customers were leaving, why they were leaving, and whether the experience itself — or the systems supporting it — were creating the friction.

That question changed the direction of the entire project.

Before redesigning anything, I needed to understand what customers were actually experiencing—not just what they were seeing.

The journey stretched across product, compliance, engineering, operations and core banking systems. Every screen represented decisions made somewhere else: identity verification, KYC requirements, backend validations, business rules and technical constraints.

Looking at the interface alone would only tell part of the story.

So we stepped back.

We analysed journey analytics to understand where customers were dropping off. We reviewed screen-level behaviour, investigated technical dependencies, spoke to stakeholders across the business and facilitated workshops to map the entire onboarding service from end to end.

As the picture became clearer, one thing stood out.

Customers weren't abandoning because of a single confusing screen. They were leaving because friction had accumulated across the entire experience. Long forms, repeated verification, unnecessary validations, unclear decision points and disconnected systems combined to create a journey that felt far longer than it needed to be.

Once we could see the whole system, the design decisions became much clearer.

The more we investigated, the clearer it became that this wasn't a problem we could solve by looking at a single screen or a single metric. Every piece of evidence told part of the story, but none of it told the whole story.

We started with the data—funnel analytics, step-by-step drop-off analysis, operational reporting and behavioural trends across the onboarding journey. The numbers showed us where customers were leaving, but they couldn't explain why.

That's where the conversations began. We spoke to business owners, listened to call-centre interactions, observed usability sessions, reviewed support cases and spent time with engineers, product teams and business stakeholders who understood the realities behind every validation, dependency and constraint. Branches, digital and customer support weren't separate channels—they were all part of the same customer experience.

Every workshop, customer conversation and research session uncovered another piece of the puzzle. Rather than validating assumptions, we challenged them. Every insight became an opportunity to ask a better question, and every question brought us closer to understanding where the experience was truly breaking down.

By the time we began redesigning the journey, the conversation had shifted. We were no longer debating how to improve individual screens—we had a shared understanding of the service we were trying to improve.

None of these problems could be solved by redesigning a screen alone.

To change an enterprise journey, everyone responsible for it needed to see the same problem, understand the same evidence and agree on what the future should look like.

That became the purpose of a large cross-functional workshop.

We brought together Product, Engineering, Architecture, Compliance, Operations, Business, Research and Design to map the onboarding experience from beginning to end. Every dependency, validation, customer decision and system interaction was placed on the wall.

For the first time, every team could see the entire journey instead of only the piece they owned.

The conversation immediately shifted.

Instead of debating interface changes, we started asking bigger questions.

• Why are existing customers entering the same journey as new customers?
• Which compliance steps are mandatory, and which exist because "that's how we've always done it"?
• Where are backend systems introducing unnecessary friction?
• Which customer problems should be solved first?
• How do we build trust before introducing additional products?

The outcome wasn't a collection of screens.

It was a shared blueprint for the future onboarding experience, prioritised around customer intent, technical feasibility and business value.

That alignment became the foundation for every design decision that followed.

Instead of waiting until the end to validate the work, research became part of delivery itself. We planned what needed to be proven, defined success before testing began, and used every round of research to shape the next iteration.

The goal wasn't to prove the design was right.

It was to discover where it was still wrong.

Working alongside Product, Research and Business, we built a structured validation programme that combined usability testing, journey analytics and customer interviews. Every finding fed directly back into the product before development continued.

Research wasn't a milestone.

It became part of how the product evolved.

I'll always value outcomes, but I've learned that numbers rarely tell the full story on their own. What mattered most on this project wasn't simply reducing friction or redesigning a journey — it was changing how the organisation understood the problem. Once we stopped assuming the interface was the cause, we could finally focus on the product, the systems and the decisions shaping the customer experience.

The result was a product built with intention rather than assumption. Existing customers were recognised instead of treated like strangers. Validation became smarter instead of heavier. Cross-functional teams aligned around a shared blueprint instead of isolated requirements. The interface became simpler because the thinking behind it became clearer. Every design decision was grounded in evidence, validated with customers and shaped alongside the people responsible for delivering the service.

Over the years I've learned that great products don't move forward because everyone stays in their lane. They move forward because people are willing to step into whatever the moment demands.

Sometimes that's leading discovery.

Sometimes it's facilitating executive workshops.

Sometimes it's sitting with engineers to understand technical constraints.

Sometimes it's analysing customer behaviour.

Sometimes it's refining the smallest interaction.

I enjoy all of it, because every part contributes to a better product.