User Experience Feedback Collection During Testing

Too many product teams believe meaningful user research has to involve long interviews, Zoom calls, and endless scheduling and note-taking. But honestly? You can get most of what you need without all that hassle. 🙅♂️ I’ve conducted hundreds of live user research conversations in early-stage startups to inform product decisions, and over the years my thinking has evolved on the role of synchronous time. While there’s a place for real-time convos, I’ve found async tools like Loom often uncover sharper insights—faster—when used intentionally. 🚀 Let’s break down the ROI of shifting to async. If you want to interview 5 people for 30 minutes each, that’s 150 minutes of calls—but because two people are on the call (you and the participant), you’re really spending 300 minutes of combined time. Now, let’s say you record a 3-minute Loom with a few focused questions, send it to those same 5 people, and they each take 5 minutes to write their feedback. That’s 8 minutes per person and just 5 minutes once for you. 45 total minutes versus 300. That’s an order-of-magnitude reduction in time to get hyper-focused feedback. 🕒🔍 Just record a quick Loom, pair it with 1-3 specific questions designed to mitigate key risks, and send it to the right people. This async, scrappy approach gathers real feedback throughout the entire product lifecycle (problem validation, solution exploration, or post-launch feedback) without wasting your users' time or yours. Quick example: Imagine your team is torn between an opinionated implementation of a feature vs. a flexible/customizable one. If you walk through both in a quick Loom and ask five target users which they prefer and why, you’ll get a solid read on your overall user base’s mental model. No need for endless scheduling or drawn-out Zoom calls—just actionable feedback in minutes. 🎯 As an added benefit: this approach also allows you to go back to users for more frequent feedback because you're asking for less of their team with each interaction. 🍪 Note that if you haven’t yet established rapport with the users you’re sending the Looms to, it’s a good idea to introduce yourself at the start in a friendly, personal way. Plus, always make sure to express genuine appreciation and gratitude in the video—it goes a long way in building a connection and getting thoughtful responses. 🙏 Now, don’t get me wrong—there’s still a place for synchronous research, especially in early discovery calls when it’s unclear exactly which problem or solution to focus on. Those calls are critical for diving deeper. But once you have a clear hypothesis and need targeted feedback, async tools can drastically reduce the time burden while keeping the signal strong. 💡 Whether it’s problem validation, solution validation, or post-launch feedback, async research tools can get you actionable insights at every stage for a fraction of the time investment.

User research is great, but what if you do not have the time or budget for it........ In an ideal world, you would test and validate every design decision. But, that is not always the reality. Sometimes you do not have the time, access, or budget to run full research studies. So how do you bridge the gap between guessing and making informed decisions? These are some of my favorites: 1️⃣ Analyze drop-off points: Where users abandon a flow tells you a lot. Are they getting stuck on an input field? Hesitating at the payment step? Running into bugs? These patterns reveal key problem areas. 2️⃣ Identify high-friction areas: Where users spend the most time can be good or bad. If a simple action is taking too long, that might signal confusion or inefficiency in the flow. 3️⃣ Watch real user behavior: Tools like Hotjar | by Contentsquare or PostHog let you record user sessions and see how people actually interact with your product. This exposes where users struggle in real time. 4️⃣ Talk to customer support: They hear customer frustrations daily. What are the most common complaints? What issues keep coming up? This feedback is gold for improving UX. 5️⃣ Leverage account managers: They are constantly talking to customers and solving their pain points, often without looping in the product team. Ask them what they are hearing. They will gladly share everything. 6️⃣ Use survey data: A simple Google Forms, Typeform, or Tally survey can collect direct feedback on user experience and pain points. 6️⃣ Reference industry leaders: Look at existing apps or products with similar features to what you are designing. Use them as inspiration to simplify your design decisions. Many foundational patterns have already been solved, there is no need to reinvent the wheel. I have used all of these methods throughout my career, but the trick is knowing when to use each one and when to push for proper user research. This comes with time. That said, not every feature or flow needs research. Some areas of a product are so well understood that testing does not add much value. What unconventional methods have you used to gather user feedback outside of traditional testing? _______ 👋🏻 I’m Wyatt—designer turned founder, building in public & sharing what I learn. Follow for more content like this!

During a Usability test, noticed that sometimes users tend to put on their 'best performance’ when they're being watched? You're likely witnessing the Hawthorne effect in action! Happens with us as well. When working from home, during meetings, you're more attentive, nodding more, and sitting up straighter, not just because you're engaged, but because you're aware that your colleagues can see you. This subtle shift in your behaviour due to the awareness of being observed is a daily manifestation of the Observation bias or Hawthorne effect. In the context of UX studies, participants often alter their behaviour because they know they're being observed. They might persist through long loading times or navigate more patiently, not because that's their natural behaviour, but to meet what they perceive are the expectations of the researcher. This phenomenon can yield misleading data, painting a rosier picture of user satisfaction and interaction than is true. When it comes to UX research, this effect can skew results because participants may alter how they interact with a product under observation. Here are some strategies to mitigate this bias in UX research: 🤝 Building Rapport:  Setting a casual tone from the start can also help, engaging in small talk to ease participants into the testing environment and subtly guiding them without being overly friendly. 🎯 Design Realistic Scenarios: Create tasks that reflect typical use cases to ensure participants' actions are as natural as possible.    🗣 Ease Into Testing: Use casual conversation to make participants comfortable and clarify that the session is informal and observational. 💡Set Clear Expectations: Tell participants that their natural behavior is what's needed, and that there's no right or wrong way to navigate the tasks. ✅ Value Honesty Over Perfection: Reinforce that the study aims to find design flaws, not user flaws, and that honest feedback is crucial. 🛑 Remind Them It's Not a Test: If participants apologise for mistakes, remind them that they're helping identify areas for improvement, not being graded. So the next time you're observing a test session and the participant seems to channel their inner tech wizard, remember—it might just be the Hawthorne effect rather than a sudden surge in digital prowess. Unmasking this 'performance' is key to genuine insights, because in the end, we're designing for humans, not stage actors. #uxresearch #uxtips #uxcommunity #ux