What good design means to me

What good design means: the working philosophy behind every decision I make

Ask me for a design philosophy and I'll ask which project you mean. What holds across all of them is smaller than a philosophy. It's a habit of asking why something is on the screen before anyone else gets the chance to ask me.

A drop shadow, an extra eight pixels of padding, a secondary button competing with the primary one for attention, none of it survives if I can't defend it out loud.

Most bloat in a design isn't intentional. It slips in because nobody made a call against it, and it just stayed through every review after that.

I worked on a subscription product where extending a plan needed to be disabled under certain conditions. The easy fix was greying out the button and calling it a day. The real fix was telling the person why it was locked and what would unlock it, because a disabled button with no explanation just makes someone feel stuck.

Clean matters, but only in service of something. I've seen interfaces so minimal they went quiet: no hierarchy, no friction, nothing telling the user where to look first.

Usability wins over impressiveness. A client once wanted a bolder, more premium checkout flow, and my job was to walk them through what a confusing extra step like that would cost in drop-off.

Sometimes the unglamorous version is correct, and the harder part of the job is making that case without sounding difficult.

None of this means function comes at the cost of feeling. A well-timed line of microcopy or a transition that's a beat slower than expected on purpose can do real work in a product, the kind that makes something functional also feel like it was made by someone who cared.

I think about that the same way I think about a single brushstroke in a painting. It's a decision with a felt effect, not just a technical one.

A brief tells me what a stakeholder believes the problem is. Research tells me what it actually is. Those two things rarely match, and the gap between them is where bad products get built.

I'd rather ship something boring and coherent than something clever and one-off. Novelty photographs well for a portfolio. Consistency is what holds up months later when someone else has to extend the pattern without me in the room.

Pushing back is part of the job. Staying quiet when a request doesn't serve the user only delays a harder conversation later.

Most of what people call good taste comes down to discipline applied where nobody's checking: whether a font reads better at fourteen pixels than sixteen, whether a hover state does anything or just exists because it was easy to add. Nobody claps for that kind of decision. It's still what decides whether something feels considered or thrown together.

The tools have changed more times than I can count across a decade of doing this, UI, UX, branding, illustration, fine art. The question underneath hasn't: does this serve the person on the other end, and can I explain why every part of it exists. When I can answer both honestly, that's the work done, my name on it either way.