A – Always.
B – Be.
T – Testing.
Always be testing. Always be testing!
Ok, ok, it’s not as riveting as Alec Baldwin’s speech in Glengarry Glen Ross, but you get the idea.
Test early — test often
User testing is not something to do right before you launch your web site.
You want to test early and test often. Usability testing lets the design and development teams identify problems before they become part of the design of the site.
The earlier problems are found and solved, the less expensive the fixes are. As the project progresses, it becomes more difficult and expensive to make major design changes. The more you test and change based on what you learn, the more confident you are that the site will meet your objectives and your users’ needs when it is launched.
You can test a sketch on a cocktail napkin
Remember, you don’t need a fully functioning site to start user testing. You should be testing prototypes from early paper-based stages through fully functional sites.
In fact, I find that you get better, more critical feedback from low-fidelity prototypes. Users don’t feel “bad” criticizing paper prototypes because there has been no development work. Most users feel uncomfortable criticizing a fully functioning site because of all the work you have obviously put into it. By testing early and often you can get more and better feedback as you test each stage of the prototype.
By moving from paper (low-fidelity) to wireframes (medium-fidelity) to fully functioning sites (high-fidelity), you will have tested users throughout the process, so there shouldn’t be major changes to the site as you close in on your development deadline.
This process of iterating — developing a prototype, testing it with users, analyzing the test results, changing the prototype based on the findings, and then repeating the cycle — is the best way to produce a successful web site.

Entries (RSS)