I turn complex needs, constraints and opportunities into clear product direction. My work starts before the interface, by understanding the domain, the people and the organisation behind the problem. I prototype early, decide with stakeholders and engineers, and choose what stays visible, what gets simpler and how different needs can coexist.

Research gives me enough understanding of a problem to make meaningful decisions. I combine interviews, co-creation, card sorting, surveys, field observation and quantitative analysis to understand behaviours, vocabulary and mental models, not only pain points. Findings become shared maps and hypotheses that keep the whole team's decisions grounded in reality.

Typography shapes how I think about systems, detail, rhythm and identity. With LO-OL, I move from single letterforms to the systems type has to work in. I see it as both a cultural object and an interface tool: it carries tone, sets hierarchy and guides navigation. That precision carries into my product work.

I code to understand what happens to a design after it leaves the canvas. I work with React, Next.js and TypeScript, across APIs, headless systems and automation. It lets me prototype realistically, work closely with engineers and weigh implementation cost early. Code, performance included, is another material for designing experiences.

I work daily, at an advanced level, with Claude Code, Cursor and Warp AI, across research, strategy, design, prototyping and development. I use AI to explore information, challenge hypotheses, compare directions and move between design and production code. It stays a collaborative layer guided by human judgment, leaving more time for the decisions that need care.