Lloyds Bank
A calm policy page and six-step claim flow, with a coded live demo.

Role
UX/UI Designer
Duration
Time-boxed design challenge
Services
Mobile banking app
Category
Fintech
Overview
A page for the moments nobody is calm
People open motor insurance after a bump, or with a renewal looming. The page has to reassure them, point at the next step, and keep a lot of detail digestible, inside Lloyds' existing visual language.
The Impact
This was a time-boxed design challenge. These are the things the design is built to change, not figures from a customer test.
One
primary action
Make a claim is the only loud button
Six
claim steps
One simple question at a time
In-app
visual language
Monochrome, green accents, rounded cards
Problem
Insurance screens are rarely visited for fun
The experience needed to reassure customers, make urgent actions impossible to miss, keep complex information readable, and feel like it belonged in the Lloyds app.

01
Stress on arrival
People are not browsing. They want to know if they are ok, and what to do next.
02
Too many equal actions
A policy page can bury Make a claim among documents, updates and help.
03
Dense cover detail
Cover, excess, limits and support are necessary, and easy to make unreadable.
Research
Three questions a stressed customer is asking
I structured the page around the questions someone is silently asking, then designed inside Lloyds' brand so it would feel familiar from the first tap.
Situation
Vehicle, status, renewal, cover type and no-claims discount.
Action
One primary action, and quieter ones that stay on the page.
Cover
Tabs for Cover, Excess and Limits, and Support.
What we learned
The page only works if someone can answer those three questions without hunting. Everything else is secondary.
It felt like it already belonged in the app. Calm, clear and on brand.
Design challenge reviewer
Lloyds Bank
Organizing recurring patterns and behaviors
The structure that held was Summary, Actions, Details, Support. It is not specific to motor insurance, which is a hypothesis, not a result.

Key insights
Make a claim has to be the only primary action.
Secondary tasks can live in modals, so people do not lose the policy page.
A long claim does not belong in a modal. It needs a stepper and a review.
The same cards, tabs, accordions and modals could extend to other Lloyds products.
Understanding the user journey
Four moments, from landing after a bump to starting a claim, and what each one has to do.
01
Land after a bump
Friction
The page has to be calm before it is complete.
Opportunity
Open with a summary card: vehicle, status, renewal, cover, no-claims.
Impact
The customer can see their situation without reading the whole policy.
02
Find Make a claim
Friction
Urgent and ordinary actions were at risk of looking the same.
Opportunity
One loud button. Documents, updates and help sit one level down.
Impact
The next step is obvious.
03
Check what is covered
Friction
Cover, excess and limits are a lot of detail.
Opportunity
Tabs and accordions, so the detail stays available and the page stays light.
Impact
People can say what they are covered for.
04
Start a claim
Friction
A claim is too long for a modal.
Opportunity
Six steps, one question each, then a review and a confirmation.
Impact
The flow holds your hand without leaving the app's language.
Ideation
One loud button, several quiet ones
I tried the page as a set of decisions: what is primary, what can stay in a modal, and what needs a full flow.

Policy summary, secondary actions in modals, and a six-step claim with a review.
01
Summary, actions, details, support
A structure aimed at situation, next step and cover, using cards, tabs and accordions.
02
Modals for short tasks
Documents, updates and help open in place, so nobody loses the policy page. The trade-off is less room, which suits short tasks only.
03
A six-step claim
One simple question at a time, a stepper, a review screen and a confirmation.
Testing interaction flows early
With more time I would test the claim with customers, especially the review step, and check the page with assistive technology. I would measure time to find Make a claim, whether people finish without help, and whether they can say what they are covered for.

Designs
Lloyds' language, on purpose
Monochrome base, bright green accents and rounded cards, so the page feels trustworthy and familiar. I also built a coded live demo.
The policy page: a summary card, one primary action, and cover detail in tabs.
The six-step claim, one question at a time, with a review and a confirmation.
A coded live demo, using the same components as the design.
Lessons
Calm, clear, and already in the app
The constraint was the brand. The page had to feel like Lloyds, and it had to be kind to someone who is not calm.
Key outcomes
A readable policy page
Situation, action and cover, in that order.
A claim people can finish
Six steps, one question each, plus a review.
A reusable pattern
Summary, actions, details, support, as a hypothesis for other products.
A coded demo
The design taken into code, still inside the visual language.

