Nick Weller

← All work

design-system.txt · Case study · Skimming time ~35 secs

Builds the part of ANZ's apps nobody notices

Open the ANZ app and you won't see the design system. That's the point. Underneath every screen is a library that 100+ designers and 1,000+ front-end developers build with, and it gives the bank back about 44,000 hours a year.

It runs on a small team. This is how.

The ANZ app home screen, built from the design system.

Invisible on purpose

ANZ is one of Australia's leading banks, around 40,000 people worldwide. Its retail division alone has 100+ designers and 1,000+ front-end developers, and most of them touch the design system every day without giving it a thought. When it works, a button is just a button.

I'm responsible for what the system produces, where it's heading and what's in the delivery backlogs, across all four platforms. The measure I care about is how little anyone has to think about it.

Quick facts2025 – now
Role
Creative and Design Systems Lead
Platforms
iOS, Android, web, EDM
Insertions
1.2M+ combined
Web Core
46 teams
Return
6.5× at current adoption
Same components, native to each platform. Switch between them.

A small team, a big surface

Four systems, 1.2M+ component insertions and dozens of teams, served by a team you could fit around one desk. That ratio only works if the system is the easiest way to ship, so nobody goes looking for a workaround. Every component we put out has to be quicker to use than to rebuild, and trustworthy enough that design, engineering and brand stop second-guessing it.

It pays off: designers who adopt the system spend 87% less time on design tasks, which gives each of them roughly two workdays back a week.

Hands on, so nobody has to think about it

I don't run the system from a roadmap deck. I'm in the Figma libraries most days, because the quickest way to earn a team's trust is a component that already does what they need.

Every platform gets a full set of templates, mirrored so a designer moving from iOS to web finds the same flows in the same places. I shipped the monogram live text component (15 variants, 5 sizes, 3 platforms), swapping rasterised PNG symbols for text that binds to tokens. I'm also leading the move to a three-tier token architecture and a federated model, so contribution scales past the core team instead of queueing behind it.

Letting AI do the drudgery

A small team has to be faster than its headcount. I built an AI-assisted workflow (Claude Code with custom ANZ design skills) and use it on live deliverables. A table component went from a 120-variant matrix to a row-based build, with instance swaps across 81 cells. Assessment and documentation that used to take hours now takes minutes, which leaves the team's time for the decisions only people should make.

Ready on launch day

Invisible also means nobody waits on the system when the hardware changes. Our iOS system is built on Apple's native components, so when iPhone Duo arrived with its foldable screen, every component already knew how to respond to the new layouts. ANZ shipped support for it on launch day. No rebuild, no catch-up sprint, and most customers never knew there was anything to do.

The same home screen on iPhone Duo, folded and unfolded. Nothing was redesigned for it.

What invisible is worth

A system nobody notices is easy to call a cost centre. So we measure it.

87%

less time on design tasks

Two workdays back a week for each adopting designer

44k

hours saved a year across the org

The same as staffing another 23 full-timers

6.5×

return at current adoption

The system pays for itself in under two months each year

The system has become shared infrastructure that silently speeds up delivery. Most teams only notice it when it's missing.