User Experience Discovery Methods

💡 Mapping user research techniques to levels of knowledge about users When doing user research, it's important to choose the right methods and tools to uncover valuable insights about user behavior. It's possible to identify 3 layers of user behavior, feelings, and thoughts: 1️⃣ Surface level - Say & Think This level captures what users say in conversations, interviews, or surveys and what they think about a product, feature, or experience. It reflects their stated opinions, thoughts, and intentions. Example: "I prefer simple products" or "I think this app is easy to use." Methods: Interviews, Questionnaires. These methods capture stated thoughts and opinions. However, insights may be influenced by social norms or biases. 2️⃣ Mid-level - Do & Use This level reflects what users actually do when interacting with a product or service. It emphasizes actions, usage patterns, and observed behaviors, revealing insights that may differ from what users say. Example: Users may claim they enjoy customizing app settings, but data shows they rarely change default options. Methods: Usability Testing, Observation. Observation helps to reveal gaps between what people say and what they actually do. 3️⃣ Deep level - Know, Feel and Dream This level uncovers deep motivations, emotions, desires, and aspirations that users may not be consciously aware of or may struggle to articulate. It also includes tacit knowledge—things people know intuitively but find hard to express. Example: A user might not realize that their preference for a minimalist design comes from the information overload of a current design. Methods: Probes (e.g., participatory design, diary studies). Insights collected using these methods will uncover implicit and emotional drivers influencing behavior. 📕 Practical recommendations for mapping ✅ Triangulate insights by using multiple methods. What people say (interviews/surveys) may differ from what they do (observations) and feel. That's why it's essential to interpret these results in context. For example, start with interviews to learn what users say. Follow up with usability testing to observe real behavior. Use probes for long-term or emotional insights. ✅ Align research with business goals. For product improvements, focus on usability testing to catch interaction issues. For innovation, use probes to generate new ideas from user insights. ✅ Practice iterative learning. Apply surface techniques (like surveys) early to refine assumptions and guide more in-depth research later. Use deep techniques (like probes) for strategic decisions and to foster innovation in long-term projects. 🖼️ UX Research methods by Maze #ux #uxresearch #design #productdesign #uxdesign #ui #uidesign

Design based on facts, not vibes. Here’s why UX research matters ↓ Skipping UX research when designing a website is like assembling IKEA furniture without the instructions. Sure, you might end up with a chair, but will it hold your weight—or will it wobble until it collapses? UX research isn’t just another box to check. It’s the foundation that keeps everything from falling apart. Without UX research, you’re designing based on vibes, not facts. And that’s how “cool” designs end up confusing users, tanking conversions, and turning into “oh no” moments after launch. So, what does UX research actually do? → Spot user pain points before they become your pain points. → Prioritize features and designs using real data instead of educated guesses. → Create experiences users love, not just tolerate. → Boost key metrics like engagement and conversions (because let’s be honest, that’s the end goal). So, how do you make UX research happen? By staying curious, asking great questions, and using the right tools: 𝗨𝘀𝗲𝗿 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 Talk to real humans—ask them what’s frustrating, what’s working, and what they need. You’ll learn more in one conversation than you will from staring at analytics. 𝗨𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝘁𝗲𝘀𝘁𝗶𝗻𝗴 Put your design in front of users early. Watch where they click, hesitate, or get stuck. Sure, it’s humbling—but it’s also how you fix things before they become disasters. 𝗦𝘂𝗿𝘃𝗲𝘆𝘀 Fast, efficient, and a great way to confirm (or shatter) your assumptions. 𝗛𝗲𝗮𝘁𝗺𝗮𝗽𝘀 Find out where users click, scroll, and hover. They’ll tell you exactly where your design nails it or falls flat. 𝗔/𝗕 𝘁𝗲𝘀𝘁𝗶𝗻𝗴 When you can’t decide between two options, let users vote with their actions. Data > opinions. 𝗖𝗼𝗺𝗽𝗲𝘁𝗶𝘁𝗼𝗿 𝗮𝗻𝗮𝗹𝘆𝘀𝗶𝘀 No, it’s not copying—it’s learning what works in your industry and where you can stand out. 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 𝗺𝗮𝗽𝗽𝗶𝗻𝗴 Walk in your users’ shoes. Every step of the way. From discovery to conversion, figure out where they’re thrilled and where they’re frustrated. Here’s the bottom line: Fixing problems post-launch is a headache you don’t need. UX research saves you time, money, and the embarrassment of explaining why users can’t figure out your shiny new design. Build websites that don’t just look good—build ones that work for your users and your business. --- Follow Jeff Gapinski for more content like this. ♻️ Share this to help someone else out with their UX research today #UX #webdesign #marketing

Let's face it: most user interviews are a waste of time and resources. Teams conduct hours of interviews yet still build features nobody uses. Stakeholders sit through research readouts but continue to make decisions based on their gut instincts. Researchers themselves often struggle to extract actionable insights from their conversation transcripts. Here's why traditional user interviews so often fail to deliver value: 1. They're built on a faulty premise The conventional interview assumes users can accurately report their own behaviors, preferences, and needs. People are notoriously bad at understanding their own decision-making processes and predicting their future actions. 2. They collect opinions, not evidence "What do you think about this feature?" "Would you use this?" "How important is this to you?" These standard interview questions generate opinions, not evidence. Opinions (even from your target users) are not reliable predictors of actual behavior. 3. They're plagued by cognitive biases From social desirability bias to overweighting recent experiences to confirmation bias, interviews are a minefield of cognitive distortions. 4. They're often conducted too late Many teams turn to user interviews after the core product decisions have already been made. They become performative exercises to validate existing plans rather than tools for genuine discovery. 5. They're frequently disconnected from business metrics Even when interviews yield interesting insights, they often fail to connect directly to the metrics that drive business decisions, making it easy for stakeholders to dismiss the findings. 👉 Here's how to transform them from opinion-collection exercises into powerful insight generators: 1. Focus on behaviors, not preferences Instead of asking what users want, focus on what they actually do. Have users demonstrate their current workflows, complete tasks while thinking aloud, and walk through their existing solutions. 2. Use concrete artifacts and scenarios Abstract questions yield abstract answers. Ground your interviews in specific artifacts. Have users react to tangible options rather than imagining hypothetical features. 3. Triangulate across methods Pair qualitative insights with behavioral data, & other sources of evidence. When you find contradictions, dig deeper to understand why users' stated preferences don't match their actual behaviors. 4. Apply framework-based synthesis Move beyond simply highlighting interesting quotes. Apply structured frameworks to your analysis. 5. Directly connect findings to decisions For each research insight, explicitly identify what product decisions it should influence and how success will be measured. This makes it much harder for stakeholders to ignore your recommendations. What's your experience with user interviews? Have you found ways to make them more effective? Or have you discovered other methods that deliver deeper user insights?

UX Research Method #2: Behavioral Mapping This one is especially interesting for those of us doing fieldwork in healthcare, finance, or other real-world contexts. What is it? Behavioral mapping is a qualitative, observational method that documents what people are doing in specific locations. It can be done using annotated maps, plans, time-lapse photography, or video. The goal? Understand what people do, where, with whom, and in what context. Type of method ➤ Qualitative ➤ Observational ➤ Exploratory When to use it ➤ During early research phases ➤ When understanding real-world behavior in physical environments ➤ When studying journeys that involve both movement and location What it’s useful for ➤ Documenting observable behavior, movements, and activities ➤ Linking behaviors to personas or segments ➤ Understanding how users interact with a space or move through a journey ➤ Identifying time spent, social context, and environmental details What it’s not useful for ➤ Understanding internal states (like motivations or emotions) ➤ Testing digital interfaces ➤ Drawing conclusions without triangulating with other data sources Pro tip: When video isn’t allowed (e.g., in healthcare settings), time-lapse photography can still offer rich insights without breaching privacy. There are two types: Place-centered mapping – observing what happens at a specific location. Individual-centered mapping – following a person’s journey across multiple locations over time. Behavioral mapping is a great tool to understand behavior in context—and that context often shapes user needs more than we realize. Want me to cover a specific method next? Let me know. UXR Study

🔍 User Testing: Turning Insights into Innovation 💡 🔍 Introduction: User testing is the cornerstone of great design, providing real-world insights that help refine and improve products. It’s the process where assumptions meet reality, allowing designers to understand how users interact with their creations and where adjustments are needed. 📈 Case Study: The Power of User Feedback: Take the example of a popular mobile app that struggled with low user retention. After conducting thorough user testing, the design team discovered that the navigation was confusing for new users. By simplifying the user flow and making key features more accessible, they saw a dramatic increase in engagement and retention. This transformation highlights the impact that user testing can have on a product's success. 🔬 Methods of User Testing: There are several effective methods for gathering user feedback: A/B Testing: Compare two versions of a design to see which performs better. Usability Studies: Observe users as they interact with your product to identify pain points and areas for improvement. Surveys and Interviews: Collect direct feedback from users about their experiences and preferences. Remote Testing: Leverage online tools to gather feedback from a diverse user base, no matter where they are. ⚠️ Common Pitfalls and How to Avoid Them: One common mistake in user testing is not testing with a diverse group of users. Ensure you have a varied testing pool to get a holistic view of your product’s performance. Another pitfall is ignoring qualitative feedback in favor of quantitative data. Both types of feedback are crucial in understanding the full picture of user experience. 🔍 Conclusion: User testing isn’t just a step in the design process—it’s the heartbeat that keeps your product alive and thriving. By incorporating user feedback early and often, you can create designs that truly meet user needs and expectations. Don’t skip this critical process; it’s key to turning insights into innovative, user-friendly designs. Ready to take your design to the next level? Start prioritizing user testing today! #UserTesting #UXDesign #Innovation #UserExperience #DesignThinking

I cannot overstate how important research and testing is. Unfortunately, it can be a tough sell to project managers. There just isn't much time or money to spare in a lean, agile environment. Here are a few tips for conducting meaningful research on a shoestring budget (be that time, money, or both). 1. Collaborate - Don't do this in a silo! Start by speaking with the rest of the team to find out what research they've already done. Depending on the situation and project, even taking a look at founding documents can be a help. 2. Speak with stakeholders - A carefully prepared interview or simple card-sorting activity can reveal a lot quickly, and almost every budget will accommodate post-it notes (or I like to do this in Miro) 3. Competitor analysis - Craete a research document with screen clippings and an analysis of competitors' products' voice, tone, and stand-out phrases. 4. Conversation mining - Visit tech review sites (like G2, Trustpilot, etc.) and competitors' social media pages to see how actual users talk about the products. You can learn common phrases, pain points, and more to address in your copy for a competitive advantage. 5. Black hat sessions - Can't afford user testing? Brushing up on Edward de Bono's Thinking Hats and running a black hat session with your team can illuminate potential usability concerns. 6. Guerilla testing - If you have a prototype you'd like to test, head to a coffee shop and offer to grab someone a cup of coffee if they'd be willing to take a quick look at a prototype. #UX #UXResearch #UXTips # #UXWriting #ContentDesign #DesignThinking #UXStrategy #HumanCenteredDesign #UserExperience #TeamWork #ForTheLoveOfWords

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!

I wouldn't want to go to a doctor who could ONLY use a stethoscope to diagnose me. I am grateful they have different tools and tests at their disposal. The same applies to customer discovery, where we are looking for signs and symptoms to answer three crucial questions: 1. Who is your ideal customer? 2. What is their job to be done? 3. What value can we deliver to them and the business? The good news is that although we don't just have a single tool... We also don't need a bottomless tool chest. In discovery, 80% of our diagnostic ability is driven by 20% of the methods we use. (and don't listen to the elitists that tell you only researchers can use them) The “foundational five” as I see them: 💬 Interviews 📑 Basic surveys 📚 Desk research 🔭 Field observation 🖥️ Usability and concept testing Use these methods to find... • 👀 signs—things you observe, and • 👂 symptoms—things people tell you ...that de-risk product decisions and create business growth by shipping better products faster. You don't need a PhD to do discovery. You just need a desire to learn the fundamentals. And then, in the eternal words of Nike: Just do it. ===== 👋 I'm Ari...a criminal investigator turned customer investigator If you liked this post: 👍 Like it 🛟 Save it ♻ Repost it 🔔 Follow me 💌 Subscribe (link in comments👇)