Websites that help people decide

Start with the visitor’s decision

A visitor arrives with a question, even when they cannot yet describe it precisely. They may need to understand whether a service fits their situation, compare available options or ask for help. Before choosing a layout, write the decision your page should make easier in one sentence.

Then read the opening screen without the benefit of knowing your own business. Does it explain what you offer, who it is for and what someone can do next? A memorable visual identity can support that explanation. It cannot supply information the page never provides.

Make the next step predictable

A button sets an expectation. “Choose a time” suggests available appointments; “Request information” suggests a conversation that still needs a response. Use wording that matches what happens immediately after the click. Explain any remaining steps where the person makes the decision.

Give the main action a clear place in the page, while allowing people to explore first. A visitor who needs details should not have to contact you to learn basic scope. A visitor who is ready should not have to finish every section before acting.

An example: choosing a workshop

Consider an explicitly fictional community workshop offering introductory classes. Its first draft says “Discover your creative potential” above a gallery and a contact button. That expresses a mood, but someone still needs to know which classes welcome beginners, what to bring and how participation is confirmed.

A revised page could explain the class format, show a sample activity labeled as an illustration and answer those practical questions beside the relevant class. If the team must confirm availability manually, the action can say “Ask about this class.” The review question is concrete: can someone now describe the class and explain how to join without guessing?

Ask for information with a purpose

Look at each form field and ask why it is needed at this stage. If an answer belongs in a later conversation, consider postponing it. Tell people which fields are optional and what a successful submission means. Give them an opportunity to correct a mistake without starting again.

W3C’s form guidance explains that labels should identify the purpose of controls and be associated with them. A field should remain understandable after someone starts typing. Treat labels and instructions as part of the conversation, rather than decoration around an input.

Review the entire journey on a phone

Open the page on a narrow screen and complete a realistic task. Read the details, choose an option, enter information, correct an error and inspect the confirmation. Notice where you need to zoom, guess what an icon means or recover your position.

Also try keyboard navigation and the page with motion reduced. Ask another person to explain what they expect before pressing the main button. Their uncertainty is useful evidence about the page, not a failure to understand your design.

Define what a successful visit means

Decide what you want to learn before judging a redesign. Opening a form, sending a valid request and confirming participation are different events. A rise in clicks alone does not establish that people made better decisions.

Keep a short review list and work on one observed problem at a time. Record the question, the change and what you will check afterward. This turns a vague wish for a better website into a reviewable decision.

• Can a visitor explain the offer in their own words?
• Can they find the information needed to choose?
• Does the next action deliver what its label promises?