- What is SharePoint 2010? Vision and Reality
view comments - Myths & Realities of Drupal
view comments - Knowledge Management in 2012? Probably Dead
view comments - iPad 3 vs. New Samsung Tablet: War Starts in February
view comments - iPad 3 to be Unveiled by Apple in Early March
view comments - 5 Signs Your Company Doesn't Get Social Business
view comments - 5 Critical Steps to SharePoint Information Architecture Planning
view comments - Knowledge Management Meets Social Business: KM is Dead, Long Live KM!
view comments
5 Techniques for Getting Buy In for Usability Testing
For more than seven years, I’ve been teaching and coaching design teams on how to conduct usability tests and gather user feedback early on in the development process. One of the questions that comes up time and time again from clients is, "How can we get buy-in for usability tests from management and other team members?"
Through our own research at UIE, and in our ongoing discussions with expert usability practitioners, we’ve identified several proven techniques for getting stakeholders onboard.
1. Start Testing Right Away
Start testing. Start doing it right away. We’ve found there isn’t any one experience more beneficial to design teams than running a usability test. I’m still amazed by how quickly development team members recognize the benefits of usability testing once they’ve actually seen it in action.
When I’m teaching courses on usability testing, I’ve found that no amount of lecturing about the benefits of testing gets development teams onboard and past their skepticism. Instead, people only truly comprehend the power of testing once they’ve observed a user interacting with a design.
If you’re struggling to communicate the value of testing to your management or fellow team members, stop explaining the benefits and start demonstrating them. I’ve yet to see a test where the design team fails to gather some new piece of valuable information about the users’ needs.
When development teams start watching users interact with their designs, they’ll typically see two possible outcomes, both positive. In some instances, usability tests confirm the team’s existing beliefs about how users will use their products. But, in the much more common outcome, teams observe users experiencing problems with the design and identify gaping holes in their assumptions.
2. Debunk the Myth that Usability Testing Is a Big Production
One of the biggest obstacles design teams face when trying to sell testing is the perception that usability tests need to be a huge production.
The best way to tackle this resistance is by debunking the myth that testing has to be a big deal. Usability testing isn’t rocket science. The organizations that do the best job of incorporating usability tests into their existing process understand that testing is not a big deal.
The best organizations make usability testing a part of their everyday culture. To convince management that testing doesn’t need to be a huge production, we recommend design teams start simple. You can start by testing 3-5 users and disseminate that information throughout your organization.
Other experts agree. In an interview I conducted in 2002 with Rolf Molich, one of the world’s most respected usability practitioners, Rolf suggests:
“If your goal is to “sell” usability in your organization, then I believe 3-4 users will be sufficient. Much more important than the number of users is the sensible involvement of your project team in the test process and proper consensus-building after the test.”
Many teams are resistant to usability testing because of the belief that they need to spend money on state-of-the-art usability labs, or they are concerned they won’t find the right users. Again, our recommendation is to start simple: Test on a computer in your office cubicle and start testing with someone, even a co-worker, to begin gathering data. A usability test doesn’t need to be perfect. It just needs to happen.
3. Start Testing Early in the Process.
Many organizations are concerned that testing will disrupt project timelines because it may necessitate major design changes before launch.
Continue reading this article:
Featured Events View all
| Add event
|
RSS
- Feb 22, 2012 – Intelligent Content Palm Springs 2012
- Feb 26, 2012 – SPTechCon - Sharepoint Conference San Francisco 2012
- Feb 28, 2012 – (Webinar) How to Build Great Mobile Websites
- Mar 6, 2012 – Get Social with Microsoft & Telligent in Dallas
- Mar 8, 2012 – Get Social with Microsoft & Telligent in New York
Who's Hiring? View all
| Post a job
|
RSS
- Web Content Manager in Newport Beach at Orange County Museum of Art
- Principal Business Consultant in Paris at Saba
- Director of Customer Success Management in Nova Scotia at Radian6
- Software Engineer -- Media Solutions in Bucharest at Adobe
- Technical Writer in Charleston at Blackbaud
- Interaction Designer in Maryland at Inmedius
- Project Manager in London at Brandworkz
- Sales Director, Consumer Electronics at Synacor

Receive
the Free CMSWire Newsletter
Email It