About Me
I've spent 15 years in tech and design. I started with computer science in high school — programming, web technologies — before specialising in UX and degree in design. That early technical grounding still shapes how I think: I see products as systems, and I speak the language of engineers rather than translating for them.
I've spent 15 years in tech and design. I started with computer science in high school — programming, web technologies — before specialising in UX and degree in design. That early technical grounding still shapes how I think: I see products as systems, and I speak the language of engineers rather than translating for them.
What I'm actually good at is finding the problem worth solving. Most teams jump to solutions too fast. I slow that down, dig into what users are really struggling with, and separate the real problem from the symptom everyone's been treating instead.
I don't take the status quo as a given. If a process, a product, or an assumption isn't working, I'll say so and push for something better — even when that means revisiting decisions other people have already signed off on. That's uncomfortable sometimes. It's also how better work gets made.
Outside of product, I love learning why people behave the way they do — psychology and neuroscience give me a lens on the same patterns I look for in products. New technology and emerging trends pull me in the same way. In my spare time, I travel for the culture and the aesthetics, read, and always have a film or a new restaurant on the list. Underneath all of it, I care — about the people I work with and the problems I take on, not just the outcome.
Right now I'm building (https://jotts.app), a personal career management app — born from watching how much of people's true value goes unseen and unowned in their own careers. It's taught me as much about building 0→1 as any job has.
Worked At
Founded
How I Work
I start with the user, not the brief. Before I design or build anything, I want to understand what's actually broken for the people using the product — not just what a roadmap assumes is broken. That discovery work is where I spend most of my energy, because a beautifully executed solution to the wrong problem is still the wrong problem.
I work at the intersection of product, design, and engineering — where the real trade-offs get made. I like taking an idea far enough to test whether it actually holds up, whether that's through research, prototyping, data, or building the alternative myself. Sometimes that means challenging a plan already in motion; sometimes it means proving a different direction is possible.
I care about outcomes over process for its own sake. I'll flag when something isn't working, propose a better way, and stay hands-on enough to see it through — not just hand off a recommendation and move on.