I’ve never been very good at staying in my lane.

I’m a product designer, but my work often spills into product strategy, QA, documentation, code, and whatever else the problem needs.

From the outside, that can look like a collection of unrelated jobs: the designer who tests the build, writes the documentation, or maps the system nobody has quite drawn yet. To me, it is all the same work. Once I notice that something is broken, incomplete, or harder than it needs to be, I have trouble leaving it alone. Fixing one part often means understanding the system around it and following the problem far enough to solve it properly.

I found design through building things. I started by editing HTML templates, moving other people’s code around to see what changed. Somewhere on YouTube, I realised the experience I was modifying had first been imagined and decided by someone else, and I wanted to make those decisions too. So I taught myself Adobe XD, with YouTube as my classroom and offline access as a necessity given the internet I had. I’ve been at it ever since.

That way of learning still shapes how I work. I’m most interested in the gap between what a product looks like and how it actually works: the state nobody designed, the rule that makes sense internally but not to the person using it, or the small detail that causes the experience to fall apart. Those are the places where a product reveals how carefully someone thought it through. To me, that is craft: bringing care and judgment to the decisions that shape an experience, especially the ones most people will never notice.

Outside of work, I’m usually playing Sudoku or Minesweeper, solving a jigsaw puzzle on Google Arts & Culture, getting overly invested in a video game, or messing around with an idea that may or may not become anything.

Fun factmy hair grows into my eyebrows.