About
The British Heart Foundation is the UK's largest independent funder of research into heart and circulatory conditions. Heart Matters is its free membership for people living with those conditions: a print magazine, an email newsletter and an account area. BHF was introducing customised newsletters, which made sign-up the moment where personalisation either worked or failed.
Scope
Evaluate the existing Heart Matters sign-up journey end to end, then redesign it around the new personalisation requirement — landing page, sign-up form, confirmation and the My Account dashboard where members manage what they receive — ready to be built in Sitecore.
The problem
Multiple entry points
Sign-up could begin in several places on the site, and each one led to a different journey.
An inconsistent process
Personalised newsletters meant existing members needed a way to change their preferences — the old journey had no answer for them except unsubscribing and starting again.
Nothing after sign-up
The moment members were most willing to engage was spent asking them for money, with no way to skip it and no route back into the site.
What we wanted to achieve
- One clear sign-up journey, whichever entry point a member arrives from.
- Personalisation members can see and change — at sign-up, and afterwards in their account.
- Ask only for what is needed: no postal address unless a member wants the printed magazine.
- A post-sign-up moment that keeps members engaged with BHF instead of pushing them away.
My role
- Research
- Facilitated the stakeholder workshop with the Health Content team, mapped the existing journeys, ran the heuristic and competitor analysis, and analysed Mouseflow session recordings and scroll maps alongside Google Analytics funnel data.
- Synthesis
- Facilitated the affinity mapping session with the project team and set the design priorities that came out of it.
- Design
- Designed and prototyped the new journeys. I worked with the Content Designer on the landing page and took full ownership of the sign-up form and the My Account dashboard.
- Validation
- Ran two rounds of unmoderated usability testing in Useberry and made the design decisions that followed from them.
- Delivery
- Annotated the wireframes for development, added the new components to the BHF design system, and supported the developers through build and QA in Sitecore.
The approach: four phases, one journey
The solution was a single sign-up journey built around what each member actually wants to receive, with the donation ask made optional, and an account dashboard that shows those choices back to members and lets them change them. Getting there ran through four phases, each feeding the next.
- 01 · Discover
Discover
Stakeholder workshop, current journey mapping, heuristic and competitor analysis, heatmap and GA analysis.
- 02 · Define
Define
Affinity mapping, new user journeys, problem areas and UX recommendations.
- 03 · Design & Validate
Design & validate
Iterative wireframes, two high-fidelity prototypes, two rounds of usability testing.
- 04 · Deliver
Deliver
Final designs and journeys, new design system components, annotated handover and QA.
DiscoverStakeholder workshop
With the Content Designer, I ran a workshop with the Health Content team to establish what the team believed members needed, how the existing journey would be affected by customised newsletters, where the team was already hitting problems, and what other opportunities they could see.

What the workshop settled
Choices members own
Members must be able to choose options tailored to their needs — and change them later, without unsubscribing.
One answer per question
Each personalisation question allows a single answer: a constraint the form design had to make feel natural.
Choices made visible
Content relevant to those choices should appear in the account dashboard, and every part of the journey on the BHF website was in scope.
DiscoverMapping the existing journeys
I mapped both live journeys — a new sign-up, and an existing member changing preferences — screen by screen, and marked every point where the design was working against the user.
Quick wins
- Remove the healthcare professional question from the sign-up form.
- Rethink the calls to action on the landing page and the My Account dashboard.
- Only ask for address details if the member opts in to the printed magazine.
- Redesign the confirmation page, which forced members into a donation journey or out of the browser.
DiscoverHeuristic and competitor analysis
I compared the journey against five charities: Macmillan, WWF, the National Autistic Society, Barnardo's and Age UK. Most large charities have no onboarding process at all, and two of the five offered only a one-page form asking for an email address and basic details. That mattered: BHF was asking members for considerably more than its peers, and needed to justify the ask.

What it pointed to
- State the reasons for subscribing, and set expectations of what membership involves.
- Show samples of what subscribers actually receive, and make testimonials more prominent.
- Introduce a personalised dashboard, and make the personalisation questions interactive rather than administrative.
- A donation must not be required to complete sign-up.
DiscoverBehavioural data
Google Analytics gave the shape of the problem and Mouseflow explained it. I reviewed session recordings, scroll maps and click maps against the funnel to find where members struggled, not just where they left.



DefineAffinity mapping
I facilitated an affinity mapping session with the project team to bring the findings from every research method into one picture. How often an issue recurred across methods decided its priority — which kept prioritisation out of the realm of opinion. Three areas separated out clearly: the landing page's information flow, the sign-up form's pain points, and theaccessibility and usability of the account dashboard.
DefineNew user journeys
I mapped every route a member could take, including the one the old journey had no answer for: an existing member changing what they receive without unsubscribing.

DefineProblem areas and recommendations
Every recommendation was assigned to one of three areas, each with a defined job in the journey:
Landing page
- Give members a reason to join: why join, and what they get.
- Elevate BHF's expertise — introduce an expert and what they contribute.
- Lead with nutrition and recipes, which CRO work showed drove sign-ups.
- Make testimonials prominent, and keep the phone option visible.
Sign-up form
- Reinforce the reasons to subscribe inside the form.
- Introduce the personalisation questions in an interactive, friendly way.
- No address details unless the member opts in to the printed magazine.
- Make the donation request at the end subtle, and optional.
My Account dashboard
- Make current personalisation choices easy to identify.
- Allow them to be updated in as few steps as possible.
- Give Heart Matters its own section, with space for related content.
I collaborated with the Content Designer on the landing page changes, and took full ownership of the designs for the sign-up form and the My Account dashboard.
Design & validateWireframes
I worked iteratively, putting each round in front of the Product Owner, Business Analyst and Content Designer, refining, and taking the strongest options forward. The Health Content team were looped in at each stage, with the wireframes used to explain the reasoning behind each decision so stakeholders could respond to the argument rather than the aesthetics.
Design & validatePrototyping
I built high-fidelity prototypes using interactive components with variables to simulate the radio button behaviour, so the interaction could be tested rather than described. Two complete, functional prototypes were produced with different designs — to be compared against each other in testing, and to carry the interaction detail into developer handover.

Design & validateUsability testing
I ran two rounds of unmoderated testing in Useberry. The first focused on the landing page: how members read it, and whether they understood what Heart Matters actually was from the content provided. The second covered the sign-up journey and the account dashboard, using tasks and open questions to compare the two designs.
What testing decided
Personalisation was only implied on the landing page, through the single word “tailored”.
→ state it outright, with the newsletter and magazine frequency
Design B — bullet points with descriptions — helped members make an informed choice.
→ Design B taken forward, with a clearer split between health goals and recipes
Selected preference cards on the dashboard read as clickable.
→ restyle the cards, and rewrite the copy to say what can be changed
Testing also led to removing the excess calls to action on the landing page, adding samples of past newsletters and magazines, and reducing the suggested donation amounts.
DeliverFinal designs and handover
I produced the final designs from the testing results, updated the journey maps with the detail required for build, and added the new components introduced by this work to the BHF design system so the rest of the site could use them.
Final account dashboard, desktop and mobile. The member's choices are stated back to them in their own words, with related content beneath — personalisation made visible rather than promised.

Each wireframe was annotated for development with the interaction and content detail the build needed, and the prototypes carried the behaviour static frames could not. I stayed with the project through build and QA in Sitecore, answering design queries and checking what shipped against what was specified.
Outcomes & reflection
The work left BHF with one sign-up system in place of several disconnected journeys: a landing page that states why to join, a form that only asks for what each member needs, a route for existing members to change their preferences without unsubscribing, and an account dashboard that shows those choices back to them. It also left a clear baseline to measure against — 13% end-to-end completion and 27% progression from landing page to form — to be tracked after launch through the same session recordings, heatmaps and Google Analytics funnel used in discovery.
What I'd do differently: testing showed that members' reasoning around health goals versus recipe preferences was the least well understood part of the journey, and we recommended a further round of testing on it. Next time I'd build that round into the plan before handover, rather than leave it as a follow-up.
What colleagues say
“I worked alongside George developing new conversion funnels and optimising existing high value pages across the BHF website. George is always super engaged, full of ideas and recommendations, absolutely focused on the user's needs, backed up by user testing and insight.”







