Available for work
How i work
I don't take problems at face value. Usually what's presented as a problem is a symptom of something deeper, something structural.
I figure out what's actually going on, and then get to work on that. It takes longer to get started but it means the solutions don't just patch things over. They fix the underlying issue and hold up better over time.
Interaction Design
I design the behaviour of a product before I design its appearance. That means mapping the full workflow first — understanding how every step connects to the ones around it — before touching any individual screen. Individual interactions only make sense in the context of the whole.
UI Design
In complex products UI isn't decoration, it's how users make sense of what they're looking at. Labels, hierarchy, and visual relationships do real functional work — they tell people where they are, what they're looking at, and how the pieces relate to each other. I design interfaces where those things are clear at a glance, because if someone has to hunt for that information the interface has already failed.
UX Research
Research is only useful if it leads somewhere. I've seen projects spend significant time and money on research that produced abstract findings with no clear path to a design decision. My approach is narrower and more deliberate — I research the product, the market, and how competitors are solving the same problems. Then I test assumptions with users once there's something concrete for them to react to. Feedback against a prototype is worth ten times the same conversation in the abstract.
Information Architecture
The way something is organised determines whether it gets used at all. People navigate products using mental models they already have, and if the structure fights against those models they'll give up or work around it. My job is to understand those models and design the architecture around them. Sometimes that means guiding people through an experience step by step. Sometimes it means getting out of the way and putting the information right where they expect it. The skill is knowing which is which.
Content Design
The people closest to a product are often the worst at explaining it. The deeper you are in something the harder it is to remember what it's like not to understand it. I work on the assumption that good writing is part of good design. If someone can't understand what a product does or why it matters, the interface hasn't done its job. I've rewritten product copy, homepage messaging, and settings language across multiple projects, and I write about design and technology for a broader audience.
Writing
Who I work with