Senior product designer / designing web interfaces since 2006
I stay with the problem until it works.
I make complex products and systems easier to understand, use and maintain. My work connects product thinking, UX, interface design, systems, identity and implementation where those disciplines most need to agree.
Career perspective
Twenty years of connected design practice.
The breadth is useful because the hardest problems rarely stop at one discipline. I can frame the question, design the experience and stay close enough to delivery to protect the reasoning.
-
01
View evidence
Packt
Enterprise design-system architecture, component foundations, documentation and front-end implementation.
-
02
View evidence
TUI
Product and system work across internal applications, aircraft experiences and service content.
-
03
View evidence
Chevin Fleet Solutions
Fleet-management product design, interface modernisation and a scalable identity system.
-
04
View evidence
Independent practice
Portfolio systems, identity, information design and a methodology for inspectable design work.
Working principles
Clarity is a chain of decisions.
Useful design makes the reasoning inspectable. It shows what is known, what remains uncertain and how each decision will survive the next handoff.
-
01
Clarify without theatre
Reduce avoidable complexity without pretending the underlying problem is simpler than it is.
PROBLEM / LANGUAGE -
02
Use evidence before certainty
Separate observed facts, working assumptions and desired outcomes so decisions carry honest authority.
EVIDENCE / BOUNDARY -
03
Design systems for people
Create foundations and patterns that help teams make better decisions rather than simply enforcing uniformity.
SYSTEM / ADOPTION -
04
Keep delivery in the room
Resolve interaction, accessibility, content and implementation constraints while the design can still respond.
DESIGN / BUILD
Collaboration and implementation
Design and delivery belong in the same conversation.
I am comfortable moving between strategic framing and fine interface detail, then carrying decisions into code or a precise developer handover. Tools can accelerate preparation and validation, but claims, priorities and consequential decisions remain visible and human-owned.
-
01
Frame Problem / people / evidence
-
02
Connect Content / behaviour / system
-
03
Resolve Direction / prototype / authority
-
04
Deliver Build / validate / transfer
ONE CONNECTED LINE OF RESPONSIBILITY
Need senior judgement that stays connected to delivery?
Tell me about the role, product or system and the decision that needs to become clearer.
Start a conversationI usually respond within two working days.