Usability testing is the final type of user research to consider in our effort to help you identify the potential of an ROI for user research. This occurs when the product or website is close to complete but not yet launched, and the purpose is to identify ways the experience can be refined.
This post is part of a series on calculating the ROI of user research!
In order to conduct Usability Testing, you’ll need to have a coded version of your solution on (at least) a staging environment. It does not have to be completely finished and ready to be pushed to production, but should be most of the way there. A set of tasks will need to be constructed that will be given to testing participants to complete (with little to no context or help).
If possible, conduct Usability Tests in a realistic user setting so that realistic reactions to distractions and/or steps in the journey that take place outside of your solution can be observed. This ensures that the solution will work in the right context and environment, post-launch.
Insights on how to make your solution more intuitive is the key recompense for Usability Testing. At this point, the core project team has been working closely with the product for months and it takes someone who isn’t familiar with the solution to properly test drive it. If Concept Validation research took place, the insights from Usability Testing should be much smaller and easier to implement. It can also begin to inform what the v2.0 roadmap might need to include.
The biggest factor when deciding to include Usability Testing is the size of the launch plan. If the audience, brand, and budget of the launch is going to be considerable, it is wise to take this extra step to de-risk that launch. Usability Testing can also be helpful when testing new interaction models or when the solution is for a target user segment with lower than average technical skills.
If the product or website is going to have a soft launch as opposed to a big splash, it may not be necessary to invest the effort in usability testing, however it is important to have an agile team on standby to react to the needs of users in the soft launch. Likewise, if the solution design is free of complexities (basic functionality only) and using best practices (not attempting to forge any new design interactions), there will be less to gain from a formal Usability Test.
The last option to explore is doing no user research at all. This is usually not an intentional decision made at the forefront of a project but can be a byproduct of shifting project scope and timelines.
Moving faster. Not having to use budget, timeline, and resources for the task of User Testing. But is it really worth the risk?
With speed to market you also increase risk. The risk lies in not reaching desired goals after your product team has spent a great deal of time and effort to bring the product to market. And this can be a very costly mistake.
We’ve seen projects that started with well-polished pitch decks including strong, third-party market research but the product team never took the time to talk to potential users. As a result the solution missed key assumptions and fell (sometimes radically) short of the expected KPIs. In the grand scope of scenarios like this I’m sure the product teams would sacrifice a week here or there to get input throughout the product development process.
Projects with zero to little risk can afford to forgo all user research. This would include brochure websites and basic blogs.
Most of the time you’ll want to consider at least one form of user research. It helps product teams look at their solutions from many different angles and ultimately makes them stronger because they learn how to adapt.
User research might not need to be conducted at every interval of every project but, there is certainly value in taking the time to pause at least once to collect user feedback. The key is understanding which type of user research will return the most value to your project.
Here are a few more tips to reduce the cost of conducting user research.
For more on user research and all things related to creating and developing successful applications that prioritize the end-user, be sure to follow the ADK blog!
Learn more on how ADK applies the rules of User Research: https://www.adkgroup.com/blog/user-testing-best-practices/