Decisions,made in the right order.
Approach is the part of the studio that stays the same when the brief changes. Four pillars, five frameworks, a kill list. Read it as a field manual — not a manifesto.
What stays true when the brief changes.
Motion as construction
Motion is not decoration. Every transition is a deliberate act of assembly — the work shows you how it's built, not just what it is.
- Mass / weight / inertia
- Mask reveals over fades
- One signature moment per surface
- Reduced-motion as a peer
Systems before surfaces
We design tokens, primitives, and rules first. Surfaces are a deterministic output of the system, not a hand-crafted exception.
- Tokens before pages
- Primitives over patterns
- Variants in code, not just Figma
- One source of truth, always
Restraint as a discipline
Less surface area, more meaning. Restraint compounds — every element you don't add is one you'll never have to maintain.
- Cut before adding
- One typeface, two weights
- Borders earn their pixel
- Defaults are decisions
Speed as a craft
Speed isn't hacking. It's knowing which decisions to commit to in week one and which to defer until week six.
- Two-week sprints
- Weekly demos, no slides
- Ship to staging in days
- One owner per surface
Rules we use to decide.
- 01The decision rule
“If two paths feel equal, pick the one with fewer parts.”
Most arguments in design are between options that are roughly equivalent in outcome but differ in maintenance cost. Pick the smaller one.
- 02The motion test
“If you mute it, does the meaning survive?”
Animation should reinforce hierarchy, not invent it. Strip every transition mentally — the page should still read.
- 03The naming rule
“If a thing needs a paragraph to name itself, the thing is wrong.”
Names compress decisions. A name you can't defend in one sentence is a sign the thing underneath is two things stitched together.
- 04The performance budget
“Every kilobyte is a vote against the user.”
We set a budget per surface in week one and treat it as a non-negotiable, not a stretch goal.
- 05The dark-side principle
“Design empty, error, and loading states first.”
Happy paths are easy. The work happens in the failure modes — design them before the polished surface seduces you.
What we won't ship.
- / AvoidAnimation as garnish/ Instead
Animation as construction — what the user is building toward.
- / AvoidType as decoration/ Instead
Type as hierarchy — three sizes, one rhythm, no mixed metaphors.
- / AvoidComponents as a Lego pile/ Instead
Components as a vocabulary — fewer pieces, sharper grammar.
- / AvoidColor as personality/ Instead
Color as signal — primary, accent, system; nothing else.
- / AvoidCopy that hedges/ Instead
Copy that commits — one verb, one object, no qualifiers.
- / AvoidRoadmaps that bloat/ Instead
A north-star moment, three priorities, a kill list.
“Restraint is not a style. It's the willingness to stop designing once the work is finished.”