User Experience Research Techniques

Last week, I coached a product team through a user interview debrief. They were excited! Users had shown enthusiasm for a new feature! 🎉 But when I asked, “What problem does this solve for them?” the room went quiet. 🫣 This happens more often than we’d like to admit. 🧠 The Trap: Mistaking Enthusiasm for Validation When users say, “That sounds great!” we often interpret it as validation. But here's the catch: - Users want to be polite. - They might not fully understand their own needs. - As product teams, we may hear what we want. This is why relying solely on user enthusiasm can lead us astray. 🔍 The Solution: Semi-Structured Interviews We need to dig deeper to understand our users truly. Semi-structured interviews strike the right balance between guidance and flexibility. Key practices include: - Start with hypotheses: Identify what you believe to be true. - Ask open-ended questions: Encourage users to share experiences, not just opinions. - Listen actively: Pay attention to what’s said—and what’s not. - Probe for underlying needs: Seek to understand the 'why' behind their behaviours. This approach helps uncover genuine insights, leading to solutions that truly resonate. 🌟 Imagine the Impact By adopting this method: - Teams build products that solve real problems. - User satisfaction increases. - Resources are invested wisely, reducing wasted effort. It's not just about building features—it's about delivering value. 🦾 Take Action Next time you're planning user interviews: - Prepare a set of hypotheses. - Design questions that explore user experiences. - Remain open to unexpected insights. Remember, the goal is to understand your users, not just confirm your assumptions deeply.

💡 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

There’s something deeply satisfying about watching a well-run qualitative interview quietly evolve into a sophisticated quantitative model. I always tell my students and collaborators that when done right, a simple conversation can eventually fuel something as complex as Structural Equation Modeling. It might sound like a stretch, but it’s really not. I went through this exact process in a study where we aimed to understand why users trust or reject a new product. Like many applied UX projects, we started with messy assumptions, vague ideas. We knew launching a survey would be premature, so we turned to interviews. We had open but focused (guided) conversations with users. Certain phrases kept surfacing. Some participants talked about feeling “disconnected” from the product, even though they found it useful. Others compared it to brands they already trusted, which clearly shaped their expectations. These comments weren’t dramatic, but they hinted at deeper structures behind user decisions. I worked through the transcripts by reading closely, making notes in the margins, and sketching out connections. There was no formal codebook in the beginning. Instead, I relied on a grounded and intuitive approach shaped by years of dealing with messy real-world data. Over time, themes began to take shape. Emotional tone, familiarity, and social alignment emerged as key ideas. These did not come from forcing responses into predefined buckets, but from how users naturally framed their experiences. It was far from a clean process. I constantly revisited groupings, challenged my own interpretations, and asked whether I was seeing real patterns or just noise. But that back-and-forth reflection is exactly where the model began to form. Once the ideas felt more stable, I started thinking about structure. One pattern stood out. When users described the product’s emotional tone early in the conversation, using words like “cold” or “inviting,” they often brought up trust later on. That sequence did not happen in reverse. It was a small but (almost!) consistent thread, and it became the basis for one of our causal paths. This is something people often overlook. Interviews do more than offer themes; they can reveal directionality. If you listen closely, the order in which ideas appear can show you which concepts come first, which serve as bridges, and how the entire experience unfolds in the user’s mind. Eventually, we translated those themes into measurable constructs and tested the model with survey data. Turning rich, emotional language into structured scale items was not easy. The final SEM model did not just fit the data well. It helped us predict how users would respond to different messaging and revealed emotional drop-off points we might have missed otherwise. All of that came from listening first, not guessing. Interviews are not the soft side of research. They are the foundation that allows your most complex methods to stand on something real.

User experience surveys are often underestimated. Too many teams reduce them to a checkbox exercise - a few questions thrown in post-launch, a quick look at average scores, and then back to development. But that approach leaves immense value on the table. A UX survey is not just a feedback form; it’s a structured method for learning what users think, feel, and need at scale- a design artifact in its own right. Designing an effective UX survey starts with a deeper commitment to methodology. Every question must serve a specific purpose aligned with research and product objectives. This means writing questions with cognitive clarity and neutrality, minimizing effort while maximizing insight. Whether you’re measuring satisfaction, engagement, feature prioritization, or behavioral intent, the wording, order, and format of your questions matter. Even small design choices, like using semantic differential scales instead of Likert items, can significantly reduce bias and enhance the authenticity of user responses. When we ask users, "How satisfied are you with this feature?" we might assume we're getting a clear answer. But subtle framing, mode of delivery, and even time of day can skew responses. Research shows that midweek deployment, especially on Wednesdays and Thursdays, significantly boosts both response rate and data quality. In-app micro-surveys work best for contextual feedback after specific actions, while email campaigns are better for longer, reflective questions-if properly timed and personalized. Sampling and segmentation are not just statistical details-they’re strategy. Voluntary surveys often over-represent highly engaged users, so proactively reaching less vocal segments is crucial. Carefully designed incentive structures (that don't distort motivation) and multi-modal distribution (like combining in-product, email, and social channels) offer more balanced and complete data. Survey analysis should also go beyond averages. Tracking distributions over time, comparing segments, and integrating open-ended insights lets you uncover both patterns and outliers that drive deeper understanding. One-off surveys are helpful, but longitudinal tracking and transactional pulse surveys provide trend data that allows teams to act on real user sentiment changes over time. The richest insights emerge when we synthesize qualitative and quantitative data. An open comment field that surfaces friction points, layered with behavioral analytics and sentiment analysis, can highlight not just what users feel, but why. Done well, UX surveys are not a support function - they are core to user-centered design. They can help prioritize features, flag usability breakdowns, and measure engagement in a way that's scalable and repeatable. But this only works when we elevate surveys from a technical task to a strategic discipline.

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

Your UX research is lying to you. And no, I'm not talking about small data inconsistencies. I've seen founders blow $100K+ on product features their users "desperately wanted" only to face 0% adoption. Most research methods are fundamentally flawed because humans are terrible at predicting their own behavior. Here's the TRUTH framework I've used to get accurate user insights: T - Test with money, not words • Never ask "would you use this?" • Instead: "Here's a pre-order link for $50" • Watch what they do, not what they say R - Real environment observations • Stop doing sterile lab tests • Start shadowing users in their natural habitat • Record their frustrations, not their feedback U - Unscripted conversations • Ditch your rigid question list • Let users go off on tangents • Their random rants reveal gold T - Track behavior logs • Implement analytics BEFORE research • Compare what users say vs. what they do • Look for patterns, not preferences H - Hidden pain mining • Users can't tell you their problems • But they'll show you through workarounds • Document their "hacks" - that's where innovation lives STOP: • Running bias-filled focus groups • Asking leading questions • Taking feedback at face value • Rushing to build based on opinions START: • Following the TRUTH framework • Measuring actions over words • Building only what users prove they need PS: Remember, Henry Ford said if he asked people what they wanted, they would have said "faster horses." Don't ask what they want. Watch what they do. Follow me, John Balboa. I swear I'm friendly and I won't detach your components.

When I teach new researchers how to conduct interviews for the first time, I like to stick to 3 guiding principles. When first learning, it can be overwhelming for new researchers to remember a long list of do's/don'ts or specific phrasing, tricks, or techniques to use or avoid. Instead, I want new researchers to first practice active listening and empathy, offering neutral questions and responses, and staying aligned with the research goals. If we can get these 3 principles down, we're in a good place to work on further fine-tuning interviewing skills from that solid foundation. 1. Active Listening 💕 Focus on truly understanding the user’s thoughts, feelings, and behaviors and showing them that you are interested and care about what they're telling you. Give your participant your full attention, use body language to show you're listening (e.g., nodding, eye contact), and notice for signs in their body language, facial expressions, and tone of voice. You can respond to users' responses paraphrasing what they said to check for understanding, thoughtful follow-up questions, or an empathic acknowledgement of their feelings and experiences. The ultimate goal here is to foster trust and show participants you value what they're sharing with you, which can lead to more authentic, insightful feedback. 2. Neutral Questioning and Responses ❓ When asking questions and responding to participant answers, maintain neutrality. Avoid leading or priming questions that encourage participants to answer in a certain way or block them from exploring different directions. Focus on neutral, open-ended questions that encourage continued conversation and sharing. Neutrality doesn't mean being cold, we're still going to actively listening and show interest. You can warmly respond to users' responses in ways that don't reward or punish certain responses. We're just trying to set up our interaction the best we can so that users don't feel encouraged or deterred from providing certain feedback or sharing certain experiences. 3. Focus on Goals 🥅 Know the goals of the research and keep them in focus during the interview. If you know what the goals of the research are, you'll be much better able to formulate follow-up questions and follow the stories of users to relevant places your stakeholders are interested in. You'll also be aware of when to redirect or refocus the conversation when it veers too far away from the goals of your research. When I was starting out and feeling a bit shaky and nervous about interviewing, knowing the research goals well really helped me reaffirm to myself that I'm doing my job to answer our research questions, even if an interview didn't go as planned or if my confidence wavered. ❓ What other guiding principles helped you when you were first learning how to conduct user interviews? ❓ If you're currently learning how to conduct user interviews, what gaps do you see? #UXResearch #UserInterviews #QualitativeResearch #LearningUXR

Founders often say they don't do research. "I don't have time for that." "I know my users so I don't need it." But if you do any of these things, you're already participating in research:   1/ You read customer support tickets You're identifying patterns in pain points and understanding where your product is falling short   2/ You listen to Gong calls You're gathering insights on what resonates with your ICP and what objections keep coming up   3/ You check your product analytics You're tracking user behavior to understand what features drive engagement and where people drop off   4/ You A/B test your pricing page You're testing hypotheses about what messaging converts better with your audience   5/ You send out NPS surveys You're measuring customer satisfaction and identifying promoters versus detractors   6/ You run beta programs You're validating product concepts before you scale them to your full user base   7/ You ask "why did you choose us?" You're uncovering the jobs-to-be-done that your product fulfills for customers   8/ You track churn and interview people who leave You're understanding what drives customers away so you can fix it   9/ You read competitor reviews You're mapping where the market has gaps and where you can differentiate   10/ You prototype before you build You're validating demand and testing assumptions about what users actually need   11/ You check which email subject lines get opened You're experimenting with messaging that resonates with your audience   12/ You monitor what features get requested most You're prioritizing your roadmap based on patterns in customer demand   13/ You ask customers for testimonials You're discovering what value they're actually getting from your product in their own words   14/ You test landing page variations You're optimizing how you communicate value to drive conversions   15/ You have regular check-ins with your ICP You're building continuous feedback loops to stay connected to how their needs evolve   Even if you don't think of it as conducting research, you can consider it an exercise in building empathy. 

The key to effective usability testing? Approaching it with a Human-Obsessed mindset. This is crucial. It determines whether your improvements are based on assumptions or real user insights. It guides how you engage with: → User needs → Common tasks → Pain points → and Preferences throughout their journey on your site. Usability testing isn’t straightforward. It requires a deep understanding of user behavior and continuous refinement. How do you start a Human-Obsessed usability testing approach? Follow these steps: 1. Set Specific Goals — Focus on areas like navigation and checkout.  — Know what you aim to improve. 2. Match Test Participants to Users — Ensure your participants reflect your actual user base.  — Diverse feedback is key. 3. Design Realistic Tasks — Reflect common user goals like finding a product or making a purchase.  — Keep it real. 4. Choose the Right Method — Decide between moderated (in-depth) and unmoderated (scalable) tests.  — Pick what suits your needs. 5. Use Effective Tools — Leverage tools like UserTesting or Lookback.  — Integrate analytics for comprehensive insights. 6. Create a True Test Environment — Mirror your live site.  — Ensure participants are focused and undistracted. 7. Pilot Testing — Run a pilot test to refine your setup and tasks.  — Adjust before full deployment. 8. Collect Qualitative and Quantitative Data — Gather user comments and behaviors.  — Measure task completion and errors. 9. Report Clearly and Take Action — Use visuals like heatmaps to present findings.  — Prioritize issues and recommend improvements. 10. Keep Testing Iteratively — Usability testing should be ongoing.  — Regularly test changes to continuously improve. Human-Obsessed usability testing is powerful. It’s how Enavi ensures exceptional user experiences. Always. Use it well. Thank us later.