UX Research Essentials

🐑 Business Language vs. UX Language. How to present design work, explain design decisions and get stakeholders on your side ↓ 🤔 Businesses rarely understand the impact of UX work. 🤔 UX language is overloaded with ambiguous terms/labels. 🤔 Business can’t support initiatives it doesn’t understand. ✅ Leave UX language and UX abbreviations at the door. ✅ Explain design work through the lens of business goals. 🚫 Avoid “consistency”, “empathy”, “simplicity”, “affordance”. 🚫 Avoid “design thinking”, “cognitive load”, “universal design”. 🚫 Avoid “lean UX”, “agile”, “archetypes”, “Jobs-To-Be-Done”. 🚫 Avoid “stakeholder management” and “design validation”. 🚫 Avoid abbreviations: WIP, POC, HMW, IxD, PDP, PLP, WCAG. ✅ Explain how you’ll measure success of your design work. ✅ Speak of business value, loyalty, abandonment, churn. ✅ Show risk management, compliance, governance, evidence. ✅ Refer to cost reduction, efficiency, growth, success, Design KPIs. ✅ Present inclusive design as an industry-wide way of working. As designers, we often use design terms, such as consistency, friction and empathy. Yet to many managers, these attributes don’t map to any business objectives at all, often leaving them baffled and utterly confused about the actual real-life impact of our UX work. One way out that changed everything for me is to leave UX vocabulary at the door when entering a business meeting. Instead, I try to explain design work through the lens of the business, often rehearsing and testing the script ahead of time. When presenting design work in a big meeting, I try to be very deliberate and strategic in the choice of words. I won’t be speaking about attracting “eye-balls” or getting users “hooked”. It’s just not me. But I won’t be speaking about reducing “friction” or improving “consistency” either. Instead, I tell a story. A story that visualizes how our work helps the business. How design team has translated business goals into specific design initiatives. How UX can reduce costs. Increase revenue. Grow business. Open new opportunities. New markets. Increase efficiency. Extend reach. Mitigate risk. Amplify word of mouth. And how we’ll measure all that huge impact of our work. Typically, it’s broken down into 8 sections: 🎯 Goals ← Business targets, KRs we aim to achieve. 💥 Translation ← Design initiatives, iterations, tests. 🕵️ Evidence ← Data from UX research, pain points. 🧠 Ideas ← Prioritized by an impact/effort-matrix. 🕹 Design work ← Flows, features, user journeys. 📈 Design KPIs ← How we’ll measure/report success. 🐑 Shepherding ← Risk management, governance. 🔮 Future ← What we believe are good next steps. Next time you walk in a meeting, pay attention to your words. Translate UX terms in a language that other departments understand. It might not take long until you’ll see support coming from everywhere — just because everyone can now clearly see how your work helps them do their work better. [continues in the comments]

Without user research, even the most exciting product in the world can fail. Ever played with LEGOs?👷 That’s a company that narrowly avoided collapse thanks to UXR. 📉In the 80s, Lego was losing its hold on the toy market. Video games and tech-based toys were entering the landscape. To keep up, LEGO launched its own theme parks & video games. They assumed what tech-savvy children would want, and launched new products. New customers didn’t care, loyal fans were confused. Nothing worked. This is when the LEGO team turned to user research. They reached out to adult fans and asked the community for feedback. They also launched a huge customer research programme in order to understand their Most Valuable Customers (MVCs)—the children who loved LEGO. The research showed that a lot of their assumptions were wrong. Even though the toy world had evolved, the tenets of play remained the same. Adults and children loved LEGOs for the possibilities of imagination, and building anything you wanted, with your friends. 🤝LEGO’s new moto? “constant empathetic contact with customers” Designers tested every new idea with users first before development. Fans became co-creators. Revenue tripled.💸💸💸 The value of RoI behind UX research sometimes only becomes obvious to companies once they’ve been burned. 🔴 For those of you struggling to prove that to your teams, here’s how you can calculate the RoI of your work (template included): https://bit.ly/3TRklJT And don’t just calculate it—shout it from the rooftops!! #uxroi #uxr

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.

Stop sending surveys. Seriously. They're a bad habit that gives you polite, sanitized data, not real insights. I found a way to get a 78% response rate and honest feedback by doing the exact opposite of what every marketing book recommends. Here are 5 customer research methods that beat surveys every single time: 1) WhatsApp Voice Notes > Written Surveys: ↳ People speak faster than they type ↳ Emotion comes through in voice tone ↳ No survey fatigue Method: Send a voice note asking ONE specific question "Hey [Name], quick question - what made you choose us over [competitor]?" 2) Watch Usage > Ask About Usage: ↳ What people do ≠ what they say they do ↳ Behavior reveals truth, words reveal intentions Method: Screen recordings + heatmaps show reality Ask: "How often do you use feature X?" → They say "daily" Data shows: Last used 3 weeks ago 3) Churned Customer Calls > Happy Customer Testimonials: ↳ Satisfaction bias makes happy customers less honest ↳ Churned customers have nothing to lose Method: Call customers who cancelled in the last 30 days "What could we have done differently to keep you?" Most brutal, most valuable insights you'll get. 4) Social Media Stalking > Focus Groups: ↳ Real conversations happen on Twitter/LinkedIn ↳ Unfiltered opinions in natural settings Method: Search "[your brand] OR [competitor] OR [problem you solve]" People complaining/praising without knowing you're watching. 5) Customer Success Team Coffee Chats > Executive Surveys: ↳ Front-line teams hear the real feedback daily ↳ Filter gets removed when it's informal Method: Weekly coffee with CS/Sales teams "What are customers actually saying?" Not the sanitized feedback that reaches leadership. The Pattern I've Noticed: The closer you get to natural conversation, the better the insights. → Formal surveys = What customers think you want to hear → Informal chats = What customers actually think My personal favourite: Join Customer WhatsApp Groups/Communities- I have joined discord & reddit communities Don't moderate. Don't participate initially. Just observe. How they talk about problems. What words they use. Their real frustrations. Pure gold for messaging and positioning. The Reality:Most "customer insights" are actually "customer politeness." People won't tell you your product sucks on a formal survey. They will tell their friend on a WhatsApp call. Your job? Be the friend, not the survey. Which method are you going to try first?

🔍 Research Funnel: A Practical Way to Strengthen Your UX Research Just like any other product design activity, UX research benefits from a solid process. Emma Boulton’s Research Funnel (https://lnkd.in/diHXu-G9) offers a clear way to align research methods with each stage of the project lifecycle—from broad discovery to focused execution. Here’s how it works, step by step: 1️⃣ Understand the Funnel Layers The funnel moves from Top (Macro) - high-level, strategic domains that look at the big picture across systems, journeys, and ecosystems - to Bottom (Micro) - detailed, tactical focus points zoomed in on specific interactions or touchpoints. ✔ Exploratory (top): Broad, open-ended research to uncover new problem spaces or underserved segments. ✔ Strategic: Define target users, personas, and scenarios (moving from broad discovery to a refined direction). ✔ Tactical: Usability testing on prototypes to iterate and improve designs. ✔ Operational (bottom): Measure specific performance (e.g., A/B testing, conversion metrics). 2️⃣ Tailor Research to Each Phase Choose method that works best for the layer ✔ Exploratory: Use surveys or semi-structured interviews to explore adjacent problem areas. ✔ Strategic: Conduct baseline usability tests on the existing product, and develop personas and user journeys. ✔ Tactical: Test prototypes with real users to refine the solution. ✔ Operational: Track launch metrics, run A/B tests, and gather satisfaction data to measure ongoing performance. 3️⃣ Mix & Blend Methodologies Don’t wait for perfectly defined phases. Instead, blend exploratory, strategic, and tactical questions within a single research session to maximize insights (especially when resources are tight). 💡 Tip: Start interviews with broad, easy questions. Warm-up conversations often lead to surprising, high-value insights. 4️⃣ Expand Your Sample Go beyond just core users. Involve adjacent user groups like secondary personas or community members during exploratory and strategic phases. Also consider competitor reviews and internal stakeholder interviews to diversify your input. 5️⃣ Iterate Non-Linearly Research isn’t always linear. Use insights from later stages (like operational findings) to inform earlier ones. Feeding these learnings back into strategy or discovery can unlock powerful pivots. 6️⃣ Align Tools with Workflow ✔ Agile teams: Lean on tactical and operational research for continuous feedback loops. ✔ Discovery/redesign phases: Focus on exploratory and strategic research to build a strong foundation. 7️⃣ Make Research Actionable & Inclusive Involve stakeholders throughout the process—from planning to synthesis. Activities like co-analysis and affinity mapping help increase buy-in and prevent insights from being ignored. 📣 Share your findings in digestible formats: think plain-language summaries, visual slides, or short videos to make insights stick across teams. #UX #research #design

Why do some qualitative studies generate groundbreaking insights while others barely scratch the surface? The secret is not in the data collected, but in matching your methodology to your research goals. The 5 qualitative research methods nobody talks about: 1. Phenomenology • Perfect for understanding perceptions • Uses deep interview analysis • Captures lived experiences 2. Ethnography • Based on extended fieldwork • Documents cultural patterns • Gives insider perspective 3. Narrative Inquiry • Uses conversations & artifacts • Finds patterns in experiences • Tells people's stories 4. Case Study • Answers specific questions • Uses multiple data sources • Creates rich context 5. Grounded Theory • Perfect for unexplored topics • Analyzes data continuously • Builds new theories Pick your method based on your goal: → Want experiences? Use phenomenology → Need cultural insights? Try ethnography → Looking for stories? Go narrative → Seeking answers? Case study works → Building theory? Grounded theory fits Most researchers fail because they pick the wrong method for their research question. The right method = better research. 🗞️ Join 7,278+ researchers on my weekly newsletter: https://lnkd.in/e4HfhmrH P.S. Do you check method-research-question fit?

UX research is 𝗻𝗼𝘁 losing relevance. It’s entering a golden era with the power of AI. Understanding users is still a key skill for every PM. It reduces guesswork. Reveals real problems. Strengthens decisions across the product lifecycle. Here’s a breakdown of research methods every PM should use: 🔵 𝗤𝘂𝗮𝗹𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵 → Interviews, field studies, contextual inquiry → Understand the why behind user behavior → Use it in early discovery or to explore new problems 🔵 𝗤𝘂𝗮𝗻𝘁𝗶𝘁𝗮𝘁𝗶𝘃𝗲 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵 → Surveys, A/B tests, usage analytics → Track what’s happening at scale → Use it to validate direction and measure impact 🔵 𝗠𝗶𝘅𝗲𝗱 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 → Combine qualitative and quantitative → Get context and confidence from both types of data → Strongest when used across the product lifecycle The best PMs don’t skip research. They use it to make every decision sharper. They combine insight and data. And they do it fast. With AI, UX research is now faster, smarter, and easier. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝗮 𝗳𝗲𝘄 𝗔𝗜 𝘁𝗼𝗼𝗹𝘀 𝘄𝗼𝗿𝘁𝗵 𝗲𝘅𝗽𝗹𝗼𝗿𝗶𝗻𝗴: ⚡ whyser.ai AI-led interviews with real users ⚡ syntheticusers.com Research with AI-generated personas ⚡ maze.co Automated unmoderated testing ⚡ sprig.com Survey and feedback analysis using AI 𝗪𝗵𝗮𝘁'𝘀 𝗻𝗲𝘅𝘁? Research is evolving. AI gives it speed. You bring the context, decisions, and direction. The best product teams don’t guess. They ask, listen, and learn. Then build. 📌 𝗪𝗮𝗻𝘁 𝗮 𝗳𝘂𝗹𝗹 𝗴𝘂𝗶𝗱𝗲? Product Map mapped the UX methods, tools, and templates 👇 https://lnkd.in/easzZpCD ♻️ Repost to help more product teams get closer to users 💙 Like if you’re already bringing UX research into your work 🛎️ Follow Matvey Bryksin for more practical tips 💬 What’s your main UX research method right now? Drop it in the comments!

If you're a UX researcher working with open-ended surveys, interviews, or usability session notes, you probably know the challenge: qualitative data is rich - but messy. Traditional coding is time-consuming, sentiment tools feel shallow, and it's easy to miss the deeper patterns hiding in user feedback. These days, we're seeing new ways to scale thematic analysis without losing nuance. These aren’t just tweaks to old methods - they offer genuinely better ways to understand what users are saying and feeling. Emotion-based sentiment analysis moves past generic “positive” or “negative” tags. It surfaces real emotional signals (like frustration, confusion, delight, or relief) that help explain user behaviors such as feature abandonment or repeated errors. Theme co-occurrence heatmaps go beyond listing top issues and show how problems cluster together, helping you trace root causes and map out entire UX pain chains. Topic modeling, especially using LDA, automatically identifies recurring themes without needing predefined categories - perfect for processing hundreds of open-ended survey responses fast. And MDS (multidimensional scaling) lets you visualize how similar or different users are in how they think or speak, making it easy to spot shared mindsets, outliers, or cohort patterns. These methods are a game-changer. They don’t replace deep research, they make it faster, clearer, and more actionable. I’ve been building these into my own workflow using R, and they’ve made a big difference in how I approach qualitative data. If you're working in UX research or service design and want to level up your analysis, these are worth trying.

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.