THE INTERFACE UX PROCESS
The process scales from a two-week study to a multi-quarter enterprise programme. The phases stay stable because they protect the decision. The methods, cadence, people, and artefacts adapt to the product.
THE PRINCIPLE
Every gate converts discussion into a durable product record. It names the evidence, accepted tradeoff, owner, implementation consequence, and open question. Product, design, engineering, legal, and leadership can return to the same truth.
The work does not advance because a presentation felt polished. It advances because the decision is understood well enough to test and build.
THE FOUR PHASES
Timelines shown are representative. Every engagement has its own scope and written gate contract.
Week 1-2
Find the real task, failure, and consequence.
A signed decision memo names who, what, why, consequence, owner, and what evidence could change the direction.
Week 2-4
Define the objects, states, roles, flow, and exceptions before the surface.
The working flow survives task trials, edge conditions, technical review, and the intended operating context.
Week 4-8
Make behaviour precise enough to feel and build.
The staged build matches the accepted behaviour across responsive, keyboard, loading, failure, and reduced-motion states.
Post ship
Test the decision against the baseline and keep the evidence attached.
The record states what moved, what did not, the outcome window, the evidence boundary, and the next accountable action.
THE WORKING WEEK
We keep research, product, design, engineering, and the accountable leader close enough to correct the work early.
Question, risk, owner
Behaviour and evidence
Flow, state, interface
Use, load, comprehension
Gate and next action
THE QUALITY CONTRACT
The product is not ready when the happy-path frame is beautiful. It is ready when the interaction remains understandable under real use.
Every consequential action works without a pointer and focus remains visible.
State never depends on colour alone and information survives real display conditions.
Work that takes time is acknowledged, explained, and safe to leave.
Partial and failed states preserve user input, agency, and a route to recovery.
Zoom, screen readers, dynamic type, motion preference, and touch targets are designed as product states.
Every accepted interaction keeps the research, tradeoff, and measure close to the build.
WHAT SHIPS
You own both. The evidence stays attached to the interface engineering receives.
THE WORKING STACK
THE PROCESS
Name the person, the decision, the failure, and what the business carries when it goes wrong.
Start a Product