I'm preparing to launch a fairly large website with several features and workflows. As the sole developer, I'm concerned that I've become too familiar with how everything is supposed to work and may be overlooking usability problems. Friends have checked parts of it, but I'm wondering whether to hire an independent tester to review the functionality, different usage scenarios, and overall user experience. Is professional testing worthwhile, or would a structured self-testing process and feedback from a few unbiased users be enough?
4 Answers
For UX, get people who have never seen the site to perform a few realistic tasks while you stay quiet and take notes. Give them goals rather than instructions, such as finding a particular product or reaching the point where they would pay. Hesitations and unexpected clicks usually reveal more than simply asking whether they like the site. Friends who already understand the project tend to fill in gaps automatically.
Treat functionality and UX as two separate testing jobs. Your own checklist and automated tests should confirm that the system behaves consistently, while unfamiliar users should test whether the interface makes sense without explanation. A product owner or developer may follow the intended workflow too closely, so outside eyes are valuable even if you don’t hire a dedicated QA company.
An independent tester is especially worthwhile when the site handles payments, sensitive information, or a complicated multi-step process. They can provide an unbiased usability review and may catch accessibility, security, or mobile issues that a developer is likely to miss. For a lower-risk project, a focused usability session may provide most of the benefit at a much lower cost.
The type of risk matters more than the site’s page count. A small checkout flow can deserve more testing than a large collection of mostly informational pages.
You probably don’t need a full third-party QA engagement for an ordinary site. Create a repeatable checklist for the important workflows and run it before every release. Include forms and email delivery, broken links, mobile layouts, multiple browsers, analytics, error handling, and slow or unreliable connections. Automated end-to-end tests are useful for the core paths, while exploratory testing is better for discovering odd edge cases.
A short session with three unfamiliar users can uncover a surprising amount, especially if you record the screen and ask them to think aloud.