Research rewrote the flow.
Not just the screens.

The hand-over, not the hand-holding. A first-in-market digital joint loan application, shaped by research that showed us what legal couldn't picture: two applicants rarely sit at the same computer at the same time.

ProjectNatWest, Account Opening RoleUX Designer (lead designer on the project) ContributionLead Designer on Apply for Loans. Designed the joint loans journey from scratch, working closely with legal and a UX researcher across three rounds of testing.

At a glance

No UK bank had a fully digital joint loan application. Every existing journey required a branch visit, a posted form, or both.

I designed a handover flow: Applicant 1 does around 90% of the work, signs, and passes the device. Applicant 2 reviews a summary, gets their version of the legal documents, and signs. It launched and is live.

The move that made it work was designing around what research kept showing: joint applicants almost never sit at the same computer at the same time.

1st fully digital joint loan
at a UK bank
3 rounds of research
with real couples
90% of the application completed
by Applicant 1

Context

In 2022, applying for a joint loan at most UK banks meant going into a branch with your partner, or posting signed documents. Single-applicant loans had gone digital long ago, but joint loans hadn't. The regulatory weight was heavier, the edge cases messier, and the legal teams cautious.

I was part of NatWest's account opening team (a retail bank with 20 million customers in the UK) and took the brief to design a fully digital journey, constrained to two existing NatWest account holders. Non-customers were out of scope.

62%

of consumers want to self-serve digitally when applying for loans

YouGov

The problem

The obvious design problem was how to let two people sign one application online without a branch visit. The less obvious one was this: a branch visit is a trust mechanism. A colleague verifies identity, witnesses consent, handles the moment where two people commit to something legally binding together. Replicating that online, without creating friction that broke the journey, was the real design challenge. Online, you can't just ask the second person to confirm it's them (fraud risk is too high), so they have to log in. That constraint shaped a lot of the design decisions that followed.

The NatWest 'Verify who you are' screen, Step 1 of 2, asking for a customer number, described as 'your date of birth followed by your unique identification number'. This authentication step is required for each applicant independently.
Each applicant had to verify independently. The authentication requirement was non-negotiable. It drove the entire hand-over structure.

The harder problem, which emerged during research, was that users and legal disagreed about what "secure enough" and "good enough" looked like, and each round shifted the balance.

01

Users were happy.
Legal wasn't.

Users found the journey simple and unremarkable (the compliment I was hoping for). Legal, reviewing it after the round, decided it wasn't secure enough. They'd verbally approved the direction, then changed their mind once they saw it tested.

Outcome: back to the drawing board with new legal requirements to absorb.

02

Legal was happy.
Users weren't.

With legal's new requirements baked in, users found it exhausting. Too much switching between applicants. Both couldn't sign at the first stage, which confused people who expected to "sign together like in branch."

Outcome: a clear signal that the multi-handover structure had to go entirely.

03

Both were happy.
Journey launched.

After redesigning around the single hand-over pattern, users described the journey as quick and painless. Legal stayed comfortable. The flow went into build and launched live.

Outcome: first fully digital joint loan application at a UK bank.

Quick and painless.

Round 3 participant

So glad I don't have to go into a branch.

Round 3 participant

My partner doesn't have much free time so this means I can do it all and they can just sign it.

Round 3 participant, the one I was hoping for
Twenty-one Round 2 prototype screens colour-coded by applicant: blue 'Together' screens, green 'Person 1' screens, and yellow 'Person 2' screens, arranged in a grid that makes visible the frequency of back-and-forth handovers that users found exhausting.
The Round 2 flow: multiple handovers between Person 1, Person 2, and joint steps. Legally tighter, but users found it exhausting to navigate.

3 colours = 3 applicant states. Blue: together. Green: Person 1. Yellow: Person 2.

Every colour switch is a handover. Every handover is a login.

Four participant quotes from Round 2 testing shown alongside screen thumbnails: 'Oh that's a bit confusing, isn't it'; 'Ah, so you have to log in now and do your bit'; 'Why can that not be on the first one to say Person 1 and Person 2 have signed it'; and 'Look, this time your box has appeared'.
Round 2 feedback: the missing box, the confusion about when to log in, the expectation of signing together. Each quote pointed to the same underlying problem.
A message sketching out the post-research direction. Round 2 is described as having too many handovers, with legal constraints listed: both applicants must see T&Cs, confirm details, and be logged in. The proposed solution shows Person 1 completing all details and signing, then Person 2 logging in to review and sign. A note at the bottom reads: it effectively creates just one handover so users will hopefully much prefer it.
Post-research thinking: Round 2's problem stated plainly, legal constraints mapped, one-handover solution proposed.

One handover instead of many. The reasoning written before any wireframe.

My approach

Five illustrated couple personas used across the three research rounds. Each pair of circular avatar portraits represents a different dynamic: varying financial engagement, living situations, and availability.
The five couples used across research rounds. Each brought different dynamics: one partner more financially engaged, different living situations, different amounts of free time.

Let research be the argument

Research ran fully remote during COVID, which turned out to be the most useful constraint of the project. Instead of hearing about users' home lives in abstract, we watched them. Kids screaming in the background. One applicant in the kitchen, the other in another room, called over only when strictly necessary. Half-finished cups of tea and laptops balanced on knees.

Legal, understandably, had been imagining the default scenario: two calm adults sitting side by side at a clean desk, both fully present, both equally engaged. That picture held up badly against what we were seeing every session.

I started bringing this directly into the legal conversations. Not as a complaint, but as a design input. If the real situation is "one person driving, the other available intermittently," the journey needs to work for that. It shifted the framing from "how do we force both users to do everything together" to "how do we let one lead while keeping the second legally protected."

Research also surfaced something consistent about device. When asked where they'd apply for a loan, users were clear: it was a "proper task," the kind of thing you'd sit down at a laptop to do properly. Nobody said they'd reach for their phone. That shaped a deliberate choice to optimise the journey for desktop and laptop rather than designing to accommodate every device equally.

If the real situation is one person driving and the other available intermittently, the journey needs to work for that.

Design around the hand-over, not around the togetherness

Every hand-over between applicants meant a log-in. So the fewer hand-overs, the less friction. The single-hand-over model wasn't just a behavioural insight. It was also the minimum-friction shape the technical constraint allowed.

Instead of asking both applicants to move through the form in parallel, I let the design match how it actually happens.

  • Applicant 1 completes around 90% of the work. Name-tagged questions make it clear whose data is being entered at any moment, which came directly from a Round 1 insight.
  • Applicant 1 signs their portion and hands the device over. Applicant 2 logs in.
  • Applicant 2 sees a summary of what's been entered, their own version of the legal documents, confirms and signs.
  • A joint confirmation page closes the loop.

To keep both applicants oriented through the hand-over, I worked with the wider account opening UX team in an ideation workshop and we landed on a "stagegate" component: a visual progress marker that showed each applicant where they were and what was still to come. Small thing, but it was what stopped Applicant 2 feeling parachuted in.

The 'What to expect on your joint loan journey' handover screen. Left panel in purple: Amanda's four steps: provide details for both applicants, confirm quote, set up payments, sign and submit. Right panel in red: Joe's two steps: confirm details, sign and submit.
The hand-over pattern in plain language: Applicant 1 does the heavy lifting, Applicant 2 reviews and signs. Fewer hand-overs, less friction.
The stagegate component showing two panels side by side. Left in dark purple: 'Sally's bit now' listing three steps: fill out both your info, set up your payments, Sally's legal bit. Right in dark red: 'It'll be Laura's turn later' listing two steps: Laura logs in to check everything, Laura's legal bit.
The stagegate component: each applicant could see exactly what their role was, and what the other person still needed to do. Round 3 prototype.

Applicant 2 sees their role before they’ve even logged in. No surprises at hand-over.

Get it in writing

The biggest process lesson from this project was about legal sign-off, not design. A verbal "we're happy with this direction" meant less than I'd assumed. After Round 1, I started documenting every legal decision in writing, getting it confirmed in email, and keeping a running log of what had been agreed and when. It slowed the early conversations and saved weeks of rework later.

A verbal 'we're happy with this direction' meant less than I'd assumed. Document every decision. Get it confirmed in writing.

Designed to work for everyone

The stagegate component was the most consequential accessibility decision. It would have been easy to build as a purely visual progress marker: position in the flow, colour, layout. Instead it used explicit text labels alongside the visuals, so both applicants could stay oriented regardless of how they were accessing the page. The name-tagged questions ("Sally's details," "Laura's details") had the same logic: clear context that worked for screen reader users and felt natural for sighted ones. When accessibility and usability point in the same direction, you've made the right call.

The Round 3 'Both your outgoings' form, headed 'Sally and Laura's outgoings', asking for monthly rent or mortgage, number of dependants, and shared costs. A 'Get our quote' button sits at the bottom, with 'Sally's turn' shown in the footer bar to keep both applicants oriented.
Round 3 prototype: Applicant 1 ("Sally") has completed the shared outgoings step. The footer bar keeps both applicants oriented throughout.
The loan confirmation page with a teal header reading 'Your money's on its way' and a subline 'Sally and Laura, the loan's yours' in warm pink. Below, a summary card shows the loan amount, account details, and repayment dates alongside a colourful isometric illustration of a car, a deliberate celebratory moment at the end of the journey.
The confirmation screen: the car illustration and warm copy mark the completion moment. Both applicants named throughout.

The confirmation was a considered moment, not just a summary screen. The copy "Sally and Laura, the loan's yours" names both applicants and uses a warm, personal register rather than a transactional one. The car illustration was a deliberate choice to mark completion as an event worth acknowledging. In banking the space for delight is narrow; you can't be playful with someone's finances. But the end of a completed journey is one of the few moments where it's entirely appropriate, and it was worth using well.

Outcomes

The journey launched as the first fully digital joint loan application at a UK bank. The hand-over structure remains live today under NatWest's current branding. Business priorities shifted the go-live timeline after the design completed, and I'd moved on by then, so I don't have post-launch performance data to share.

The significance wasn't primarily in the product metrics anyway. Journeys like this one were part of how NatWest was actively repositioning itself, moving away from a bank where important life moments required a branch visit, towards one built around how people, families and businesses actually live. Being first to market on digital joint loans wasn't just a product milestone. It was a signal about the kind of bank NatWest was becoming, and this project was a tangible part of making that case.

Round 3 testing was the clearest positive signal of the project itself: applicants described it as "quick and painless" and specifically valued being able to let one person lead.

Reflection

Designing for real life, instead of the idealised version legal had in mind, was what turned a stuck project into something that felt warm and easy.

01

Real behaviour beats assumed behaviourThe hand-over pattern only worked because research showed us what legal couldn't picture: two people rarely sit at the same computer at the same time.

02

Research is your argument with stakeholdersBringing session clips into legal conversations shifted the framing from "how do we force both users together" to "how do we let one lead while keeping the second protected."

03

Get it in writingA verbal "we're happy with this direction" meant less than assumed. Documenting every legal decision, confirmed in email, saved weeks of rework.

A note on confidentiality: Screens and interaction structure shown here are simplified representations. Specific product details have been generalised.

← All work
Next up The savings backlog