Fresh eyes testing is asking someone unfamiliar with a change to look at it without instructions on what to test. It counters the familiarity that builds up when testers work on the same product for a long time.
Why it matters: People close to a product stop seeing obvious problems. A newcomer, given no direction, notices what everyone else has learned to overlook.
In practice: Teams invite colleagues from other teams, support staff, product managers or marketing to use a feature freely before release. The key is not telling them what to test, so their attention isn't shaped by the team's assumptions.
Examples:
- Asking a colleague from another team to use a redesigned page for ten minutes before launch.
- Inviting customer support staff to explore a feature freely, rather than only verifying fixes.
Common pitfalls:
- Giving fresh eyes a script, which brings back the team's blind spots.
- Using the same people every time, until their eyes aren't fresh any more.
Why do testers miss obvious bugs? Familiarity. After weeks with a product, people see what they expect to see. Fresh eyes, breaks and changing how you look at a product all help.
