Good interfaces don’t ask for attention. They make the next step feel obvious, the structure feel natural, and every motion earns its place.
Before I think about layout, typography or motion, I need to understand what I am actually designing for.
I start with the brand and the business behind it - what it does, what it offers, what it wants people to understand, and what already exists. I look through the available content, the current website if there is one, existing analytics and the wider market to understand both the opportunities and the limitations of the project.
Then I look at the people who will actually use it. Who are they? Why are they coming to the site? What do they already know, what are they trying to find, compare or decide, and where are they likely to hesitate? Age, context, device and familiarity with the product can all change what the experience needs to do.
Competitors are useful here too - not as something to copy, but as a way to understand the conventions people already recognise and the places where a brand can behave differently.
This stage is not about collecting information for the sake of research. It is about reducing noise. Finding what matters, what can stay secondary, and what the whole experience needs to accomplish.
Only then can the design start making decisions.
01 / UNDERSTAND & DEFINE
BEFORE THE INTERFACE
Every decision should have a reason to be there
DESIGN STARTS WITH UNDERSTANDING
Once the direction is clear, priorities need to become a structure.
Content needs an order, and related ideas need to belong together. Structure defines what appears first, what needs comparison, and how one decision leads naturally to the next.
The goal is to turn separate pieces of information into one clear experience.
02 / EXPERIENCE DESIGN
STRUCTURE & FLOW
A page starts to work when every section has a job. One introduces the idea, another adds context, another helps compare options, another leads to action.
The structure is the order that makes all of those parts feel connected - so the user never has to stop and figure out where to go next.
Give content a role.
More information does not always make something easier to understand. When options share many of the same details, the important differences can quickly disappear.
The structure should bring those differences forward, while keeping the deeper information available when it is needed.
MAKE COMPLEXITY EASIER TO READ.
GUIDE THE NEXT DECISION.
A good page doesn’t just explain. It leads somewhere. After the first understanding, the next step should feel clear - compare options, look deeper, get in touch, or move forward.
At its best, structure removes hesitation. It helps the user stay oriented, see what matters next, and continue without having to stop and figure it out alone.
Once the structure is clear, the interface needs a visual language of its own.
Typography, colour, spacing, imagery and components begin to work as one system - not as separate styling choices. The goal is consistency without sameness: enough rules to keep the experience coherent, and enough flexibility to let different moments feel distinct.
VISUAL SYSTEM
Rules Become The Interface.
SYSTEM IN PRACTICE
A design system is useful only when it holds together in real pages.
Type, colour, controls and components create a common base, but they should never dictate every composition.
The rules stay consistent. The content decides how they are used.
Designed to adapt across the experience
BUILT FOR FLEXIBILITY
A visual system has to work beyond a single screen. As the available space changes, layouts and components can reorganise while the hierarchy and character remain familiar.
Responsive design is not a smaller desktop. It is the same priorities rebuilt for a different space.
Movement should make an interface easier to understand, not simply more animated.
It can show what changed, respond to an action, guide attention or connect one state to the next. But motion only works when it feels right in use. I test timing, scroll and transitions in the browser, and when standard tools are not enough, I extend the behaviour with CSS, JavaScript and SVG.
03 / INTERACTION & IMPLEMENTATION
WHY IT MOVES
SYSTEM IN PRACTICE
/04
01
VISIBLE WHEN IT MATTERS.
The header stays available without staying in the way. It disappears as the page moves down, returns when the direction changes, and adjusts to the background behind it.
THE COMPLEXITY BELONGS BEHIND THE SCREEN. Research, wrong turns, testing, code, endless small adjustments - all of it is part of making the work. None of it should become part of using it. The person on the other side only meets the result. That, to me, is the point: the complexity is ours to solve, not theirs to carry.