Westpac NZ · 2024–2025 · 7 min read
Making deposit regulation clear for customers and bankers
A new law meant Westpac had to tell customers what happens to their money if a bank fails. I led the UX so customers got clear answers, and bankers could explain them with confidence.

- My part
I led the UX from end to end, across customer and banker experiences: the website, the app and the tools bankers use
- Key decision
We tested the bank’s worries with real customers, instead of guessing how people would react
- Result
The web page and banker content went live by July 2025. In concept testing, the designs scored around 85 out of 100 on the System Usability Scale (SUS)
01 · Overview
A new rule, and a lot of worried people
Imagine your bank gets in touch to explain what happens to your money if the bank fails. Even when the news is reassuring, it’s an unsettling message to read.
That was the job. In 2023 New Zealand passed the Deposit Takers Act. It required banks to put in place the Depositor Compensation Scheme (DCS), which protects eligible deposits up to $100,000 per person, per bank. Banks had to tell customers about it. On paper, that’s a compliance task. In practice, the message arrives for people who might already be anxious about money. Westpac needed to meet the Reserve Bank of New Zealand’s (RBNZ) requirements without alarming anyone.
02 · My role
What I owned, and who I worked with
I led the UX from end to end, across the website, the app and the tools bankers use. Each person on the team owned their own part, and we worked closely with product owners, developers and compliance.
- The researcher led 30 in-depth interviews. I supported and listened in.
- The content designer wrote the copy, and helped with note-taking and some testing sessions.
- The service designer led communications and the overall plan and timelines, and led the later co-design workshops.
- I co-led a 30-person workshop to pull out customer needs and emotions.
- I owned the journey framework, the hypotheses, the prototypes for customers and bankers, the testing, and how the findings shaped the programme.
- Research30 customer interviews and a 2,200-person survey showed what customers needed
- MeFrom those needs, I found the touchpoints, six journeys and the hypotheses to test
- BAs, with meI shared and explained the needs. The business analysts turned them into requirements
- Me, with the teamIdeating and designing solutions for each journey, for customers and for staff
- MeTesting the journeys, content and hypotheses with customers and staff
- TeamAll of these studies led to the final recommendations
03 · The problem
Same rule, very different situations
- 30customer interviews, aged 18 to 82, with RBNZ observers
- 2,200survey responses from personal and business customers
- 6customer journeys the scheme would affect
- 26people in testing: 9 customers and 17 staff
We had three things to solve. The rules were complex, and customers needed simple answers about who was covered. Customers ranged from people with small balances to clients with more than $100,000, each with different worries. And bankers needed the right information to answer questions confidently.
Using Westpac’s experience framework, I identified six journeys the scheme would affect. They ran from low-balance customers wanting reassurance, to people from other banks looking for reliable information during a crisis. These became the base for every decision that followed.
Six situations
- Existing customer, under $100k, looking for information
- Existing customer, over $100k (a complex customer)
- Dormant customer reactivating an account to be prepared
- New customer opening an account
- Westpac customer during a crisis
- Another bank's customer during a crisis
One source
Plain-language content about the scheme
Who's eligible, what's covered, how it's funded, what happens in a crisis.
Two audiences
Customers
Website, app and email
Bankers
Knowledge base, so they can explain it the same way
Mapped across three kinds of touchpoint: digital (logged out), digital (logged in), and branch, contact centre and relationship managers.
For each journey I mapped what customers needed at each step, then added rows for risk, emotion and how information was delivered. The programme kept using the map to stay aligned, long after the first playback.





04 · Key decisions
Choices that kept it calm and clear
Challenge
Many people on the programme hadn’t worked with UX before, and the default was compliance first.
Decision
Bring them into the process early. I shared the artefacts and showed why the way a customer reads a sentence matters as much as whether it’s legally right.
The service designer led a series of co-design workshops, which I supported and co-facilitated. One was a Crazy 8s session, where people sketch eight quick ideas in eight minutes. It produced more than 200 ideas. Not all were practical, but they raised good questions, like how to show coverage visually and which phrases made people worry. Then we weighed cost and priority in feasibility sessions with several departments.


Challenge
If customers and bankers got different answers, trust would drop fast.
Decision
Design one set of plain-language content for both: a DCS section on the website and app for customers, and a rewritten knowledge base for bankers.

The bank had real worries about how customers would react. Would they panic about their money? Would they call the bank or visit a branch? Would they split their savings across other banks? We turned these worries into six hypotheses and tested them with customers. These are the ones that shaped the final design.
What we thought
Telling customers directly would build trust, not worry.
What we learnt
Most had already heard about the scheme on TikTok, Instagram, the news or podcasts. Hearing it from the bank by email or in the app felt open and caring. Putting it only on the website felt like “telling you by stealth”.
What we thought
An email and a web page would give customers the information without leading to more calls.
What we learnt
The email and website answered people’s questions. They said they wouldn’t call or visit, even those who usually prefer to call.
One less thing to worry about now. I won’t call the bank.
What we thought
Plain-English explanations would help people understand who and what is covered.
What we learnt
Customers understood eligibility easily, and corrected their own mistakes as they read. Some were surprised KiwiSaver wasn’t covered, so we recommended a clear line explaining why.
What we thought
A web page on its own would reach people.
What we learnt
Customers liked the page, but they only visit the website to open an account or change a home loan. They needed an email or an app message to send them there.
After reading, most customers said they would do nothing. Some would google it or talk to friends, and a few would adjust how much they keep with each bank.
Based on this, we recommended contacting customers by email and an in-app message about a month before the scheme started, with one public web page as the single source of truth for customers and bankers.
05 · Outcome
What we delivered
I led the testing, with the content designer supporting. With 9 customers, we tested whether the content was easy to find and understand. With 17 staff, we tested whether they could find it and explain it accurately.

- For customers: a dedicated web page with plain-language information about who’s eligible and which products are covered.
- For bankers: a rewritten knowledge base, focused on what the change meant and how to explain it.
- For the bank: tested answers to the programme’s key questions, to help it plan.
The web page and banker content went live by July 2025.




06 · Pat on the back
What the team said
Your ability to navigate tight deadlines, manage shifting priorities, and facilitate key conversations between the key stakeholders was truly invaluable.
To Shine, who made sure our journeys were not only mapped but looked so good even the design forums couldn’t find fault … You literally designed our way out of trouble.
Shine is a brilliant UX designer with the ability to unpack and define complex user flows across an enterprise.
07 · Reflection
What I took from it
Compliance and empathy can sit together, but only if design is in the room early, while the programme is still deciding what to say.
Testing our hypotheses with real people, rather than assuming, gave the programme clear answers. Clear, calm information gave customers what they needed.
It also changed how I think about vulnerability. People can feel exposed for many reasons, from money worries to not trusting big institutions. Customers valued clear facts and choice over being told what to do.