Loading
Loading
Our way of thinking
Most websites are designed around what the business wants to say. We design around what the customer is trying to do.
About 7 minutes
The short version
When somebody lands on your website they are usually not there to browse. They are there to finish a very simple journey. Find you, work out what you do, decide whether they trust you, and act.
On a phone that journey is often much harder than it should be. Not because the information is missing. Because the experience gets in the way of it.
A website can be “mobile responsive” and still fail the moment somebody tries to use it.
A fast, intent-driven tap. A search result. A recommendation.
A link somebody has just been sent and opened straight away.
In that moment they are not exploring. They are moving with purpose, and they expect the website to keep up. Instead they land on something that technically fits the screen but does not support the way they are trying to move through it.
And in that moment something subtle breaks, which is trust. Not because the business is not credible. Because the experience does not feel aligned with the intent that brought them there.
They do not think
“This is badly designed.”
They think
“This doesn't feel like what I just tapped.”
Every visit runs on two levels at the same time. Design one without the other and the site works in a demonstration and fails in a car park.
The experience layer
ReachTapFlow
What their hands are doing, on the phone, right now.
The decision layer
FindUnderstandTrustAct
What is going on in their head while they do it.
These are not two competing frameworks. They are the same journey seen from two angles, and each step in the first one produces a step in the second.
ReachFind
If people cannot easily reach what matters, they cannot find it.
TapUnderstand
If interacting is difficult, understanding breaks down with it.
FlowTrustAct
If the journey feels smooth and deliberate, trust builds, and acting becomes the natural next thing.
On a phone nobody experiences your website as pages anyway. They experience it as a sequence of taps.
None of these is a score and none of them is a setting. They are seven questions we ask of a page, and the answer to every one of them is something you can check yourself by using your own site the way a customer would.
01 of 7
Can they get to what matters quickly?
When somebody lands on your site, not everything on it is equal. A few actions matter far more than the rest.
Call. Book. Get a quote. See the work. Get in touch.
Those should not sit behind three layers of navigation or halfway down a page. Reach is about making the important actions naturally available at the moment they are wanted.
Not forcing attention on them. Not piling on choice. Just making sure the right path is always within easy reach.
Because if something important is hard to reach, it becomes easy to ignore.
02 of 7
Can they interact without any friction?
A mouse gives you precision. A finger does not, and that single difference changes everything. Small targets, tight spacing and overloaded screens all produce the same two results: hesitation, and mistakes.
So we design for the way a hand actually works on a phone:
The goal is not to make things bigger. It is to make using them feel effortless, because every moment of friction interrupts the momentum somebody arrived with.
03 of 7
Can they move forward without thinking about the website?
Flow is continuity. From the first impression to the final action, nobody should feel like they have hit a dead end or taken a wrong turn.
We look at the whole thing as one path, and we ask three questions of it.
Good flow removes the effort of deciding. It makes the next step feel obvious, not because it is pushed, but because everything before it led there.
04 of 7
Do they know what matters right now?
Most mobile websites fail by trying to show everything at once. Every service, every message, every option competing on equal terms.
Focus is clarity of priority. At each point in the journey somebody should only be asked to take in what matters at that point.
We do not remove information. We organise it around the decision, because clarity is what allows movement.
05 of 7
Does the site keep up with the intent they arrived with?
Speed is not only a technical score. It is psychological momentum. When somebody taps a result they expect it to carry straight on, and if they wait, hesitate or stall, the intent drains out of the visit.
So we build for immediacy. Fast loading, light interactions, no unnecessary delay, and nothing that drags visually or technically.
Because nobody experiences load time. They experience an interruption, and an interruption breaks flow.
06 of 7
Does their confidence build as they move?
Before somebody acts they need certainty. Not total conviction. Just enough confidence to take the next step.
That comes from a clear explanation of what you do, visible proof of the work, other people vouching for you, consistent messaging and no ambiguity anywhere. But the part most websites get wrong is not the proof. It is the timing.
So reassurance goes exactly where somebody needs it, rather than buried on a page they may or may not find.
Trust is not a page. It is a feeling that builds through the journey.
07 of 7
Is taking action the easiest part of the whole thing?
At some point somebody is ready. Call, enquire, book, request, get in touch.
The job of the website in that moment is not to persuade harder. It is to take the friction out of the decision.
Every other part of this list is preparation for this one moment. It should be the shortest part of the whole visit.
A fast site does not fix unclear messaging. A strong button does not fix a broken journey. Good-looking design does not fix a lack of trust.
Which is why this is not a checklist. It is one system of movement and decision, describing how somebody gets from the first tap to the final action.
That difference is the whole thing. What matters is whether the experience holds up in the moment somebody actually uses it, one handed, in a hurry, on whatever signal they happen to have.
We do not design layouts.
We design decisions.
We do not design pages.
We design movement.Nothing here is assumed. We watch how people behave, we design around it, and we keep refining it until the experience feels invisible, because nothing is getting in the way.
Next