I lead design systems, and stay hands-on in product design and implementation.

How my scope changed

At Dickiebirds, I ran a studio and worked across design and front-end implementation. The two developed together because I was often responsible for both defining the experience and making it work in the browser.

At AppsBuilder, I moved further into digital product work inside a larger team. My role increasingly involved connecting design decisions with implementation constraints and supporting other designers.

At Nissan, I lead design systems across a global product organisation, stay hands-on in customer journeys and product direction, and work closely with engineering through delivery.

One example is the finance decision experience in this portfolio. Research produced a preferred prototype, but I recommended a different product direction based on what the evidence showed across both concepts. That direction was accepted, refined and carried into the delivered experience.

Making ownership transferable

Part of working at a larger scale is making sure work does not depend on one person continuing to own it.

I created version 2.0 of Nissan's native iOS and Android design system, aligning the existing mobile system with the web design system before handing over ongoing ownership and supporting the transition.

Developing other designers started earlier in my career. At Dickiebirds, I helped a designer move from mainly WordPress-based work into UX/UI design, and I also supported other designers at AppsBuilder.

Current direction

I'm primarily interested in senior Design Systems and Design Engineering leadership roles. I also remain a strong fit for Lead or Staff Product Design roles on complex platforms and products, where systems and implementation depth are an advantage.

My strongest work sits where customer decisions, system constraints and implementation are closely connected. I stay involved deep into delivery, with the product problem as the starting point.