When Boring is Safe

The fracture

People moving real money read consistency as competence. A misaligned number, a button that behaves one way on this screen and another way on the next - each one is a small reason to wonder if the rest of the product is held together with tape.

Research

In fintech, what's familiar feels safe. If a transfer flow doesn't work like the user's bank, they get nervous before they trust it. So instead of inventing, I studied - five competitors covering planning, investing, and full-service wealth management.

Wealthsimple

Theme-based investment buckets

Origin

Planning-led approach

Facet

Onboarding flow + pricing transparency

Range

Planning approach + flat-fee positioning

Titan

Niche, tech-focused audience

The stance

The product made the call: boring is safe. People moving real money want familiar, calm, and clear - they don't want to be impressed by gradients, they want to find their numbers and trust them. My job was to commit to that and go deep, not to argue it. That requirement turned into three rules - every component decision had to follow at least one.

See it in practice

Quiet, not loud

Every visual choice should mean something. No decoration, no gradients, no shadows that pop. Color is reserved for signal.

See it in practice

Color, one job each

Each color in the system is assigned a single job and never reused. Asset classes have fixed colors used wherever they appear; red is reserved for moments that carry weight.

See it in practice

Clear, not clever

Never make the user wonder if something happened. Tabular figures, explicit labels, inline validation, modal confirmations for big actions.

Foundations

The token system stays small on purpose.

1:1

The system

Fourteen component families, every one built against the three rules - here's the catalog.

A system maintained by one person stays consistent only if it can review itself. As the surface area grew, I built a layer of agents on top of the DS - each one a Claude Code skill that operates on the Figma file directly:

The trick wasn't the agents themselves. It was writing structured component descriptions once so they could read the file the way I do. I still make the design calls; the agents handle what used to eat my afternoon.

Results

The most concrete outcome was speed. Screen mockups that used to take 1–2 days started landing in half a day. Design review turned from "is this consistent with what we shipped before?" into "is this the right pattern for this problem?" - a much better conversation. Scope-wise, the system covers fourteen component families, thirteen-plus chart variants, an atomic table system, and a wealth-management vocabulary that no off-the-shelf system would have given me.

Reflection

Building alone is fast, but it's lossy.

What I learned: in regulated, high-stakes domains, restraint is a feature, not a constraint. The harder lesson was that working alone shapes what you make. The next version of this system needs more than another set of tokens - it needs another point of view.