Make the difficult feel obvious.
Complex software does not have to feel complicated. I design the interaction model, information structure and visual system together, then prototype the important moments until they are clear. The result is a product with a strong point of view that still feels natural on the first use.
Discuss this kind of work
The important parts, held together.
Interaction architecture
Define how the product behaves before polishing how it looks, so every screen belongs to a coherent system.
High-fidelity prototyping
Make the key journeys tangible early enough to test the decisions, not just present them.
Interface and design systems
A distinctive visual language with the reusable foundations needed to stay consistent as the product grows.
Motion and feedback
Purposeful transitions and micro-interactions that explain state, reward action and never get in the way.
Bring me in while the important decisions are still movable.
The product has grown screen by screen
Individual features work, but the overall experience no longer has a clear model or a recognisable point of view.
Users rely on training and workarounds
The interface reflects the organisation or database more clearly than it reflects the job someone is trying to do.
The vision needs to survive production
You need more than a persuasive concept: the decisions must remain coherent through edge cases, responsive states and real data.
A coherent product model
Clear information architecture, interaction rules and priority journeys that make the whole product easier to reason about.
A testable experience
A high-fidelity prototype that lets users and stakeholders react to the important behaviour, not imagine it from static screens.
A system ready to grow
A distinctive interface and reusable foundations that hold their quality when new features, people and platforms arrive.
One context. Short, informed loops.
The same senior practice runs through research, design and engineering. Each discipline sharpens the others, so decisions move quickly and the original intent does not disappear between departments.
Find the organising idea
Reduce the product to the objects, actions and decisions people need, then give that complexity an understandable shape.
Prototype the hard moments
Work through the interactions where confidence matters most, using realistic content, states and constraints.
Design through the build
Keep design and engineering in the same loop so detail improves in production instead of being lost at handover.
You work with the person doing the thinking and making the product. Trusted specialists join when the work genuinely needs them — never as layers between you and the decisions.