Process & principles

How I work.

Seven frameworks. From ambiguous brief to operational system.

01

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.
From brief to systemA brief describes a symptom. Reframing finds the cause. The system outlasts the project.BRIEFREFRAMECAUSESYSTEMGOVERNANCE DEBT

02

Craft : UX · UI · System

  • 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.
Craft: UX, UI, SystemThree overlapping layers: research, interface, system — the gap between intent and reality is always communication.RESEARCHdirection, not certaintyINTERFACEhypothesis, ship to learnSYSTEMdocumented decisionGAP = COMMUNICATION

03

Decision making

  • 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.
Decision makingThree forces converging toward a single decision point: user need, business constraint, system reality.USER NEEDBUSINESSCONSTRAINTSYSTEMREALITYDECISION

04

System design

  • 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.
System designTokens before components. Architecture before aesthetics. Structure is the only thing that scales.TOKENSprimitives · semantic · componentCOMPONENTSvariants · states · documentedGOVERNANCEADR · council · ritualsSCALES

05

AI as an operational layer

  • 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.
AI as an operational layerAI amplifies what is structured. Knowledge architecture upstream, invisible output downstream.STRUCTUREknowledgearchitectureAIamplificationOUTPUTtechnologyinvisibleGARBAGE IN · GARBAGE OUT

06

Cross-functional governance

  • 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.
Cross-functional governanceInfluence without authority. Design at the center of C-level, product, engineering and brand.C-LEVELdecisionsPRODUCTdirectionENGINEERrealityBRANDcoherenceDESIGNinfluence

07

Design ops

  • 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.
Design opsThree pillars: system, contribution, rituals. Design culture is what you do when no one is watching.SYSTEMwhat youdocumentCONTRIB.easier thanignoringRITUALSinfra of shareddecisionsDESIGN CULTURE = WHAT YOU DO WHEN NO ONE IS WATCHING