Systems

Here is the belief that survived all of it, the thing that’s true no matter which room I’m standing in:

I do not design screens. I design systems for people.

I know how that sounds. Let me be precise about what I mean, because it’s not a slogan — it’s the most practical thing I know.

A screen is an output. It’s the visible end of something. By the time a problem shows up on the screen, it was already created somewhere upstream — in a wrong assumption, a missing step, a relationship nobody mapped. If you fix the screen, you’ve fixed a symptom. The problem regenerates the next day in a new form. I learned this as an engineer and I’ve never been able to unlearn it: you cannot fix the surface by touching the surface.

So I work one layer down. The unit I actually design in is not the page or the component — it’s the behaviour. What is the person trying to do? What do they believe? Where will they hesitate, and why? Get the behaviour right and the screen almost designs itself. Get the behaviour wrong and no amount of polish will save it.

The second principle came from the enterprise work and it’s just as portable: the best systems create accountability without friction. Any system can force compliance. Forcing it just teaches people to escape it. A system earns its keep when doing the right thing is also the easiest thing — when the structure quietly makes good behaviour the path of least resistance.

The reason I can move between a vodka brand and an enterprise platform without losing my footing is that I’m not actually switching subjects. The industry changes. The user changes. The technology changes. The thing underneath never does. There is always a person trying to be understood, and there is always a structure producing their behaviour. My job is to find that structure and design it on purpose.

That’s what stays constant when everything else moves. It’s the whole reason this isn’t a portfolio of unrelated things. It’s one way of thinking, applied repeatedly, in public.

❡