Process & principles

How I work.

Seven frameworks. From ambiguous brief to operational system.

From brief to system

—A brief describes a symptom. The work starts when you find the cause.
—Reframing is not a delay. It is the fastest path to the right solution.
—Every delivery creates governance debt if the system is not designed to outlast the project.

—Research does not slow down delivery. Research done without a decision trigger does.
—An interface is a hypothesis. Ship it fast enough to learn, slow enough to be intentional.
—UI quality is not about aesthetics. It is about the precision of the signal sent to the user at every interaction.
—A component is not a reusable element. It is a documented decision about how the system should behave.
—The gap between design intent and engineering reality is always a communication problem, never a technical one.

—Every design decision lives at the intersection of user need, business constraint and system reality. Ignore one and the other two will collapse it.
—The best decision is not the most elegant one. It is the one the organisation can actually implement.
—Document the why, not just the what. Future teams will change the solution. They need to understand the reasoning.

—Fragmentation is never a design problem. It is always a governance problem wearing a design costume.
—Tokens before components. Architecture before aesthetics. Structure is the only thing that scales.
—A system that cannot be understood by the team that did not build it has already failed.

—AI amplifies what is structured. It cannot replace what is not.
—The quality of the output is directly proportional to the quality of the knowledge architecture upstream.
—Good AI disappears into the product. The experience feels smarter. The technology is invisible.

—Being in the room where decisions are made is not a status move. It is where fragmentation is prevented.
—Translate coherence into business language. Inconsistency costs time and money. That lands harder than showing a Figma library.
—Influence without authority requires making the right decision feel inevitable, not imposed.

—A design system is what you document. Design culture is what you do when no one is watching.
—Contribution models fail when they optimise for process over adoption. Make it easier to contribute than to ignore.
—Rituals are not meetings. They are the infrastructure of shared decision-making.