Skip to content

OtherUpdated 2 min read

Remote website reviews: turn a call into clear decisions

Everyone watches the same page while discussing different things. One person judges colour, another reads the copy and a third asks about form delivery. The call produces many comments but no clear decision or agreed version.

A remote review starts before screen sharing. Define the questions that need answers. Keep the scope concrete, such as the route from product selection to enquiry, rather than asking people to assess the entire website at once.

Give everyone the same starting point

Share the relevant address and explain what is ready or temporary. Do not present a mockup as a working site. For a test site, check participant access before the meeting.

Retain the address and version with the decisions. The W3C guidance on stable addresses emphasises preserving useful links. A review record also needs a meaningful destination, without silently replacing the discussed version with something different.

A participant takes notes during a remote website review
Connect observations during a review to concrete decisions and responsibility.

Complete a task as well as giving an impression

Ask someone to find a service, understand its conditions and submit a test enquiry. Watching a demonstration cannot replace actual use. A large desktop screen share can conceal phone problems.

Separate the observation from a proposed solution. “I could not find the button” identifies a symptom; “make it red” proposes one possible response. Agree what should improve and why first.

Turn the review into a decision record
A practical remote website-review workflow. An illustrative planning example.

Record decisions in one place

Connect each agreement to its page, owner and acceptance check. Do not hand conflicting comments to a developer as an unresolved list. Identify the decision-maker and questions that still need evidence.

  • Send the address, version and specific review purpose.
  • Complete a customer task and inspect the phone view.
  • Record the observation, agreed change and owner.
  • Separate unresolved questions from decisions.
  • Verify the changed result using the same task.

The useful outcome of a design review is a shared agreement. After the call, the team should understand both the work and how its improvement will be verified.

More articles