A better website starts with what happens next

A website has a job to do after it makes a good first impression.

Someone arrives with a question. They try to work out whether you can help. If the answer looks promising, they take a next step. Your team then has to pick up the conversation.

That whole path deserves attention. A new design can make your business easier to understand, but a beautiful page cannot answer an enquiry that never reaches the right person.

Before you write a website brief, walk through the experience as a customer. Start with an ordinary question they might bring. Leave your knowledge of the business out of it for a few minutes.

Start with the question on the other side of the screen

Your visitors may not know the name of the service they need. They might know that their booking process is confusing, that their team copies the same information between tools, or that their current website no longer explains the business clearly.

Use language that helps them recognize their situation. Explain what you do, who it helps, and what working together would involve. A visitor should not have to translate your internal service names before deciding whether to keep reading.

Try this: ask someone unfamiliar with your company to read one page, then describe what they think you do. The gaps in their answer are useful places to begin.

Give each page a clear next step

A service page can invite someone to describe a project. An article can point to a related explanation. A contact page can help someone choose between writing and calling.

The next step should follow naturally from what they have just read. A button labeled “Start a project” should lead to a place where they can actually start one.

Check the small details too. Is the form comfortable on a phone? Does it explain which information is optional? If something goes wrong, does the person know how to try again or contact you another way?

Follow the enquiry beyond the form

Submit a test enquiry with your own details and follow it all the way through.

• Can the visitor tell that their message was received?
• Does it reach the person responsible for answering it?
• Can that person understand the request without asking for everything again?
• Is there a clear owner for the next response?

This is where website work meets operations. Sometimes the useful next improvement is a clearer form. Sometimes it is a better handoff, a connection between existing tools, or an agreed process for the team.

Measure the action you actually care about

A visit to a form and a successfully received enquiry are different things. Decide what you want to understand before choosing what to measure.

Keep the measurement proportionate. Respect a visitor's analytics choice, avoid sending their personal information into analytics, and test the complete journey yourself. A dashboard is more useful when you know what its events represent.

Choose the next improvement from what you find

Write down the places where the journey becomes unclear or stops. Start with the one that prevents a useful conversation from happening.

You may need a new website. You may need to improve a few pages, simplify a handoff, or connect systems you already use. Walking the path first gives you a more useful brief for whichever work comes next.

That is what we want to explore in the Ethos Feed: practical ways to think about websites, growth, and the systems behind a business. Questions worth asking before the work begins, and details worth checking once it is live.

If you are working through one of those questions, tell us what you are trying to improve.