How I work.
I like problems without obvious answers. The kind where understanding the product, questioning assumptions, and working closely with people can turn a good interface into something genuinely useful.
Five things shape how I approach them.
I look beyond
the interface.
I start with the bigger picture: what people need, what the business wants to achieve, where the product fits, and what's technically possible.
Design isn't an isolated layer. Better solutions come from understanding how these pieces connect.
I bring clarity
to complexity.
Enterprise products carry legacy behaviours, competing requirements, and plenty of edge cases. I enjoy making sense of them: simplifying workflows and clarifying hierarchy without losing what people rely on.
The goal isn't always to remove complexity. It's to make it easier to navigate.
I care about
the details.
Hierarchy, spacing, interaction states, responsiveness, and accessibility all shape how a product feels every day. I explore different directions and refine the details until the experience feels considered.
Craft isn't the finishing touch. It's part of solving the problem.
Good design is
a team sport.
I work closely with engineers, PMs, researchers, and designers, staying involved in decisions rather than just handing over files.
I value honest feedback and healthy disagreement. I'll challenge an approach when it could be better, and change my mind when someone brings a stronger idea.
I get my
hands dirty.
I'm curious about how things get built. I use AI-assisted tools to prototype ideas, implement interface changes, and contribute code. I've raised and merged PRs and built tools that connect design and implementation.
Designers don't need to become engineers. But getting closer to the code helps me shorten the distance between an idea and something people can use.