Approach

I started my career as a Product Designer at Google’s moonshot factory, X, helping early-stage teams build 0-to-1 products. I worked closely with founders, often owning both product and design, and hands-on building the first product versions (you can find my code contributions in Google codebase - and that even before ChatGPT!).

Building is how I design. I understand a problem best once something real exists, so I prototype early - and often in the production code.

I have worn a lot of hats ever since, and that is the part I like most: in my first role I was mostly PM and designer, and a bit of a software engineer when the week needed one. I love being a builder, not only the one holding the vision.

Product DNA, not what everyone else is shipping. I shape the few core ideas a product is built on, rather than watching what everyone else is doing, so every feature has a reason.

Some of those bets worked, others flopped - and that’s exactly what I believe shaped my current approach to design and product building: I care about strong product decisions, clear concepts, testing fast, and getting things done. I love thinking via building! I’m most energised by teams that push boundaries, challenge conventional thinking, and are open to trying and learning.

Concepts align the team. A rough concept in front of people early teaches the team more than a polished answer shown late; at McKinsey that meant 100+ users. It settles how the product should feel, and it creates urgency - which is how I get work to actually happen.

Currently, I’m at Miro, leading design for AI surfaces and rethinking how AI works in an infinite, multiplayer canvas for collaboration.

Hands-on polish, in production. I stay in it to the end. The last ten per cent happens in the real thing, not in the file.