A prototype review is most useful when participants try to accomplish something. Give them a realistic scenario, such as finding the right service and preparing an enquiry, then observe where the interface supports or interrupts that task. Explain which parts of the prototype are functional.

A practical approach

Separate content problems from interaction problems. A visitor may understand where to click but lack enough information to decide. Record both the obstacle and the expected outcome so the next revision addresses the cause rather than only the visible symptom.

Your checklist

  • Prepare a small set of representative tasks.
  • Record hesitations and misunderstood labels.
  • Prioritise issues by their effect on completion.

For example

If reviewers repeatedly return to the homepage to locate pricing information, the issue may be missing cross-links or unclear labels. Adding decoration to the pricing section would not resolve that navigation problem.

Planning a project? Explore our website design or tell us what you need.