About
Product design leader.
I build teams, shape craft, and connect design to business impact.
Background
Over 15 years working across agencies and product companies, I've had the chance to design for very different contexts [B2C, B2B, automotive, telecom, travel] before focusing on product design leadership in tech scale-ups.
My work now sits at the intersection of design craft, team growth, and business outcomes. I'm hands-on when it matters, and I know when to step back.
Trajectory
Versatility by necessity. Switching domains — tourism, automotive, telecom, retail — built the ability to learn fast, frame problems without prior knowledge, and design for users I didn't know yet. Michelin, Amadeus, ORPI.
Design at scale inside a large organisation. Led the transition of UX/UI profiles toward product design thinking. Introduced workflow tooling to align design with engineering. Built a skills framework that propagated across the Renault group.
Scale-up pace, post-acquisition complexity, global teams. Recruited and onboarded 5 Senior Product Designers during a high-growth phase. Raised the bar on craft quality and business storytelling across the design team. Shipped Data Connect — a feature built through tight PM/Engineering collaboration and ahead-of-schedule research iteration.
🧠 How I work
I'm impact-driven and detail-oriented, both at once, not alternately. I communicate clearly and early, collaborate without friction, and stay proactive about surfacing new ways to frame a problem or approach a project.
I've learned that the quality of a team's work is inseparable from the quality of its conversations.
👁️ Point of view
Product design is at an inflection point. Closer proximity to the codebase, clearer accountability for business outcomes, and the rapid expansion of AI tools are reshaping what the role means and what it can do. I see this as an opportunity to experiment, not a threat to manage.
🛠️ Tooling
A tool is only a tool. Some are worth knowing well.
Figma remains central for ideation, component work, and increasingly for design-to-code workflows via MCP. GitHub is where the work lives and ships. Claude and Cursor are where a lot of the thinking and building happens right now, often together.
Working closer to the codebase is changing how we approach design problems.
It's still early, but it really feels like the right direction if we want design to have a stronger and a more lasting impact.
🔎 Beyond work
I read a lot across design, culture, and technology. I'm drawn to how ideas travel: how a concept moves from one field to another, how communication shapes understanding. Art, music, and digital culture are part of that same curiosity.