← All services Approach ยท Design system

Four greys in production, and nobody decided on any of them.

Without a system every screen is a fresh set of decisions. Two teams build the same modal twice, slightly differently, and the product slowly stops looking like one product. The cost isn't taste. It's the week you lose every month.

What we find

The inventory is always worse than anyone expects.

What you get

Built from your product, then used on it.

We inventory what's actually shipped first. Then one value per decision, documented with the reasoning behind it, and we build real screens with the system before handing it over. A system that hasn't been used on real work isn't finished, it's a proposal.

How it runs

Inventory, decide, build, hand over.

01

Inventory

Everything in production. Expect it to be worse than you think.

02

Decide

One value per decision, reasoning written down.

03

Build

Tokens, components, docs, then real screens made from them.

04

Hand over an owner

Migration sequenced, with a name against it.

What we think

A system nobody uses isn't a system. It's a Figma file with a nice cover.

Adoption is a design problem too. If it isn't easier than not using it, your team won't, and they'll be right.

Proof

See all the work →
Endeavor
Approach

Endeavor

One system across a product that had grown in four directions.

RAWW
Approach

RAWW

Brand and product on one set of tokens from day one.

Kronologic
Approach

Kronologic

A component library that let a small team ship consistently.

Try before anything else

Send us one screen.

Pick the screen that's costing you the most. We redesign it in five working days, free, no contract. You keep the file whether or not we carry on.

01

You send the screen and tell us what it's supposed to do.

02

We redesign it in five working days, and walk you through why every change is there.

03

You keep the file. If it lands, we talk about a pod. If it doesn't, you're still one screen better off.

Send me the screen

One screen per company. We take three of these a month, so tell us early if your date is tight.

Related

Services

Product redesign

Untangle a product that grew feature by feature, so people reach the value you built.

Services

Team extension

Drop a senior pod into your team. In your tools and shipping by the end of week one.

Make consistency the default

Twenty minutes with the founders. Tell us how many buttons you have and we'll tell you what it's costing.