- By now, you're already sold on the idea of doing usability testing. However, there will most likely be other people in your company who aren't so sure. That's why if you want good job security, it's important to keep track of the changes that were implemented as a result of user testing. Even more importantly, you want to track how much money those changes potentially saved the company. It's hard for anyone in the organization to argue against a process that saves money and makes the product better.
Tracking this isn't too hard. You just have to extrapolate from your usability test findings to your whole user population. For instance, if you found that a usability fix saved an average of 10 minutes or a certain proportion of help desk calls, those figures have dollar values associated with them. Extrapolating to the whole user population and turning the figure into dollars per year is likely to yield some impressive statistics. It also helps if you have quotes from well-respected people in the development team saying how usability helped them.
And from important customers who have seen the benefits of usability testing in improvements in the product. The best thing to do is to seek out this information by asking people what benefits they've seen from usability testing. Archive that information away in a presentation deck that's always evolving. More recent, more awesome comments replace older remarks. Having the data in presentation format means you can quickly share it at a moment's notice. And you can easily copy and paste into your annual performance review or resume.
You might also find that this information is useful when the team needs to produce a business case for making changes to the product. Having quick access to the benefits you've gained from previous usability enhancements will help demonstrate that the team cares deeply about users and will be making the changes for the right reasons.
- What is usability testing?
- Finding the right participants
- Making a screener
- Asking the right questions
- Avoiding bias
- Making a task list
- Creating the test environment
- Running a pilot study
- Moderating sessions
- Capturing real-time observations
- Analyzing and reporting your results