Your Staff Know the Website Too Well to Test a First Visit

Ask a colleague to find the enquiry page on a website they helped build, and they may go straight to it. They remember the menu label, the design discussion and the route used during earlier checks. A person visiting for the first time arrives without that history.

That difference matters when you want to understand whether a website explains itself. Familiarity can help staff move past a label or missing explanation that would make a new visitor pause.

Internal checks remain useful for finding broken links, incorrect details and faults in a known process. To examine a first visit, give someone unfamiliar with the site a realistic task and watch how they approach it before explaining the intended route.

Notice what familiarity supplies

Someone who works with the website may know that a package name refers to updating an existing site. They may remember that a useful explanation sits near the bottom of a particular page. They can use that knowledge even when the page gives a new reader little reason to look there.

A colleague who has never seen the site may bring a fresher view. The relevant issue is the knowledge a person already carries into the task. Before treating a quick internal check as evidence about new visitors, consider how much of the route the person already knows.

Use the team’s knowledge to choose a useful question. Then observe whether the information visible on the website helps an unfamiliar person answer it.

Choose one task with a clear purpose

Begin with a practical question about the first visit. For example: can someone work out whether the business can help with an existing website and find a way to ask about it?

The GOV.UK guidance on moderated usability testing describes watching people attempt specific tasks. It recommends relevant, believable tasks with a clear goal and instructions that avoid giving away the route. That is a useful starting point for planning this kind of observation.

Choose someone whose situation makes the task meaningful and who does not already know the website. Explain the purpose of the session and agree what you will observe and record. For an enquiry task, use prepared example details and stop before sending a real request.

Give the goal without the navigation instructions

Here is a task for an illustrative session on a fictional agency website. It is a proposed exercise, rather than a report of research carried out for a client.

Your business already has a website, but some pages no longer explain what you offer. You want help improving what is there. Starting from the home page, find how you would check whether this provider can help and ask them about it. Stop before sending an enquiry.

The task gives the person a reason to use the website. It leaves them to decide which information and contact route would help. Giving them the names of the menu items to open would change what you are observing.

Prepare the starting page and the task wording in advance. If the person asks what the task means, clarify the situation in ordinary language while leaving the website choices to them.

Leave room for the person to choose

Once the task begins, give the person time to read and act. You can invite them to describe what they are looking for and what they expect a link to contain. This can make an otherwise silent pause easier to understand.

The person observing may feel an urge to point at the right menu or explain a service label. Nielsen Norman Group’s introduction to usability testing highlights the facilitator’s responsibility to collect useful information while avoiding accidental influence on the participant’s behaviour.

If the person becomes stuck and you help them continue, note where that help was needed. The rest of the session can still provide useful observations. Keep the assistance visible in your account of how they reached the next page.

A question such as “What were you expecting to find there?” can help you understand an action already taken. Avoid turning the session into a demonstration of how the team intended the website to work.

Follow the route and the moments of uncertainty

In our fictional session, imagine that the participant opens the company background page first. They are looking for evidence that the agency works with businesses like theirs. They return to the home page, open a package description and ask whether they would need a completely new website.

The observer then points out a contact link further down the page. The participant reaches the enquiry form and explains the question they would send. The route includes a point where the observer supplied information.

A useful note could say: “The participant asked whether the package required a new website. They reached the enquiry form after the observer pointed out the contact link.” These events are invented to illustrate a record, not presented as real customer feedback.

That note gives the team something specific to investigate. Where does the page explain which existing projects the service can cover? How is the relevant contact route introduced? The team can review those parts of the page against the question the person was trying to answer.

The observation does not establish that everyone would take the same route. It shows a possible difficulty and the context in which it occurred. Preserve that context when deciding what to examine next.

Keep the conclusion proportionate to the observation

One session can give you a concrete question to investigate. It cannot tell you what percentage of all visitors experience that difficulty or how much revenue a wording change would produce.

The team might decide to make the service’s relevance to existing websites clearer, then observe another unfamiliar person attempting the same task. Write down what changed so the next discussion has a clear reference.

Someone who has already completed the exercise now knows more about the website. A later session with that person may help examine returning use, but it brings different prior knowledge from the first visit.

Staff can contribute their understanding of the business, the service and the work the site needs to support. An unfamiliar visitor can reveal which parts of that understanding the page itself makes available. Watching one realistic task gives those two perspectives a useful place to meet.

I work in marketing at Salestudia, an agency working with businesses in Germany. Forms, buttons and contact options are part of landing page development at Salestudia. A task for a first visit is one way to examine whether that page structure makes sense to a new reader.

This article was drafted with AI assistance. The cover image was generated with AI.