![Illustration depicting the UX design research process with interconnected elements](/sites/default/files/usertestingv3/styles/medium/public/2023-01/ILLUST-2022-ux-design-research-2616x1622.png.webp)
One of the most important tools in a designer’s toolbox is feedback. Design teams make critiquing work and gathering input from colleagues and peers a regular part of their creative process. Most designers wouldn’t dream of launching a design without first getting feedback from their peers. In fact, according to UserTesting’s annual CX Industry Report, 77% of designers report that they should get user feedback before launching any new or updated design. Yet when asked how often various experiences were tested with users, designers reported that only a few were being tested on a regular basis. This leads to less confident design decisions, not to mention running the risk of launching designs that don’t resonate with users. User feedback—at every stage of the design process—is a designer’s best strategy to create with confidence.
In this guide, we’ll share real-life examples of how teams rely on user feedback to guide their decisions and tips on how to use two common methods of remote user feedback—self-guided tests and user interviews—so you can start gathering insights on your next design project.
This guide is organized with tips and examples so that you understand how and why to test during:
During the discovery phase, you want to gain a better understanding of your customers, their needs, and frustrations. This can entail identifying and getting to know different personas or understanding high-level pain points. At this stage, you may not have a design idea or an endpoint in mind. You’re at a starting stage and in search of clarity on areas of opportunity. This is also a great opportunity to get feedback on initial concept ideas before moving forward with any designs.
While it’s better to do a live interview for the discovery phase (it offers the opportunity to ask follow-up questions or pursue new areas and topics as the conversation evolves), if you’re short on time you can also gather high-level information using self-guided tests.
Here’s an example of a test plan you could create:
Task: Go to the URL for a brand that you would visit to complete {activity X}.
Task: Explain why you selected that brand.
Task: Tell us about the last time you completed {activity X}.
Task: Now show us how you did that.
Conduct an open-ended interview on any topic, including:
Feeling inspired? Try a needs and frustrations discovery template to identify opportunities to improve customer experiences or activities.
![]() AutotraderThe Autotrader team wanted to better understand the car buying experience. Notes Bradley Miller, Senior User Experience Researcher at Autotrader.com, “There was an institutional perspective about the kind of influence third-party automotive classifieds sites like Autotrader have on car shoppers, and therefore, we developed products and experiences around that perspective.” After conducting interviews using Live Conversation, the team discovered that the process of buying a car online resembled standard digital behavior: it all starts with a search engine. “Buying a car isn’t a new or different circumstance. It’s just another problem people have. People have questions, so they turn to Google or another search engine to get an answer. Adds Miller, “I learned that we need to meet consumers where they are. They don’t necessarily seek out a site like Autotrader; rather, they’re more likely to stumble into us from a search result. “Realizing that they are starting with a search engine and could be dropped onto any page of our site challenges the notion that car buying follows a set sequential process. This is important because when we're designing pages, we have to ensure that each part of the experience draws them further into the website. We can’t assume they’ve been on other webpages and have greater context.”
View customer story |
When you have some early sketches or designs, it’s important to get feedback to validate them before investing resources to build them out. Does the design make sense? Is it clear and intuitive to the user? And if you find out that something in your early designs is really problematic, you can change it and then test again to see if it’s a better experience before proceeding to development or production.
User feedback is also a great way to settle internal design disputes. If you find that your team can’t agree on a specific design the fastest, easiest way to choose confidently is to ask your users what they think. You can even have test participants evaluate multiple designs in a single session, enabling you to continue to iterate on your design direction until you have something everyone can agree on—especially your users.
You can test wireframes using either remote feedback method. However, there are some factors to consider that will help you choose the best method. Before conducting your test, ask yourself:
Self-guided tests are best if you know users will be able to interact with your design without much guidance or explanation and if you have an easy way to share your design.
Live interviews are best if you want to ensure your designs are only shared with the test participant during the duration of the test. They’re also more effective if you think a test participant may get confused about a prototype or design (you can still do this via a self-guided test, just be sure to be very clear in your instructions and anticipate any questions or areas needing additional explanation.
If you want to ensure your designs are only shared with the test participant during the test, you should share your screen during a Live Conversation session or use UserTesting’s secure prototype hosting during an unmoderated test. If you think a test participant may get confused about a prototype or designs, you should present them during a Live Conversation session or be very clear in your instructions if running a self-guided test.
Provide a link to your design (such as from a third-party design tool or a third-party hosting solution) to get feedback about early design ideas. Learn more about sharing options.
You can also upload an image or prototype to UserTesting’s secure prototype hosting. Your designs will only display during the test. Learn more about secure prototype hosting.
It’s common for test participants to mistake prototypes (especially high-fidelity ones) for live sites or apps. Make it clear in the task directions that this is a prototype with elements that the test participant can’t select. They should speak out loud about what they would do if they encountered the webpage or app.
Share prototypes during the live session to maintain control over your designs while getting feedback. Learn more about sharing your screen in our Help Center.
As with interviews conducted during the discovery phase, the flexible and dynamic interaction gives you an unrestricted opportunity to gain insights. This helps you to radically reimagine and redesign your product before any development begins.
This is also a good option if you have more complex designs that might be confusing if presented during a self-guided, unmoderated test. Presenting your designs during a live session offers you the best of both worlds. It gives you control over when, where, and with whom your designs are shared. It also allows you to guide test participants if they encounter challenges.
Feeling inspired? Try a prototyping template to observe users interacting with a pre-production experience here.
![]() Pediatric health systemThe largest pediatric health system in a major US metropolis wanted to update its website and apps—hubs of critical information that helped to attract prospective patients and kept current patients healthy and informed. Given the great scale of the project, and inversely the size of the lean team, they sought to rebuild the website template by template. Using this approach, they could create optimized designs that could then be applied across all relevant webpages—for rapid change at scale as well as consistency throughout the digital experience. Starting with the template used on department and program pages of the website, the team gathered feedback to figure out what was working, what wasn’t, what people liked, and what needed to change. The team asked questions like, “Do we have the right information there? And of the information that is there, is it in the right order?’” Using these insights, the team created a wireframe of a potential new design. They then sought feedback on the revised wireframe as well. The digital marketing lead shares, “We cut the wireframe up and then had people change the order of the parts according to their preferences—sort of like having them build their optimal page. We then created a design based on the most popular order and again asked people to assess whether this new version provided all of the information that they needed.”
|
Get feedback as you reach each milestone to ensure that you end up where you planned. And if feedback indicates there’s a problem or something that requires attention, you have the opportunity to fix these issues before proceeding to the next milestone. Studies show that problems that are discovered and fixed after a product release have 100x the cost compared to when issues are identified and addressed while in development.
It’s also worth noting that many things are happening in tandem as a product or experience is readied for launch. This is around the time that marketing and other GTM teams are preparing their campaigns and other promotional assets. These GTM projects also benefit from customer feedback to ensure that the messaging and promotional activities line up product capabilities with customer needs and preferences.
Share a link (plus any necessary login information) for test participants to access your staging environment so you can see how they attempt to accomplish tasks using the product at that point.
You can also upload an image to UserTesting to get feedback on imagery or even ads prior to launch. Learn more about image hosting.
Conduct a live feedback session and share your desktop or mobile screen to show the new product in a staged environment. Bonus: Give the test participant mouse/ keyboard control to give them more “free reign” as they interact with the experience. Learn more about screen sharing during an interview.
Feeling inspired? Try a multichannel journey template to understand how customers engage with your brand or products across multiple touchpoints.
![]() Code for AmericaWhile developing ClientComm, a web app that allows probation officers (POs) to exchange text messages with their clients from their computer, tablet, or mobile device, the Code for America team ran unmoderated tests to understand the needs of the product’s two user types. “We have users with a wide range of digital literacy, and we wanted to be sure we covered everyone’s needs,” notes Rachel Edelman, Product Designer at Code for America. “Our customers (POs) operate in a world where fax machines, phone calls, and personal meetings are the main modes of communication. Many have legitimate fears about their ability to adopt new technology. Being able to do usability testing and ensure we were upholding our mandate to provide intuitive, helpful solutions was very important.” Adds Edelman, “We just wanted to make sure that people can complete the tasks they need to do in order to do their jobs.” And by using unmoderated testing and the UserTesting contributor network, the team was able to locate the types of audiences they were seeking and quickly receive feedback to support the team’s busy schedule and resource constraints. “There’s only so much we can travel. It’s amazing that I can sit in my office and set up a UserTesting study and get all the results back within 30 minutes,” notes Edelman. “That’s about the amount of time it would take me to take a cab to the airport. It’s an amazing time saver.”
View customer story |
Even after a new design has launched, it’s important to continue monitoring to address problems or to keep evolving the experience to keep up with experience best practices and user expectations. For example, your team may wonder, “Why are people dropping off at this stage in the workflow?” You can understand why this is happening by gathering qualitative insights and using that feedback to continuously inform your design updates.
Qualitative insights are great when paired with analytics or quantitative metrics you may be tracking already. Together, they provide a fuller understanding of the why behind user behaviors.
Identify areas where you want a fuller understanding of how customers are interacting with or perceiving products, experiences, or messaging. They can include:
Identify areas where you want to get more insight and have a dialogue with customers about those sections in particular.
Understand how well the new release is meeting customer needs and uncover new wants and needs.
Another idea: Have users show how they’re actually using the design that was released (and compare this to what you learned during Discovery!)
Feeling inspired? Try a landing page conversions template to optimize conversions with insights about what motivates your customers.
![]() Adobe PhotoshopIn its efforts to continually improve upon Photoshop, the perennial graphics editing software favored by design experts and novices alike, the Adobe team set out to launch an image extraction feature frequently requested by users. However, usage data following the launch as well as posts on user forums revealed that customers were confused and struggling to use the new feature. The excitement of releasing the high-priority feature wore off as the team realized they had to make some major revisions. The Photoshop team turned to UserTesting, using the on-demand contributor network to connect with new Photoshop users representing a wide variety of skills and levels of expertise. Based on the feedback, they made a number of updates, including giving the feature a clearer name, better interface, and menu navigation. Doing so helped them launch an improved experience that is helpful and easy to use for the wider spectrum of users. View customer story |
Finally, it’s worth mentioning that while the steps of product development or any project plan are often presented as linear, in reality, inspiration and challenges can crop up anywhere and at any stage. It’s rare for a team to follow the process from start to finish.
If in the course of development, you get feedback that creates the opportunity to pivot and change direction or creates an offshoot project for another team to pursue, these are moments to regroup and decide how to proceed. The point is this: let feedback from your users be your guiding light—your proverbial North Star—to ensure that all the work, time, and other resources you put into creating newer and better experiences line up with what your users want.