Return to Answer

I also recommend looking at this question What ways to conduct user research quickly and cheaply are there? for additional inputs

I also recommend looking at this question What ways to conduct user research quickly and cheaply are there? for additional inputs

I also recommend looking at this excellent article Five Techniques for Getting Buy-In for Usability Testing. To summarize the article

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.

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.

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.

However, time and time again, we find that design teams actually save time (and money) when they start testing at the beginning of a project. By finding usability problems very early on, teams prevent themselves from going in the wrong direction, leading to wasted time and resources.

The most successful teams have learned that the best way to create usable designs is to make informed decisions from the beginning of a project. They view testing as a technique to gather information to create great designs in a more timely and efficient way.

Involve Management and Stakeholders To get buy-in from team members and management, it’s essential to keep them involved. On every project, we suggest that stakeholders sit and observe at least one usability test. This will give team members the opportunity to observe first-hand the information gathered from tests.

Identify Your Organization’s Champions and Address Their Needs Finally, one of the best ways to get buy-in is to identify which members of your organization will benefit most from usability tests and recruit them as your Champions, assisting to rally other members of the organization

To briefly quote some of the points in the article

1. Use existing analytics. If you are redesigning a site or product, review all existing data on traffic patterns, errors, and any survey results since the product’s last launch. Get a sense for what is going right and what is going wrong with the existing product. Don’t expect a single point of contact on the client side to have all the information you need. Do the leg work and pull the data together.
2. Add the call center to your list of stakeholders to interview. If your client has a call center, interview the call center employees. Observe the call center at work if you can, even just an hour is great. The call center knows better than anyone else in the business what the user problems and perceptions are. When you interview stakeholders, ask them about analytics. Try to make questions open-ended so the answers can surprise you. Surprise is good.
3. Identify key scenarios. Once you’ve reviewed existing analytics and aggregated stakeholder requirements, you can begin to sketch out key user scenarios. Make sure these scenarios come with measures of success so you can plan to gather analytics for the next product launch. UX is cyclical – line up your next success early. Ground scenarios in the return on investment they can demonstrate.
4. Mock-up the concept by any means necessary. Sketches, HTML prototypes, iRise, Axure, comps; use whatever works for your timeline and your team to get the concept to a point that it can be shared. It’s better to get user feedback too early than too late.

To briefly quote some of the points in the article

1. Use existing analytics. If you are redesigning a site or product, review all existing data on traffic patterns, errors, and any survey results since the product’s last launch. Get a sense for what is going right and what is going wrong with the existing product. Don’t expect a single point of contact on the client side to have all the information you need. Do the leg work and pull the data together.
2. Add the call center to your list of stakeholders to interview. If your client has a call center, interview the call center employees. Observe the call center at work if you can, even just an hour is great. The call center knows better than anyone else in the business what the user problems and perceptions are. When you interview stakeholders, ask them about analytics. Try to make questions open-ended so the answers can surprise you. Surprise is good.
3. Identify key scenarios. Once you’ve reviewed existing analytics and aggregated stakeholder requirements, you can begin to sketch out key user scenarios. Make sure these scenarios come with measures of success so you can plan to gather analytics for the next product launch. UX is cyclical – line up your next success early. Ground scenarios in the return on investment they can demonstrate.
4. Mock-up the concept by any means necessary. Sketches, HTML prototypes, iRise, Axure, comps; use whatever works for your timeline and your team to get the concept to a point that it can be shared. It’s better to get user feedback too early than too late.

I also recommend looking at Hallway testing as a way to quick user evaluations and get an understanding of the challenges faced by the user base.

I also recommend looking at this question What ways to conduct user research quickly and cheaply are there? for additional inputs