work / 03 / leading-designSantander · 2025
Making a design team's work visible
No shared view of work, unclear ownership, requests arriving as "make this screen". A stakeholder map, a workflow built for design, and an AI-assisted brief changed how the team takes on work.
- Decision
- Treat how the team works as a design problem
- Role
- Lead UX Designer, Onboarding; line manager
- Team
- Design, Product, Engineering, Compliance, Marketing
- Scope
- Current accounts, credit cards, the public website and the app
- Timeline
- From September 2025, ongoing
- 30+
- colleagues trained in Figma, prototyping, motion and AI tools
- AI
- Champion for Santander UK
- 2024
- award for financial inclusion, Global Retail Banking Innovation Awards
Onboarding squad
Design board
Figures are rounded. Exact figures are shared privately on request.
01 · The problem
Nobody could see what the design team was working on, including the design team.
In September 2025 I was promoted to lead design on the Onboarding team: the journeys that bring customers in across current accounts, credit cards, the public website and the app.
Before I started I ran a short discovery of my own. There was no shared view of the work in flight or of its priority. Ownership was unclear, which slowed everything that needed more than one person. Designers worked in silos, and new requests arrived ad hoc, often as “make this screen”, so design spent its time reacting.
02 · The constraint
The work could not stop while the way of working was fixed.
Onboarding is regulated, busy and shared with Product, Engineering, Compliance and Marketing. Any change had to make sense to all of them, fit the tools they already used, and help from the first week rather than after a reorganisation.
I was also new to the team. Whatever I introduced had to earn its place, or it would quietly be ignored.
03 · The call I made
I treated the team's way of working as the thing to design.
The same habits I would bring to a customer journey: find out who is involved, make the work visible, and improve what goes in, so that what comes out improves with it.
What I prototyped
An AI-assisted request form that walks the person asking through the problem, the goal and the information design will need, so a request arrives as a brief instead of a screen.
- Stakeholder mapping. A workshop to name every partner across Product, Engineering, Compliance and Marketing, and how each prefers to work with design. It cut the time lost to loops of who-should-I-ask.
- A workflow built for design. A design board in JIRA, training for the team, and a JIRA review folded into the weekly design sync, so the board stayed true.
- Better requests. Through the Ways of Working group I helped define what a story needs before design starts: the user's problem, the goal, and what the designer needs to know.
Depth: What the board and briefs include
- Naming conventions, so work can be found across Figma, JIRA and Confluence.
- A design brief practice, so every piece of work starts from the same questions.
- Onboarding materials, so a new designer is useful in days, not weeks.
- Accessibility sign-off routes, so accessibility is checked at a known point instead of at the end.
04 · What changed
The team can see its work, and requests arrive ready to design.
There is now one shared view of what is in flight and who owns it. Communication is clearer, requests are better formed, and designers switch context less, which leaves more time for the design itself.
The culture moved with it: from reacting to requests towards shaping them, with partners brought in earlier.
Beyond the team
I line-manage and mentor designers through prototyping, accessibility, storytelling and design decision-making. I have run sessions on Figma Variables, prototyping, motion and AI tooling for more than 30 colleagues, and as Santander UK's AI Champion I help define how design works with AI.
05 · What I took from it
Leading design is designing the conditions for good work.
- Visibility comes first. A team that can see its work can prioritise it; one that cannot is always reacting.
- Improve what goes in. A better request does more for quality than a better review at the end.
- Introduce change in the tools people already use, and keep it alive in the rituals they already have.