Public sector · UX case study

Transforming the Household Support Grant Application into a Digital Service

Replacing a print, fill, scan and upload process with a GDS-compliant digital application for residents of the London Borough of Hounslow.

Client
London Borough of Hounslow
My role
UX Designer
Timeline
12 weeks, 3 days
Tools
Figma · FigJam · Miro
Laptop showing the purple Grant Application form
20 mins
to apply online, down from 30+ days with the paper process
0
printers or scanners needed to apply
7
usability test participants, new and existing applicants
500+
applications submitted online since launch
Overview

A paper process that shut out the residents who needed it most

S

Situation

Residents had to download a form, fill it in by hand, then scan and upload it. Many said it took too long, and many had no printer or scanner at all, so applications stalled.

T

Task

Turn the paper form into a fully digital application that follows Hounslow's design system and the GDS "one question per page" pattern, grouping only related questions such as address or bank details.

A

Action

Interviewed current and prospective applicants, ran workshops with the internal grants team, and mapped the end-to-end journey, which stakeholders signed off before design began.

R

Result

An end-to-end prototype plus confirmation emails for residents and the council. Post-launch feedback described the new service as much faster and easier to use than the paper form.

Design process

Five stages, tested at every step

01
Discover
Interviews · Survey · Workshop
02
Define
Persona · Journey map · POV
03
Ideate
How might we · User flow · Sketches
04
Validate
Wireframes · Prototype
05
Iterate
Usability testing
01 · Discover

Listening to the grants team and the people applying

I ran workshops with internal stakeholders using open questions to surface the service's goals, then interviewed current and prospective applicants to find where the paper process broke down.

Stakeholder workshop questions

Whoare the intended users?
Whatare their main responsibilities?
Whendo applications reach the team?
Whichchannels do residents use to apply?
Whydoes the project matter for the data we hold?
Howwill this contribute to the council's goals?

What residents told us

"It takes far too long."
Print, fill, scan and upload made a simple claim a multi-step chore.
No printer, no scanner, no application
The equipment needed to apply excluded many of the residents the grant was for.
Unclear what happens after submitting
Residents needed clearer information about what would happen next and when they could expect an update.
Interview themes: comprehension · information clarity · summary · calls to action · next steps
02 · Define

Who we were designing for

Susan William, persona
Susan William
43 · Senior HR officer, London Borough of Hounslow
London office Full time Internal user
Needs
A simple, informative process with timely updates on next steps and clear, straightforward information about the grant.
Frustrations
Incomplete or difficult-to-read scanned forms that require her to follow up with residents to clarify missing information.
Point of view

"Residents applying for financial support need a simple and accessible way to complete their application online, because the existing print, fill, scan and upload process creates unnecessary barriers and delays."

User journey map

The end-to-end resident journey across five stages, from awareness to outcome, reviewed and signed off by the Housing & Communities and Digital Transformation teams before design began.

Household Support Grant user journey map showing five stages (Aware and prepare, Start application, Complete application, Confirmation, Outcome) with user actions, pain points, emotions, opportunities, service improvements, key metrics and stakeholder sign-off
03 · Ideate

Mapping every route through the service

In Miro, I mapped how a resident moves from finding a grant to submitting, including the paths where their grant isn't available.

User flow diagram from start to submission, with decision points
Happy path
Resident picks their grant, completes the application and submits it.
Dead end
The resident can't find the grant they need, and the journey ends.
Alternative
Their grant isn't available, so they find a substitute and apply for that.

How might we…

…let residents apply without needing a printer or scanner?
…make the application process easier to understand and navigate from start to finish?
…give residents clear information about what happens after they submit their application?

Lo-fi sketches

Hand-drawn screens covering every section of the application, from sign-in to declaration, following the order of the original paper form.

Twelve lo-fi sketches of the grant application: sign in, task list, name, address, about you, household details, people living with you, why you need help, income, bank accounts, applying on behalf of someone else, and declaration
04 · Validate

One question per page

Wireframes followed the GDS pattern so each screen asked one thing, with "Save and return later" for residents who couldn't finish in one sitting.

Wireframe: What is your name? question page with title dropdown
Tablet on a desk showing the hand-drawn What is your name? screen with title dropdown, first, last and other name

Lo-fi wireframes

Greyscale wireframes of all twelve screens, used to test structure and flow before any visual styling.

Lo-fi wireframe: Sign in
01 Sign in
Lo-fi wireframe: Application task list
02 Application task list
Lo-fi wireframe: About you: your name
03 About you: your name
Lo-fi wireframe: About you: address
04 About you: address
Lo-fi wireframe: About you: date of birth & contact
05 About you: date of birth & contact
Lo-fi wireframe: Household: partner
06 Household: partner
Lo-fi wireframe: Household: who lives with you
07 Household: who lives with you
Lo-fi wireframe: Why you need help
08 Why you need help
Lo-fi wireframe: Your income
09 Your income
Lo-fi wireframe: Bank accounts, savings & investments
10 Bank accounts, savings & investments
Lo-fi wireframe: Applying on behalf of someone else
11 Applying on behalf of someone else
Lo-fi wireframe: Declaration
12 Declaration
Design system

The building blocks behind every screen

One typeface, a purple-led palette and a small set of reusable components, taken directly from the hi-fi mock-ups and aligned with Hounslow's brand.

Typography

Inter throughout: a clear, highly legible sans-serif that works at small sizes on form-heavy screens.

Aa
Inter
Regular 400 · Semibold 600 · Bold 700
ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789 £ & ? !
Page heading
32px / 40px · Semibold 600
What is your name?
Section heading
24px / 32px · Semibold 600
Your Resident Address
Task title
19px / 28px · Semibold 600 · Purple
Application For Household Support Grant
Label / body
16px / 24px · Regular 400
Do you have a partner?
Button
16px / 24px · Bold 700
Continue
Hint / link
13px / 20px · Regular 400 · Underlined
Forgotten your password?
Status tag
11px / 16px · Bold 700 · Uppercase
Not started

Colour palette

Sampled from the hi-fi mock-ups, with contrast ratios against the text colour used on each.

Aa
Hounslow Purple
#652F6C
Header, primary buttons, headings, links
White text 9.7:1 · AA
Aa
Lilac
#B297B5
Action bar, Yes/No toggles
Black text 8.0:1 · AA
Aa
Pale Lilac
#D1C1D3
Filled inputs (savings, shares)
Black text 12.3:1 · AA
Aa
Mist
#E0D5E2
Declaration fields
Black text 14.8:1 · AA
Aa
Ink
#000000
Body text, input borders, table rules
On white 21:1 · AAA
Aa
Mid Grey
#858585
Status tag border, dividers
Text on white 3.7:1 · decorative only
Aa
White
#FFFFFF
Page background, inputs
Base surface
Lo-fi wireframe greys
Header
#454545
Action bar
#9F9F9F
Filled input
#C6C6C6
Field
#D8D8D8
Text
#000000
Surface
#FFFFFF

Icons

A deliberately small set, so every icon has one clear meaning.

London Borough of Hounslow crest
Council crest
Logo in the header of every screen
Chevron left
Back link
Chevron down
Expand a task-list section
Chevron up
Open dropdown toggle
Chevron right
Breadcrumb separator
Checkbox
Consent and “I’m not a robot”

Components

Reusable pieces that make up all twelve screens.

Header bar
London Borough Of Hounslow DashboardHelpProfilePrivacy StatementSign Out
Buttons & links
Continue Log in Submit
Save And Return Later Forgotten your password?
Navigation
Back
DashboardHousehold Details
Text input
First Name
Tony
Shares or investments
Dropdown (open)
Mr
Master
Mrs
Miss
Ms
Yes / No toggle
No Yes
NINO segmented input
Status tag & task row
Household Details NOT STARTED
I'm not a robot
Data table
Assistance withWhy it is needed
Food
Cooker
Action bar (sticky footer)
Continue Save And Return Later
Final designs

Built on Hounslow's design system

Hi-fi mock-ups

The same twelve screens in Hounslow purple, using the type, colour and components above.

Hi-fi mock-up: Sign in
01 Sign in
Hi-fi mock-up: Application task list
02 Application task list
Hi-fi mock-up: About you: your name
03 About you: your name
Hi-fi mock-up: About you: address
04 About you: address
Hi-fi mock-up: About you: date of birth & contact
05 About you: date of birth & contact
Hi-fi mock-up: Household: partner
06 Household: partner
Hi-fi mock-up: Household: who lives with you
07 Household: who lives with you
Hi-fi mock-up: Why you need help
08 Why you need help
Hi-fi mock-up: Your income
09 Your income
Hi-fi mock-up: Bank accounts, savings & investments
10 Bank accounts, savings & investments
Hi-fi mock-up: Applying on behalf of someone else
11 Applying on behalf of someone else
Hi-fi mock-up: Declaration
12 Declaration

In context

Desktop sign-in screen for an LBH account
Sign in. A single LBH account so residents can save and return.
Task list showing each application section and its status
Task list. Each section shows its status, so progress is always visible.
Confirmation email to the resident with application reference and what happens next
Resident email. A reference number and clear next steps, so residents know what to expect.
Notification email to the council grants team with application reference, resident and status
Council email. Alerts the grants team with the reference and status, ready for review.
05 · Iterate

Testing with seven applicants

Participants were prospective applicants and residents who had used the paper form and knew its drawbacks. We tested against five criteria, and each finding shaped a specific design change.

01
Comprehension
Test finding
Residents were unsure about some of the terminology and what they were being asked to provide.
Design change
Simplified wording and used clearer, more direct questions.
02
Information clarity
Test finding
Some information was difficult to scan or understand quickly.
Design change
Reworked content hierarchy and clarified supporting information.
03
Short and concise
Test finding
Some screens contained more information than residents needed at that point.
Design change
Reduced unnecessary copy and kept each step focused on one task.
04
Calls to action
Test finding
Residents needed clearer direction on how to start or continue.
Design change
Strengthened button labels and made the primary action more obvious.
05
Next steps
Test finding
Residents wanted reassurance about what happened after submission.
Design change
Added clearer confirmation messaging and email notifications explaining what happens next.
Reflection

Looking back on the project

What I learned

Research earns its value when it moves beyond data collection and turns evidence into clear, actionable decisions.
Bringing stakeholders into workshops early made sign-off of the journey map straightforward.

One thing I'd do differently

I would bring analytics into the design process earlier.

While interviews and usability testing helped me understand residents' needs, having earlier access to application analytics would have helped me identify where residents were dropping out and prioritise improvements with greater confidence. In the next iteration, I would combine qualitative research with behavioural data from the beginning.

Outcome

Faster, simpler, and open to everyone

After launch, residents reported that applying online was significantly more efficient and far easier than the paper form. Further testing and analytics surfaced more pain points to address in the next iteration.