About.

Fifteen years of design work taught me one thing above everything else: the best outcomes happen when designers treat engineers, product managers, and data scientists as equals, not as obstacles to the vision.

I've spent the last 7+ years owning end-to-end design for B2B SaaS analytics products, which is where I found the kind of work I love most: complex, ambiguous, cross-functional, and full of moments where the right answer only becomes visible once someone builds the structure to see it.

When a framework doesn't exist, I build one. When a team needs alignment, I create it. My approach is collaboration-first and evidence-led: I treat research as non-negotiable, hold quality standards by instinct, and lead through empathy rather than authority.

Beyond individual features, I care about the systems that make good design scalable: design systems built in genuine partnership with engineering, discovery workshops that produce shared direction rather than design hand-offs, and organisations where design is a strategic contributor, not a service function.

I speak both languages, design and code. I'm genuinely curious about technology, enjoy getting hands-on with code, and read engineering conversations with real interest rather than polite patience. That lets me collaborate with engineers as a peer, understand their constraints from the inside, and build the kind of trust that makes cross-functional teams actually work. Design thinking and engineering logic aren't two different worlds to me. They're the same problem viewed from two angles.

That makes me the bridge most product teams are missing: someone who facilitates an alignment workshop with 15 stakeholders and pushes pixels in Figma at midnight, driven by the same commitment throughout: building the right thing, not just building things right.