User Experience Research Techniques

✅ How To Run Task Analysis In UX (https://lnkd.in/e_s_TG3a), a practical step-by-step guide on how to study user goals, map user’s workflows, understand top tasks and then use them to inform and shape design decisions. Neatly put together by Thomas Stokes. 🚫 Good UX isn’t just high completion rates for top tasks. 🤔 Better: high accuracy, low task on time, high completion rates. ✅ Task analysis breaks down user tasks to understand user goals. ✅ Tasks are goal-oriented user actions (start → end point → success). ✅ Usually presented as a tree (hierarchical task-analysis diagram, HTA). ✅ First, collect data: users, what they try to do and how they do it. ✅ Refine your task list with stakeholders, then get users to vote. ✅ Translate each top task into goals, starting point and end point. ✅ Break down: user’s goal → sub-goals; sub-goal → single steps. ✅ For non-linear/circular steps: mark alternate paths as branches. ✅ Scrutinize every single step for errors, efficiency, opportunities. ✅ Attach design improvements as sticky notes to each step. 🚫 Don’t lose track in small tasks: come back to the big picture. Personally, I've been relying on top task analysis for years now, kindly introduced by Gerry McGovern. Of all the techniques to capture the essence of user experience, it’s a reliable way to do so. Bring it together with task completion rates and task completion times, and you have a reliable metric to track your UX performance over time. Once you identify 10–12 representative tasks and get them approved by stakeholders, we can track how well a product is performing over time. Refine the task wording and recruit the right participants. Then give these tasks to 15–18 actual users and track success rates, time on task and accuracy of input. That gives you an objective measure of success for your design efforts. And you can repeat it every 4–8 months, depending on velocity of the team. It’s remarkably easy to establish and run, but also has high visibility and impact — especially if it tracks the heart of what the product is about. Useful resources: Task Analysis: Support Users in Achieving Their Goals (attached image), by Maria Rosala https://lnkd.in/ePmARap3 What Really Matters: Focusing on Top Tasks, by Gerry McGovern https://lnkd.in/eWBXpCQp How To Make Sense Of Any Mess (free book), by Abby Covert https://lnkd.in/enxMMhMe How We Did It: Task Analysis (Case Study), by Jacob Filipp https://lnkd.in/edKYU6xE How To Optimize UX and Improve Task Efficiency, by Ella Webber https://lnkd.in/eKdKNtsR How to Conduct a Top Task Analysis, by Jeff Sauro https://lnkd.in/eqWp_RNG [continues in the comments below ↓]

Your research findings are useless if they don't drive decisions. After watching countless brilliant insights disappear into the void, I developed 5 practical templates I use to transform research into action: 1. Decision-Driven Journey Map Standard journey maps look nice but often collect dust. My Decision-Driven Journey Map directly connects user pain points to specific product decisions with clear ownership. Key components: - User journey stages with actions - Pain points with severity ratings (1-5) - Required product decisions for each pain - Decision owner assignment - Implementation timeline This structure creates immediate accountability and turns abstract user problems into concrete action items. 2. Stakeholder Belief Audit Workshop Many product decisions happen based on untested assumptions. This workshop template helps you document and systematically test stakeholder beliefs about users. The four-step process: - Document stakeholder beliefs + confidence level - Prioritize which beliefs to test (impact vs. confidence) - Select appropriate testing methods - Create an action plan with owners and timelines When stakeholders participate in this process, they're far more likely to act on the results. 3. Insight-Action Workshop Guide Research without decisions is just expensive trivia. This workshop template provides a structured 90-minute framework to turn insights into product decisions. Workshop flow: - Research recap (15min) - Insight mapping (15min) - Decision matrix (15min) - Action planning (30min) - Wrap-up and commitments (15min) The decision matrix helps prioritize actions based on user value and implementation effort, ensuring resources are allocated effectively. 4. Five-Minute Video Insights Stakeholders rarely read full research reports. These bite-sized video templates drive decisions better than documents by making insights impossible to ignore. Video structure: - 30 sec: Key finding - 3 min: Supporting user clips - 1 min: Implications - 30 sec: Recommended next steps Pro tip: Create a library of these videos organized by product area for easy reference during planning sessions. 5. Progressive Disclosure Testing Protocol Standard usability testing tries to cover too much. This protocol focuses on how users process information over time to reveal deeper UX issues. Testing phases: - First 5-second impression - Initial scanning behavior - First meaningful action - Information discovery pattern - Task completion approach This approach reveals how users actually build mental models of your product, leading to more impactful interface decisions. Stop letting your hard-earned research insights collect dust. I’m dropping the first 3 templates below, & I’d love to hear which decision-making hurdle is currently blocking your research from making an impact! (The data in the templates is just an example, let me know in the comments or message me if you’d like the blank versions).

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.

Ever spent months building a product, only to realize no one’s willing to pay for it? I’ve seen this happen more times than I’d like to admit—especially with first-time tech founders. One big reason? They didn’t talk to enough customers/users before building their solution. In some cases, they didn’t talk to anyone at all! Trust me, skipping these interviews is like flying blind—it rarely ends well. Building something people actually want starts here. Here’s what I’ve learned about doing user interviews effectively:   𝗧𝗶𝗽𝘀 𝗳𝗼𝗿 𝗨𝘀𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄𝘀 Focus on understanding, not pitching. Speak less. Listen more. Respect their time—15-20 minutes is enough. Ask open-ended questions to dig deeper. Find out if it’s a real pain point, not just a "nice-to-have." 𝗨𝘀𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝘁𝗼 𝗔𝘀𝗸 What’s the hardest part of this problem? When did it last happen? What caused it? How did you try solving it? Did it work? Why was it so difficult to address? What don’t you love about existing solutions? 𝗨𝘀𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗡𝗼𝘁 𝘁𝗼 𝗔𝘀𝗸 "Would you buy this if I built it?" (It’s hypothetical and leads to false positives.) "Do you think this is a good idea?" (People want to be polite and will often say yes.) "Would you pay X amount for this?" (Pricing feedback without context isn’t reliable.) The goal is to uncover the truth, not get the answers you want to hear! #startups #startupindia #incubator #management #founder #uservalidation

7 things I’d do right now as an in-house UX researcher to make my work matter You’re shipping insights but decisions still happen without you You’re in the room but your input’s too late You’re running solid studies but people don’t remember them a week later If I were in-house again, here’s exactly what I’d do to change that: 1. Add a baseline and follow-up to every study No baseline? No impact. Every study would start with: - What metric or decision are we trying to shift? - Where is it today? - How will we know if we moved it? Then I’d schedule a follow-up 4 weeks later to ask: - What changed about the metric? - What decisions were we able to make? - Did anyone act on it? - Did we learn anything unexpected? Even if the answer is “nothing changed,” that’s a finding. That’s evidence. That’s visibility. 2. Create a 1-page roadmap and update it monthly Just a table with: - Project name - Which decision it’s meant to support - Who requested it (or why I’m doing it) - Status I’d circulate it like product teams do their sprint boards. It becomes the backbone of research comms. When someone asks, “What are you working on?” they get the link. 3. Run a workshop called: “What decisions are you stuck on?” 5 stakeholders. 45 minutes. 1 board with 2 columns: - Decisions we need to make - What’s stopping us? I’d cluster responses, pick one, and scope a super lean study to unlock it in 10 days or less. Repeat once per quarter. 4. Turn one chunky project into a rolling study Instead of running a massive generative project once a year, I’d slice it down into a monthly rhythm: - One 20-minute interview a week - One theme per month - An executive summary at the end. You stay close to the user. The org stays warm to the problem. 5. Build a habit of sending weekly research signals I’d pick a repeatable day (say, Wednesday) and send one research signal every week: - A 45-second video clip, a quote that flips an assumption, or a side-by-side of what users expected vs what happened - Tag the relevant team and concisely explain what happened - Ask them what next steps they can take to fix it No template. No pressure. Just high-frequency learning in a low-friction format. 6. Use a research request form that raises the bar on thinking Add friction and force focus. Ask: - What decision is this tied to? - What do you already know? - What happens if we don’t answer this? 7. Rip apart your reporting process and rebuild it with your stakeholders Instead of asking “How should we report this?” ask: - What format gets used? - What’s easiest for you to share? - What helped you make a decision last time? Test it like you test a product. You don’t need to overhaul everything at once. Pick one. Test it. Track the shift.

Your Product Managers are talking to customers. So why isn’t your product getting better? A few years ago, I was on a team where our boss had a rule: 🗣️ “Everyone must talk to at least one customer each week.” So we did. Calls were scheduled. Conversations happened. Boxes were checked. But nothing changed. No real insights. No real impact. Because talking to customers isn’t the goal. Learning the right things is. When discovery lacks purpose, it leads to wasted effort, misaligned strategy, and poor business decisions: ❌ Features get built that no one actually needs. ❌ Roadmaps get shaped by the loudest voices, not the right customers. ❌ Teams collect insights… but fail to act on them. How Do You Fix It? ✅ Talk to the Right People Not every customer insight is useful. Prioritize: -> Decision-makers AND end-users – You need both perspectives. -> Customers who represent your core market – Not just the loudest complainers. -> Direct conversations – Avoid proxy insights that create blind spots. 👉 Actionable Step: Before each interview, ask: “Is this customer representative of the next 100 we want to win?” If not, rethink who you’re talking to. ✅ Ask the Right Questions A great question challenges assumptions. A bad one reinforces them. -> Stop asking: “Would you use this?” -> Start asking: “How do you solve this today?” -> Show AI prototypes and iterate in real-time – Faster than long discovery cycles. -> If shipping something is faster than researching it—just build it. 👉 Actionable Step: Replace one of your upcoming interview questions with: “What workarounds have you created to solve this problem?” This reveals real pain points. ✅ Don’t Let Insights Die in a Doc Discovery isn’t about collecting insights. It’s about acting on them. -> Validate across multiple customers before making decisions. -> Share findings with your team—don’t keep them locked in Notion. -> Close the loop—show customers how their feedback shaped the product. 👉 Actionable Step: Every two weeks, review customer insights with your team to decipher key patterns and identify what changes should be applied. If there’s no clear action, you’re just collecting data—not driving change. Final Thought Great discovery doesn’t just inform product decisions—it shapes business strategy. Done right, it helps teams build what matters, align with real customer needs, and drive meaningful outcomes. 👉 Be honest—are your customer conversations actually making a difference? If not, what’s missing? -- 👋 I'm Ron Yang, a product leader and advisor. Follow me for insights on product leadership + strategy.

Color plays a major role in that decision before users even read a word. In UX/UI design, color isn’t just visual =>𝗜𝘁’𝘀 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 It guides attention, builds trust, and shapes how users feel about a product. Why does color matter this much? Because users don’t think first—they perceive first. 👉 Visuals are processed 60,000x faster than text 👉 Color improves recognition and usability when used consistently Here are key factors that influence how users experience color: 🎨 TONE & SATURATION ⇢ Bright colors = energy, attention ⇢ Muted tones = calm, approachable ⇢ Dark shades = depth, authority 🌍 CONTEXT & CULTURE ⇢ Colors don’t mean the same everywhere ⇢ Red can signal urgency—or celebration ⇢ White can mean simplicity—or emptiness 🧠 USER EXPERIENCE ⇢ High contrast improves readability ⇢ Consistent colors improve navigation ⇢ Clear color hierarchy reduces confusion HOW COLORS FUNCTION IN UX/UI: 🔴 Red: Attention, urgency, action ↳ Use for alerts, errors, critical CTAs 🟢 Green: Balance, growth, reassurance ↳ Ideal for success states, confirmations 🔵 Blue: Trust, stability, clarity ↳ Common in dashboards, finance, tech 🟡 Yellow: Positivity, highlight, alertness ↳ Best for drawing attention to key elements 🟣 Purple: Creativity, depth, differentiation ↳ Works well for unique or premium experiences 🟠 Orange: Energy, engagement, visibility ↳ Strong for CTAs and interactive elements 🟤 Brown: Warmth, grounding, authenticity ↳ Suitable for natural or earthy brands 🩷 Pink: Friendliness, care, approachability ↳ Often used in lifestyle and community-focused apps ⚫ Black: Contrast, authority, emphasis ↳ Useful for hierarchy and premium feel ⚪ Gray: Balance, neutrality, support ↳ Essential for backgrounds and secondary elements Don’t choose colors because they look good. Choose them based on how users think and behave. Ask yourself: ✓ What action should the user take here? ✓ What emotion should this screen create? ✓ Does my color system guide or confuse? ✓ Is my hierarchy clear at a glance? Good design isn’t decoration. It’s decision-making made easier. What’s one color you rely on most in your UI designs? #ColorPsychology #UXDesign #UIDesign #UXUI #ProductDesign #DesignThinking #imenmlika

You ran the sessions. You found the themes. The insights feel right. But before you present, a quiet question lingers, did I go deep enough? Did I check the right things? This is the part of qualitative UX research we don’t always emphasize. Not just doing the work with care, but supporting it with structure. Adding rigor isn’t about questioning your effort - it’s about strengthening your insights. It brings clarity, consistency, and confidence - for you, your team, and anyone who’ll act on what you’ve found. Here are eight practical ways to add that kind of rigor without slowing your work down. Start with triangulation. Don’t rely on just one type of data. Pair interviews with usability testing, behavior logs, or survey responses. Ask another researcher to take notes independently and compare interpretations. This builds confidence that your insights reflect more than one lens. Maintain an audit trail. Keep a record of key decisions, theme changes, or shifts in scope. Use a shared doc, spreadsheet, or even versioned codebooks. Others should be able to see how your findings evolved- not just the end product. Practice reflexivity. Before analysis, write down what you expect to find. During synthesis, notice when your background might be influencing what feels important. If you’re working in a team, make this a shared habit. You’re part of the instrument, and that’s worth tracking. Use member checking. Once your findings are drafted, send a summary to a few participants and ask if it reflects their experience. Their feedback will tell you where you’ve nailed it- and where you need to dig deeper. Use structured frameworks. Lincoln and Guba’s trustworthiness criteria are great for longer studies. The PARRQA checklist helps keep fast-paced projects grounded. Either way, frameworks give your work consistency and make your choices visible. Look for negative cases. Instead of just confirming patterns, search for outliers. Find the participant who doesn’t fit the theme. Revising your analysis to include their story makes your findings more durable. Make your insights transferable. Don’t stop at “users want X.” Add who those users were, what tools they used, and what constraints they faced. When findings are rich in context, teams can apply them more confidently. Document key decisions as they happen. Use a shared log or notes thread. Track sampling shifts, analysis changes, design pivots. Later, include this in your final report. It shows how you got from raw data to real insight- and helps others trust it. Rigor isn’t about adding more work - it’s about adding more strength. Even a few thoughtful checks, built into your workflow, can make your qualitative UX research clearer, more credible, and easier to stand behind when the pressure’s on.

I’ve worked at quite a few companies, and the same thing happens again and again in UX research: A researcher works hard on a study. They write a massive report filled with insights. They send it out… and nothing happens. It doesn’t matter how brilliant the findings are—no one is reading a 180-page document. And if no one reads it, nothing changes. So instead of writing reports that get ignored, I run synthesis workshops. How it works: Instead of just delivering research, you bring stakeholders into the synthesis process. Designers, product managers, and customer journey experts work together with the researcher to: 1. Review key data—the researcher pre-selects and preps the most important findings. 2. Identify patterns and themes—using affinity mapping or similar methods. 3. Recognize issues & opportunities—what needs to change, and where are the gaps? 4. Map out impact—for users, business goals, and design. 5. Prioritize & brainstorm solutions—to define design recommendations By the end of the session, everyone owns the findings. The insights aren’t just the researcher’s anymore—they belong to the whole team. Why this works: • Stakeholders engage with the research instead of just receiving a PDF. • Insights get used because everyone is part of defining the next steps. • It’s faster than writing a giant report and drives real change. Instead of a report that gathers dust, you walk away with shared understanding, buy-in, and actionable recommendations. If your research isn't leading to impact, try bringing people into the process instead of just handing them the results.

💡 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