The difference between a product made by a craftsman and a beginner is their experience. Innovation by definition means we have no experience yet. Where most innovation stalls is that teams try to think of the perfect answer before building anything. Build as fast as possible and get it in front of your users. Only through building and using it can you learn the nuances of what will cause it to fail, and what will cause it to succeed.

01

Asking about
the problem,
not the brief.

DISCOVERY

A brief describes what someone thinks they need. The real problem is usually one layer underneath. Before any concept work begins, I spend time with the people closest to the friction: users, support teams, sales, engineers. The questions they cannot easily answer are where the work actually starts.

This phase moves fast. Interviews, observations, quick sketches, early provocations. The goal is not a comprehensive research report. It is a sharp enough problem statement to build something against.

02

Design as if
hardware is software.

PHYSICAL  ·  DIGITAL

Most design practices live on one side of the physical-digital boundary. Products that cross it well are the exception, because crossing it well requires someone who genuinely understands both sides and can translate between them without losing anything in the handoff.

From CMF decisions that invite first touch, to atomic UI frameworks that make complex devices feel simple, to accessories that complete the experience: every decision is made with the whole system in view, not just the screen or just the enclosure.

03

Make something
before it is ready.

PROTOTYPING

You cannot think your way to a great product. You can only build your way there, iterating fast against real reactions from real people. A rough prototype in week two tells you more than a polished presentation in week eight.

This is not about skipping rigour. It is about applying rigour to the right questions at the right time. Details that seem critical before testing often turn out to be irrelevant. Problems that nobody anticipated show up immediately when something physical exists.

04

Build for
ownership,
not dependency.

LEADERSHIP

The measure of a well-led innovation project is not whether it shipped. It is whether the team that inherits it understands it well enough to keep improving it without you. That requires a different kind of leadership: coaching people into defining their own milestones, holding the standard through questions rather than answers, and making the thinking visible so it can outlast any single person.

I design for handover from the first day. Documentation, design systems, named frameworks, and trained teams are as much a part of the deliverable as the product itself.

05

Treat AI
as a craft,
not shortcut.

AI INTEGRATION

Most people achieve about five percent of what AI makes possible, and stop there. That five percent is useful but it is not craft. The remaining ninety-five percent requires the same thing that makes any tool powerful: practice, judgment, and a clear point of view about what you are trying to make.

AI does not replace the designer’s eye or the engineer’s instinct. Used well, it extends them. I have led AI adoption across organisations operating across three continents, always with the same standard: remove the friction that gets in the way of good work, without removing the human quality that makes work worth doing.