Clutch · Fintech · Design Systems

Scaling digital

banking across

150+ credit

unions

Scaling digital

banking across

150+ credit

unions

I took a fragmented component library and turned it into an accessible, well-documented design system for more than 30 white-label banking apps.

Role

Senior Product Designer

Timeline

January 2026 — Present

150+

Credit Unions

supported

30+

Applications using

the Design System

137

Components

reviewed and documented

2.2 WCAG

AA target

accessibility

01 / Context

The challenge

A growing platform without a reliable design system

Each credit union wants the app to feel like its own. So the brand needs to be flexible, but how things work, accessibility and behavior need to stay the same everywhere.

When I joined, the team was migrating between two design systems and nobody owned it. Documentation was incomplete, accessibility wasn’t built in, and a component marked as ready could still change in Figma after handoff.

Before

Design and code didn’t match

Figma

Changed after handoff

Button

Radius 12 · Height 48

Storybook

In development

Button

Radius 6 · Height 44

Mismatch

×

Figma

Changed after handoff

Continue

Radius 12 · Height 48

Storybook

In development

Continue

Radius 6 · Height 44

Mismatch

×

Figma

Changed after handoff

Continue

Radius 12 · Height 48

Storybook

In development

Continue

Radius 6 · Height 44

Mismatch

×

Establishing the baseline

Audit

first,

then build

Audit

first,

then build

Before adding anything new, I wanted to know what we had. I connected

Claude to Figma through MCP for a health check, then reviewed

components and accessibility by hand. Most problems were structural:

naming, tokens, metadata, coverage and parity with code.

Before adding anything new, I wanted to know what we had. I connected

Claude to Figma through MCP for a health check, then reviewed

components and accessibility by hand. Most problems were structural:

naming, tokens, metadata, coverage and parity with code.

↳

No established token architecture

No established

token architecture

↳

Missing documentation and accessibility states

Missing documentation

and accessibility states

↳

Unnecessary variants and inconsistent naming

Unnecessary variants

and inconsistent naming

↳

No contribution, versioning or deprecation process

No contribution, versioning

or deprecation process

02 / Align

02 / Align

Creating a source of truth

Exploration stays flexible

Production stays reliable

I split the work into two files. Designers explore freely in one, and only reviewed, documented

components go into Production. That gave everyone one clear path from a product need to code.

Flexible workspace

Exploration

Ideas · Requests · Product needs

Review

→

Design truth

Production Figma

Reviewed · Documented · Versioned

Parity

↔

Implementation truth

Storybook

Built · Tested · Released

“If it isn’t in both, it isn’t part of the Design System.”

Creating a source of truth

Exploration stays flexible

Production stays reliable

I split the work into two files. Designers explore freely in one, and only reviewed, documented

components go into Production. That gave everyone one clear path from a product need to code.

Flexible workspace

Exploration

Ideas · Requests · Product needs

Review

→

Design truth

Production Figma

Reviewed · Documented · Versioned

Parity

↔

Implementation truth

Storybook

Built · Tested · Released

Rebuilding the foundation

From raw

values

to shared

product

decisions

From raw

values

to shared

product

decisions

I went through the original components one by one, removed

variants nobody needed, fixed the naming and set up three

levels of tokens: primitive, semantic and component.

I went through the original

components one by one, removed

variants nobody needed, fixed the

naming and set up three levels of

tokens: primitive, semantic and component.

↓

02 · Semantic

color.action.primary

Meaning

↓

↓

03 · Component

button.primary.bg.default

Behavior

01 · Primitive

blue.600

#2E63D4

Accessibility as a foundation

Accessibility as a foundation

Fixing the

pattern, not

every screen

Fixing the

pattern, not

every screen

Input borders didn’t meet contrast requirements, and

that affected every form in the platform. Fixing the

shared component fixed it everywhere at once.

Input borders didn’t meet contrast requirements, and that affected every form

in the platform. Fixing the shared component fixed it everywhere at once.

WCAG 2.2 · AA target

Before · insufficient contrast

Email address

name@email.com

Border disappears against the surface

After · accessible states

Email address

name@email.com

Persistent label · clear focus · defined error behavior

Establishing governance

Every new component has to earn its place

Every new component has to earn its place

Before a component goes into Production, it has to solve a problem more than one

product has, not duplicate something we already have, and work across products.

01

Proposal & scope

Validate the problem, use cases and

whether it belongs in the shared system.

Approved to explore

02

Design exploration

Define states, variants, configuration

boundaries and accessibility behavior.

Approved for production

03

Production promotion

Apply tokens, documentation, naming

and component-level versioning.

Ready for engineering

04

Implementation

Build in Storybook and validate visual,

behavioral and accessibility parity.

Release approved

White-label without fragmentation

Credit unions

can change

their brand. They

can’t change how

things work.

Credit unions

can change

their brand. They

can’t change how

things work.

Configurable

Brand colors, logo, content and approved swappable areas.

System controlled

Structure, spacing, interaction, accessibility and component states.

North

Available balance

$12,480.00

View account

The impact

What

changed

What

changed

137

reviewed and documented

components

5.6 → 8.9

internal system-health

assessment

7–8

product teams using the

foundation

~50

engineers supported by

clearer specifications

The Production file is fully in use. To be honest, Storybook parity is still in progress. We’re

doing it in baby steps, based on engineering capacity and what’s safe for partners.

The Production file is fully in use. To be honest, Storybook parity is still in progress. We’re doing it in baby steps, based on engineering capacity and what’s safe for partners.

My role

What I own and

who I work with

What I own and

who I work with

I own

Design direction, Production Figma, governance, tokens,

accessibility standards, documentation and component reviews.

Design direction, Production Figma, governance, tokens, accessibility standards, documentation and component reviews.

I partner on

Product needs, engineering feasibility, Storybook implementation,

rollout strategy and compliance requirements.

Product needs, engineering feasibility, Storybook implementation, rollout strategy and compliance requirements.

Today designers and engineers work from the same

source of truth, and new features start from

components that are already accessible and documented.

Today designers and engineers work from the same

source of truth, and new features start from

components that are already accessible and documented.

Today designers and engineers work from the same

source of truth, and new features start from

components that are already accessible and documented.

03 / Let's connect

Open to Senior & Staff product design roles · US remote

Building something complex?

I’d love to hear about it.

Building something complex?

I’d love to hear about it.

Building

something

complex?

I’d love

to hear

about it.

Stefany Andrade · Senior Product Designer, Design Systems

Brazil · Remote, US hours

© 2026

02 / Align

“If it isn’t in both, it isn’t part of the Design System.”

Creating a source of truth

Exploration

stays flexible

Production

stays reliable

I split the work into two files. Designers explore freely in one, and only reviewed, documented components go into Production. That gave everyone one clear path from a product need to code.

Flexible workspace

Exploration

Ideas · Requests · Product needs

Review

→

Design truth

Production Figma

Reviewed · Documented · Versioned

Parity

↔

Implementation truth

Storybook

Built · Tested · Released