[The operational baseline]

Manifesto

I work in the overlap of two things most designers separate: how a product feels, and how it holds up.

My thoughts

01. Strategy demands structure

Most design problems aren't design problems. They're positioning problems wearing a UI costume. A founder says the signup flow isn't converting; the real issue is they can't explain what the product does in one sentence. A team says the dashboard is confusing; the real issue is they don't know who it's for. No amount of pixel work fixes a product that hasn't decided what it is.

So strategy comes first. Not as a phase before design, but as the first design decision.

02. Systems require identity

Once the strategy is clear, the interface has to carry it. This is where most products fail in the other direction. They get the positioning right and then ship something that looks like every other SaaS - same five components, same template energy, same flat illustrations. The product becomes invisible inside its own category.

The fix is to design like a human made it. Deliberate type. A color system that means something. Visual decisions that match this product, not the generic version of its category. The good interfaces feel like themselves. You can recognize them across screens.

03. Aesthetics require strategy

But "feels like itself" can't survive contact with a real product team. Features get added. Edge cases appear. Engineers ship at 2am. Without rules underneath - variables, components, behaviour, states - the design falls apart the moment a new screen needs to exist.

So the third job is the system. Type scale, spacing rhythm, color tokens, component logic. Not because it's elegant - because without it, everything you built in the first two stages quietly degrades over six months of feature work.

04. Absolute reduction

Strategy without craft is cold. Craft without strategy is decoration. Systems without either is bureaucracy.

The job is all three at once.