M

Before we talk, let’s make sure we’re aligned

a

Patterns in the field

Designing for the decision, not the journey

By the time your best visitors get in touch, they have mostly already decided. Here is why building for the user journey misses them, and what it looks like to design for the decision instead.

Jessica Foord  •

Decisions  •

1 Jun 2026  •

2 mins

Think about the last time you chose someone for your business. An accountant, a supplier, whoever it was. By the time you actually got in touch, you had mostly already decided. You had looked around, read a little, narrowed it down, and the message you finally sent was less a beginning than a confirmation of something you had already worked out.

Your best visitors tend to arrive the same way.

For years the industry has built websites around the user journey. The path someone takes through a site, the story it tells, the flow from landing to enquiry. It is a useful idea, and it still holds for someone who genuinely does not know you yet. But by the time a high-intent visitor lands, the journey has usually already happened somewhere else. They have searched, compared, read something, sat with it, come back to it. They are not open and waiting to be led. They are near the end of deciding, looking for the one thing that tips them.

Those are two different visitors, and they need different things from the same page. One needs a narrative. The other needs an answer.

Most service sites are built for the first one. The architecture introduces, builds the case, takes someone somewhere, which is exactly right for a visitor with time to explore. But the person who has already half decided is not looking for an introduction. They are looking for the specific thing that settles the doubt still sitting with them, and when the page keeps making its case instead of answering it, they leave. Not because they were not serious. Because they were, and the page met them at the wrong point. The enquiry that was closest to happening is lost on the page least built to catch it.

The reframe is small, but it changes the questions you ask of a page. Less about where it takes someone, more about what it confirms for someone who is already almost there. Decision architecture, if you want a name for it.

It is a quick thing to check. Read your most important page as someone who has already been here once and come back. Does it still set out to introduce you, or does it answer the question that brought them back?

Now look at yours

What is your website telling you?

Behaviour like this shows up more often than most owners realise, and almost always unnoticed. The question worth asking is what your own site is doing right now. Ten questions, a few minutes, and you will see where it has fallen behind your business.

More from the field

One observation like this, once a month

Field notes on what real websites are telling their owners. What I noticed, what it revealed, what to do about it.