By Philip Burgess | UX Research Leader Understanding how users interact with products is essential for creating effective and intuitive designs. Task analysis and modeling methods offer UX researchers a structured way to break down user activities, identify pain points, and design solutions that fit real user needs. This post explores key task analysis techniques and modeling methods used in UX research, providing practical insights and examples to help you apply them effectively. Mapping user tasks on a whiteboard What is Task Analysis in UX Research? Task analysis involves studying how users perform specific tasks to achieve their goals. It focuses on understanding the steps users take, the decisions they make, and the challenges they face. This method helps uncover inefficiencies, confusion, or unnecessary complexity in workflows. By breaking down tasks into smaller components, UX researchers can identify opportunities to improve usability and streamline interactions. Task analysis is especially valuable when designing new features, improving existing interfaces, or creating user guides. Common Task Analysis Techniques Several techniques help researchers gather detailed information about user tasks. Here are some widely used methods: Hierarchical Task Analysis (HTA) HTA breaks down a task into a hierarchy of sub-tasks and operations. It starts with the main goal and divides it into smaller, manageable steps. This method clarifies the structure of complex tasks and highlights dependencies between steps. Cognitive Task Analysis (CTA) CTA focuses on the mental processes users engage in while performing tasks. It explores decision-making, problem-solving, and knowledge required. This technique often involves interviews and think-aloud protocols to capture users’ thought processes. Contextual Inquiry This method involves observing users in their natural environment while they perform tasks. Researchers ask questions and take notes to understand the context, tools, and challenges users encounter. Critical Incident Technique Users describe specific instances where they faced difficulties or succeeded in completing tasks. This helps identify critical moments that impact user experience. Modeling Methods to Visualize Tasks Once task data is collected, modeling methods help visualize and communicate findings clearly. These models guide design decisions and stakeholder discussions. Task Flow Diagrams Task flow diagrams map the sequence of steps users take to complete a task. They show the order of actions, decision points, and possible paths. These diagrams help identify unnecessary steps or loops that cause frustration. For example, a task flow for booking a flight might include searching for flights, selecting options, entering passenger details, and confirming payment. If users often abandon the process at payment, the diagram can highlight this step for further investigation. Use Case Diagrams Use case diagrams focus on interactions between users (actors) and the system. They describe what users want to achieve and how the system supports those goals. This method is useful for defining system requirements and ensuring the design meets user needs. GOMS Model GOMS stands for Goals, Operators, Methods, and Selection rules. It models user behavior by breaking down tasks into these components. GOMS helps predict how long tasks will take and where users might encounter difficulties. For example, in a text editing app, a goal might be to format a paragraph. Operators include clicking buttons or typing commands. Methods describe sequences of operators, and selection rules determine which method users choose. State Transition Diagrams These diagrams represent different states of a system and how users move between them based on actions. They are useful for interactive systems where the interface changes depending on user input. Practical Example: Improving an E-commerce Checkout Imagine a UX team analyzing the checkout process of an online store. They start with hierarchical task analysis to break down the checkout into steps: cart review, shipping information, payment, and confirmation. Next, they observe users through contextual inquiry and notice many abandon the process at the payment step. A task flow diagram reveals multiple redundant screens asking for the same information. Using this insight, the team redesigns the checkout to combine steps and simplify forms. They also create a state transition diagram to ensure smooth navigation between stages. After implementation, conversion rates improve significantly. Task flow diagram of e-commerce checkout process Tips for Effective Task Analysis and Modeling Engage real users Observing and interviewing actual users provides the most accurate insights. Focus on goals, not just actions Understanding why users perform tasks helps design better solutions. Keep models simple and clear Use diagrams that stakeholders can easily understand. Iterate and validate Update task models as you gather more data or test new designs. Combine methods Use multiple techniques to get a comprehensive view of user tasks.

By Philip Burgess | UX Research Leader Creating a product that looks good on paper is one thing. Making sure it works well for real users is another challenge entirely. Usability evaluation methods help bridge this gap by testing how actual people interact with a product. This process reveals issues that designers and developers might miss, ensuring the final product is intuitive, efficient, and satisfying to use. Understanding these methods is essential for anyone involved in product design, development, or management. This post explores key usability evaluation techniques, practical examples, and how to apply them effectively. User testing session with touchscreen device What Is Usability Evaluation? Usability evaluation measures how easy and pleasant a product is for users. It focuses on: Effectiveness : Can users complete their tasks accurately? Efficiency : How quickly can users finish tasks? Satisfaction : Do users feel comfortable and happy using the product? These evaluations help identify problems early, reduce costly redesigns, and improve user retention. Common Usability Evaluation Methods Several methods exist to assess usability, each with its strengths and best use cases. Here are some of the most widely used: 1. User Testing User testing involves observing real users as they interact with the product. Test participants perform specific tasks while evaluators watch for difficulties or confusion. Example: A team developing a mobile app asks 10 users to book a flight using the app. Observers note where users hesitate or make errors, then use this feedback to improve navigation and button placement. User testing provides direct insight into user behavior and uncovers unexpected issues. 2. Heuristic Evaluation Experts review the product against established usability principles, known as heuristics. Jakob Nielsen’s 10 heuristics are a popular framework, including rules like "visibility of system status" and "error prevention." Example: A website is evaluated by usability experts who identify that error messages are unclear and navigation labels are inconsistent. These findings guide targeted fixes. Heuristic evaluation is fast and cost-effective but depends on the evaluator’s expertise. 3. Surveys and Questionnaires After users interact with a product, surveys collect their opinions and satisfaction levels. Tools like the System Usability Scale (SUS) provide standardized scores. Example: After using a new software tool, users complete a SUS questionnaire rating ease of use. The average score helps the team benchmark usability against other products. Surveys complement observational methods by capturing subjective user feelings. 4. A/B Testing This method compares two versions of a product to see which performs better on usability metrics. Users are randomly assigned to either version, and their behavior is tracked. Example: An e-commerce site tests two checkout page designs. Version A has a simplified form, while Version B includes extra fields. Data shows Version A leads to faster checkouts and fewer abandoned carts. A/B testing provides quantitative data to support design decisions. 5. Cognitive Walkthrough Evaluators step through tasks as if they were users, asking if the user’s goals and actions are clear at each step. This method focuses on learnability for new users. Example: A team uses cognitive walkthroughs to assess a new software feature. They identify that users might not understand how to start the feature without additional guidance. This method helps improve onboarding and first-time user experience. When to Use Each Method Choosing the right usability evaluation method depends on the project stage, budget, and goals. | Stage | Recommended Methods | Purpose | |-------------------|-----------------------------------|---------------------------------| | Early Design | Heuristic Evaluation, Cognitive Walkthrough | Identify major usability issues before development | | Prototype Testing | User Testing, Surveys | Gather user feedback on design concepts | | Post-Launch | A/B Testing, Surveys | Optimize and refine based on real user data | Combining methods often yields the best results. For example, start with heuristic evaluation, then conduct user testing, and finally use surveys to measure satisfaction. Participant performing usability test on laptop Practical Tips for Effective Usability Evaluation Recruit representative users : Test with people who match your target audience to get relevant feedback. Define clear tasks : Give users specific goals to complete during testing to observe real interactions. Record sessions : Video or screen recordings help analyze behavior and share findings with the team. Avoid leading users : Let users explore naturally without guiding them to avoid bias. Iterate often : Usability evaluation is not a one-time event. Regular testing improves the product continuously. Real-World Example A popular streaming service wanted to improve its search feature. They conducted user testing with 15 participants who tried to find specific shows. Observers noticed users struggled with unclear filter options. The team redesigned the filters with clearer labels and added tooltips. Follow-up testing showed a 30% reduction in search time and higher user satisfaction scores. This example shows how usability evaluation directly impacts product success. Final Thoughts on Usability Evaluation Usability evaluation methods provide essential insights into how real users interact with products. By applying techniques like user testing, heuristic evaluation, and A/B testing, teams can create products that are not only functional but also enjoyable to use.

User experience (UX) research plays a crucial role in designing products that truly meet users’ needs. Yet, many teams struggle to decide which type of research to conduct at different stages of product development. Two main approaches—formative and summative UX research—serve distinct purposes and offer unique insights. Knowing when and how to use each can save time, reduce costs, and improve product success. This post breaks down the differences between formative and summative UX research, explains their goals, methods, and timing, and offers practical examples to help you apply them effectively. What Is Formative UX Research? Formative UX research happens early and throughout the design process. Its main goal is to inform and shape the product by identifying user needs, pain points, and opportunities for improvement. This type of research helps teams explore ideas, test prototypes, and refine designs before final development. Key Characteristics of Formative Research Conducted during early design stages or while iterating on prototypes Focuses on understanding user behavior, motivations, and challenges Uses qualitative methods such as interviews, usability testing, and contextual inquiry Helps uncover usability issues and design flaws before launch When to Use Formative Research When defining user requirements for a new product or feature To test wireframes, mockups, or prototypes and gather feedback To explore how users interact with a concept or workflow To identify unmet needs or pain points in existing products Example of Formative Research in Action Imagine a team designing a new mobile app for booking fitness classes. Early on, they conduct interviews and observe users trying a rough prototype. They discover users struggle to find classes by location and want clearer pricing info. This feedback leads the team to redesign the navigation and add pricing details before building the final version. Formative UX research session with user testing a mobile app prototype Formative UX research helps identify usability issues early by observing users interacting with prototypes. What Is Summative UX Research? Summative UX research takes place after the product or feature is mostly complete. Its purpose is to evaluate the overall user experience and measure how well the product meets its goals. This research validates design decisions and provides evidence for product success or areas needing improvement. Key Characteristics of Summative Research Conducted near or after product launch Focuses on measuring usability, satisfaction, and performance Uses quantitative methods like surveys, A/B testing, and analytics, often combined with usability testing Provides benchmarks and metrics to compare against goals or competitors When to Use Summative Research To assess if a product meets usability standards before release To compare different design versions or features To measure user satisfaction and task success rates To gather data for stakeholders on product effectiveness Example of Summative Research in Action A team launches a redesigned e-commerce website and wants to know if the checkout process is easier. They run a usability test with 50 participants and measure task completion rates, time on task, and user satisfaction scores. The results show a 20% improvement in checkout speed and higher satisfaction, confirming the redesign’s success. How Formative and Summative Research Work Together Both types of research are essential and complement each other. Formative research guides design decisions and helps avoid costly mistakes early. Summative research confirms whether those decisions achieved the desired results. Practical Tips for Combining Both Start with formative research to explore ideas and test prototypes. Use insights to refine designs and fix usability problems. Conduct summative research before launch to validate the final product. Repeat the cycle for continuous improvement based on user feedback. UX team reviewing summative research data from usability testing Summative UX research provides data-driven insights to evaluate product performance and user satisfaction. Choosing the Right Research Method for Your Project Selecting between formative and summative research depends on your project stage, goals, and resources. Here are some questions to guide your choice: Are you still exploring design options or refining concepts? Choose formative research. Do you need to measure how well the product works for users? Choose summative research. Is your timeline flexible enough to iterate based on feedback? Formative research fits best. Do you need to provide evidence of usability to stakeholders? Summative research is ideal. Summary Formative and summative UX research serve different but connected purposes. Formative research helps shape and improve designs early by uncovering user needs and usability issues. Summative research evaluates the final product’s effectiveness and user satisfaction with measurable data. Using both strategically throughout your design process leads to better products and happier users. Start with formative research to build a strong foundation, then confirm your success with summative research before launch. This approach ensures your product truly meets user expectations and business goals.

By Philip Burgess | UX Research Leader Usability testing is a key step in creating products that people find easy and enjoyable to use. It involves observing real users as they interact with a product to identify problems and areas for improvement. This process helps teams build better designs, reduce errors, and increase user satisfaction. Understanding the different methods of usability testing, the benefits it brings, and the right moments to apply it can transform how products meet user needs. User testing a touchscreen device in a controlled environment Methods of Usability Testing Usability testing comes in several forms, each suited to different goals and stages of product development. Here are the most common methods: 1. Moderated Usability Testing In moderated testing, a facilitator guides the user through tasks while observing and asking questions. This can happen in person or remotely via video calls. The moderator can clarify instructions, probe deeper into user thoughts, and adapt the session based on user behavior. Example: A software company invites users to their lab to complete specific tasks on a new app while a researcher watches and takes notes. 2. Unmoderated Usability Testing Users complete tasks on their own, often using a testing platform that records their screen and actions. This method allows for testing with many users quickly and at a lower cost. However, it lacks the immediate feedback and interaction of moderated sessions. Example: An e-commerce site sends a link to customers to test a new checkout process at home and collects data on where users struggle. 3. Remote Usability Testing Remote testing can be moderated or unmoderated and takes place with users in their natural environment. This method captures more realistic user behavior and can reach a wider audience. Example: A mobile app developer asks users worldwide to test a new feature from their phones and share their experience via video recordings. 4. A/B Testing While not a traditional usability test, A/B testing compares two versions of a design by measuring user interactions and preferences. It helps decide which design performs better in real-world conditions. Example: A website shows two different homepage layouts to visitors and tracks which one leads to more sign-ups. Benefits of Usability Testing Usability testing offers clear advantages that improve product quality and user experience: Identifies real user problems Testing reveals issues that designers and developers might overlook, such as confusing navigation or unclear instructions. Saves time and money Fixing usability problems early prevents costly redesigns after launch. Increases user satisfaction Products that are easy to use encourage repeat visits and positive reviews. Improves accessibility Testing with diverse users helps ensure the product works well for people with different abilities. Supports data-driven decisions Observing actual user behavior provides evidence to guide design choices instead of relying on assumptions. When to Use Usability Testing Knowing when to conduct usability testing maximizes its impact: Early in design Testing wireframes or prototypes helps catch major issues before development begins. Before launch Testing the final product ensures it meets user needs and functions as intended. After updates Testing new features or changes confirms they improve the experience without introducing new problems. When user complaints arise If users report difficulties, testing can pinpoint the cause and guide fixes. To compare options Testing different designs or workflows helps choose the best solution. Practical Tips for Effective Usability Testing Define clear goals Know what you want to learn from the test to design relevant tasks. Recruit representative users Select participants who match your target audience for meaningful feedback. Keep tasks realistic and focused Avoid overwhelming users with too many or artificial tasks. Observe without interfering Let users work naturally but be ready to ask clarifying questions if needed. Analyze results carefully Look for patterns in user behavior and feedback to identify key issues. Usability testing software displaying user interaction heatmaps and session recordings

By Philip Burgess | UX Research Leader Creating products that truly meet user needs while keeping pace with fast development cycles remains a challenge for many teams. Agile development has transformed how products are built by emphasizing flexibility and quick iterations. Yet, without integrating user experience (UX) research effectively, teams risk delivering features that miss the mark. Combining Agile with UX research helps teams build better products faster by continuously validating assumptions and adapting designs based on real user feedback. UX researcher reviewing user feedback during Agile sprint Why Agile and UX Research Must Work Together Agile focuses on delivering small, incremental improvements through short development cycles called sprints. This approach encourages rapid prototyping and frequent releases. However, Agile alone does not guarantee that what is built will satisfy users or solve their problems. UX research brings the user’s voice into the process by uncovering needs, behaviors, and pain points. It uses methods like interviews, usability testing, and surveys to gather insights. When UX research is integrated into Agile workflows, teams can: Validate ideas early before investing heavily in development Identify usability issues quickly and fix them in upcoming sprints Prioritize features based on real user value, not assumptions Reduce costly rework by catching problems sooner Without UX research, Agile teams risk building features that users find confusing or unnecessary, slowing down product adoption and success. Practical Ways to Integrate UX Research in Agile Incorporating UX research into Agile requires thoughtful planning and collaboration. Here are some effective strategies: 1. Include UX Researchers in Sprint Planning Invite UX researchers to sprint planning meetings to share recent findings and suggest user-focused priorities. This helps the team understand which features need validation or redesign. 2. Conduct Lightweight Research During Sprints UX research doesn’t have to be lengthy. Quick usability tests, short interviews, or remote surveys can fit into sprint cycles. For example, testing a prototype with 5 users can reveal major issues in a few days. 3. Use Research to Inform Backlog Prioritization Product owners can use UX insights to rank backlog items by user impact. Features that solve critical pain points should get higher priority. 4. Share Research Findings Regularly Create a culture of transparency by sharing UX research results with the whole team. Visual reports, video clips, or live demos help developers and designers understand user needs better. 5. Plan for Iterative Testing and Feedback Build time into sprints for testing new features with users and gathering feedback. This allows continuous improvement rather than waiting until the end of development. Real-World Example: Improving a Mobile App Experience A team developing a fitness tracking app used Agile but struggled with low user retention. They brought in UX researchers who conducted remote usability tests and interviews. The research revealed users found the onboarding confusing and the workout tracking interface cluttered. The team adjusted their sprint backlog to focus on redesigning onboarding and simplifying the interface. They tested prototypes with users every sprint. Within three months, the app’s retention rate improved by 25%, and user satisfaction scores increased significantly. This example shows how combining Agile with UX research leads to faster, more user-centered improvements. Digital prototype being tested for usability during Agile development Overcoming Common Challenges Teams often face obstacles when merging Agile and UX research: Time constraints: Agile sprints are short, making it hard to fit research in. Solution: Use rapid research methods and plan research activities ahead. Communication gaps: Developers may not fully understand research insights. Solution: Use clear, visual summaries and involve the whole team in research discussions. Balancing speed and quality: Pressure to deliver quickly can reduce focus on user needs. Solution: Emphasize that user validation saves time by preventing rework. By addressing these challenges, teams can create a smooth workflow that values both speed and user experience. Key Benefits of Combining Agile and UX Research Faster problem detection: Catch usability issues early before they become costly. Better product-market fit: Build features users actually want and need. Increased team alignment: Everyone understands user goals and works toward them. Reduced development waste: Avoid building unnecessary or confusing features. Continuous learning: Each sprint delivers new insights to improve the product. Teams that embrace this approach often see improved customer satisfaction and stronger business results. Building better products faster requires more than just rapid coding. It demands a deep understanding of users combined with flexible development. Integrating UX research into Agile workflows creates a powerful cycle of learning and improvement. Teams that listen to users continuously and adapt quickly can deliver products that truly resonate and succeed in the market.

By Philip Burgess | UX Research Leader Mentoring and coaching junior UX researchers plays a crucial role in shaping the future of user experience design. As the demand for skilled UX professionals grows, organizations must invest in developing new talent who can navigate complex research challenges and deliver meaningful insights. This post explores practical ways to support junior researchers, helping them build confidence, sharpen skills, and contribute effectively to projects. A UX researcher mentoring a junior colleague on user journey mapping Understanding the Needs of Junior UX Researchers Junior UX researchers often enter the field with theoretical knowledge but limited hands-on experience. They may struggle with: Designing effective research plans Choosing appropriate methods for different projects Analyzing qualitative and quantitative data Communicating findings clearly to stakeholders Mentors and coaches must recognize these challenges and tailor their support accordingly. Listening carefully to juniors’ questions and concerns helps identify gaps in knowledge and confidence. This understanding forms the foundation for a productive mentoring relationship. Creating a Supportive Learning Environment A positive learning environment encourages junior researchers to ask questions, experiment, and learn from mistakes. Here are some ways to foster this atmosphere: Schedule regular one-on-one sessions to discuss ongoing projects and challenges Encourage open dialogue without judgment or criticism Share personal experiences and lessons learned to normalize setbacks Provide constructive feedback focused on growth rather than fault-finding When juniors feel safe to explore ideas and receive honest feedback, they develop resilience and a growth mindset essential for long-term success. Practical Coaching Techniques for Skill Development Coaching junior UX researchers requires a hands-on approach that balances guidance with independence. Effective techniques include: Shadowing and Observation: Invite juniors to observe research sessions, note-taking, and analysis to learn best practices. Pair Researching: Work together on small tasks such as drafting interview questions or coding data to build confidence. Role-playing: Simulate stakeholder presentations or user interviews to practice communication skills. Project Ownership: Gradually assign responsibility for parts of a project, allowing juniors to lead while mentors provide support. These methods help juniors gain practical experience and develop critical thinking skills needed to handle real-world research challenges. Encouraging Critical Thinking and Reflection Mentoring is not just about teaching methods but also about cultivating a mindset that questions assumptions and seeks deeper understanding. Encourage juniors to: Reflect on why certain research methods are chosen Analyze the strengths and limitations of their findings Consider how insights impact design decisions and user outcomes Seek feedback from multiple sources, including users and team members Reflection sessions can be informal discussions or written journals. This practice strengthens analytical skills and promotes continuous learning. Detailed UX research notes and sketches on a desk during a mentoring session Building Communication and Collaboration Skills UX research does not happen in isolation. Junior researchers must learn to communicate effectively with designers, product managers, and developers. Mentors can support this by: Encouraging clear, concise reporting of research findings Teaching storytelling techniques to make data relatable Facilitating introductions to cross-functional teams Modeling active listening and empathy in meetings Strong communication skills help junior researchers advocate for users and influence product decisions positively. Measuring Progress and Celebrating Achievements Tracking growth motivates junior researchers and helps mentors adjust their approach. Consider: Setting clear, achievable goals for skill development Reviewing progress regularly with specific examples Recognizing improvements publicly within the team Encouraging juniors to share their successes and challenges Celebrating milestones builds confidence and reinforces the value of mentoring relationships. Supporting Career Growth Beyond Initial Training Mentoring should extend beyond immediate projects to include career guidance. Help juniors explore: Specializations within UX research such as usability testing, ethnography, or data analysis Opportunities for further education, workshops, or conferences Building a professional network through events and online communities Preparing for future roles with leadership or strategic responsibilities This long-term perspective ensures junior researchers remain engaged and continue growing as valuable contributors. Mentoring and coaching junior UX researchers requires patience, empathy, and practical strategies. By creating a supportive environment, offering hands-on guidance, and encouraging reflection, mentors help build confident researchers who can tackle complex challenges. Investing in the next generation of UX talent strengthens teams and drives better user experiences. Organizations and senior professionals should prioritize mentoring as a key part of their growth strategy to ensure a thriving UX community.

By Philip Burgess | UX Research Leader When product owners doubt the value of UX research, teams often face roadblocks that slow progress and reduce product quality. UX research provides critical insights into user needs, behaviors, and pain points. Without it, products risk missing the mark, leading to wasted resources and frustrated users. This post explores common challenges when product owners undervalue UX research and offers practical ways to address them. Team collaborating on user experience insights Why Some Product Owners Undervalue UX Research Understanding the root causes helps tailor solutions. Some common reasons include: Focus on speed and deadlines : Product owners may prioritize quick releases over thorough research, seeing UX research as a time-consuming luxury. Lack of awareness : They might not fully understand what UX research entails or how it benefits the product. Budget constraints : Research can seem like an added cost with unclear immediate returns. Overconfidence in assumptions : Product owners sometimes rely on their own experience or intuition instead of user data. Recognizing these reasons helps teams approach the issue with empathy and targeted strategies. Challenges Faced When UX Research Is Undervalued When product owners do not support UX research, teams often encounter: Limited user insights : Without research, teams guess user needs, increasing the risk of building features no one wants. Reduced product quality : Lack of user feedback leads to usability issues and poor user satisfaction. Lower team morale : UX researchers may feel undervalued, which affects collaboration and creativity. Inefficient resource use : Time and money spent on features that don’t solve real problems. These challenges can stall product success and damage the team’s ability to deliver value. How to Demonstrate the Value of UX Research Showing clear benefits can shift product owners’ perspectives. Try these approaches: Share success stories : Present case studies where UX research improved product outcomes, such as increased user engagement or reduced support tickets. Use quick wins : Conduct small, fast research activities like usability tests or surveys that provide immediate, actionable insights. Quantify impact : Translate research findings into numbers, such as potential revenue gains or cost savings from avoiding redesigns. Involve product owners : Invite them to observe user sessions or review findings firsthand to build empathy with users. For example, a team once ran a 2-day usability test that uncovered a confusing checkout flow. Fixing it increased conversions by 15%, a clear win that convinced the product owner to invest more in research. Integrating UX Research into Agile Workflows Many product owners worry UX research slows down agile development. To address this: Embed research in sprints : Plan research activities early in the sprint cycle to inform design and development. Use lightweight methods : Employ guerrilla testing or remote surveys that fit tight timelines. Prioritize research questions : Focus on the most critical user issues to maximize impact. Communicate clearly : Share concise summaries and visuals that highlight key findings without overwhelming stakeholders. This approach keeps research aligned with delivery goals and shows it as a tool for faster, smarter decisions. UX researcher reviewing user journey maps to identify pain points Building a Culture That Values UX Research Long-term change requires cultural shifts within the product team and organization: Educate stakeholders : Run workshops or lunch-and-learns to explain UX research methods and benefits. Celebrate research wins : Highlight how research led to product improvements in team meetings or newsletters. Create shared goals : Align UX research objectives with business outcomes to show relevance. Encourage collaboration : Foster open communication between product owners, designers, and researchers. When everyone sees UX research as a shared responsibility, it becomes a natural part of the product process. Practical Tips for UX Researchers Working with Skeptical Product Owners Speak their language : Frame research findings in terms of business impact, user retention, or cost reduction. Be concise and visual : Use charts, videos, or prototypes to make insights clear and memorable. Offer alternatives : Suggest research methods that fit the project’s constraints. Build trust gradually : Start with small research efforts and expand as confidence grows. For example, instead of presenting a long report, a researcher might share a 3-minute video of users struggling with a feature, which can be more persuasive.

Making the jump from being a hands-on UX researcher to managing a UX research team changes everything. It is not just a new job title but a shift in how you think, what you focus on, and how you measure success. Instead of producing research yourself, your role becomes about helping your team deliver their best work and shaping the bigger picture. This change can feel overwhelming at first. The skills that made you a great researcher are still important, but now you also need to lead people, influence strategy, and navigate complex organizational dynamics. Here are some of the most valuable lessons learned by those who have made this transition. A UX research manager guiding a team member during a one-on-one coaching session Your Output Becomes Your People As an individual contributor, your value was clear: the quality of your research reports and insights. When you become a manager, your success depends on how well your team performs. This means shifting your mindset from asking: What research am I producing? to How am I enabling my team to deliver their best work? Supporting your team might mean removing obstacles that slow them down, helping them communicate with stakeholders, or guiding them to prioritize projects that align with business goals. For example, if a team member struggles to get buy-in from product managers, your role is to coach them on effective communication or step in to advocate for the research yourself. UX Research Soft Skills Become Your Hard Skills In management, technical expertise alone won’t carry you. Building relationships and influencing others become your most important skills. You need to: Build trust with cross-functional partners like product, design, and engineering Advocate for the value of research with company leaders Resolve conflicts within your team to keep morale and productivity high Empathy and active listening help you understand your team’s challenges and motivations. Strategic communication allows you to explain research value clearly and align it with business priorities. For instance, when a stakeholder questions the need for a study, your ability to explain how it supports product goals can make the difference. Strategy Matters as Much as Execution As a manager, you join conversations about product direction and business priorities. Your role includes: Ensuring research efforts align with company goals Helping shape the product roadmap based on user needs Protecting time and resources for studies that have the biggest impact This means thinking beyond the current sprint or quarter. You might plan research themes for the next six months or a year, anticipating what questions will be most important. For example, if the company plans to enter a new market, you can prepare your team to explore user needs in that area ahead of time. Close-up view of a UX research strategy board with notes and maps Let Go of the Perfect Study Mindset As a researcher, you might have aimed for the perfect study—flawless design, comprehensive data, and clear conclusions. As a manager, this mindset can hold you back. You need to balance quality with speed and impact. Sometimes a quick, focused study that informs a decision is more valuable than a lengthy, detailed report. Encourage your team to deliver insights that are good enough to move the product forward, even if they are not perfect. This approach helps the team stay agile and responsive to changing priorities. Embrace Coaching and Development Your team’s growth becomes your priority. This means investing time in one-on-one meetings, providing constructive feedback, and creating opportunities for learning. For example, you might pair junior researchers with more experienced ones or organize workshops on stakeholder communication. Supporting career development also means recognizing individual strengths and helping team members find roles where they can excel. When people feel valued and challenged, they produce better work and stay motivated. Navigate Organizational Dynamics Managing UX research means working across departments and sometimes pushing back on competing priorities. You need to understand how decisions are made and who the key influencers are. Building alliances with product managers, designers, and executives helps you secure resources and support for your team. For example, if engineering deadlines threaten to cut research time, you might negotiate a compromise that preserves critical studies while respecting delivery schedules. Being a strong advocate for research requires diplomacy and persistence. Stepping into UX research management is a rewarding but challenging journey. Your focus shifts from individual output to enabling your team’s success, from technical skills to relationship-building, and from execution to strategy. By embracing these lessons, you can lead your team to deliver research that truly shapes products and delights users.

By Philip Burgess - UX Research Leader Summary Philip Burgess led the creation and implementation of a structured UX research and optimization framework that translated user insights into measurable business outcomes. By connecting ROI modeling with a repeatable rollout process, this initiative empowered global teams to prioritize high-impact UX improvements, accelerate experimentation, and drive millions in revenue. Challenge Nu Skin’s digital teams needed a way to scale UX research across markets while ensuring that every initiative was tied to business value. The challenge was to: Quantify the financial impact of UX improvements Prioritize initiatives based on ROI potential Create a repeatable rollout process for global adoption Strategic Framework 1. ROI Modeling Developed a proprietary ROI calculator to estimate revenue impact from UX improvements Modeled conversion rate lift scenarios (e.g., 5%, 10%, 20%) to forecast gains ranging from $78M to $312M annually Used baseline analytics data to validate assumptions and align stakeholders 2. Prioritization Matrix Created a decision-making framework to evaluate UX opportunities based on effort vs. impact Mapped usability issues to business KPIs—conversion, cart abandonment, bounce rate, support volume Enabled data-driven prioritization across teams and regions 3. Rollout Process Steps Outlined a clear, repeatable process for executing UX research and optimization initiatives: Step Description 1. Identify Opportunity Use analytics, heatmaps, and user feedback to spot friction points 2. Estimate ROI Apply the ROI calculator to forecast financial impact 3. Design & Test Create prototypes and run A/B or usability tests 4. Validate & Iterate Analyze results, refine designs, and retest if needed 5. Roll Out Globally Deploy winning solutions across markets with localized adjustments 6. Monitor & Optimize Track KPIs post-launch and feed insights into future cycles 4. Enablement & Governance Created templates, dashboards, and training materials to empower teams Established governance protocols to ensure consistency and quality Fostered cross-functional collaboration between UX, Product, Analytics, and Engineering Results Accelerated Time-to-Impact : Reduced rollout timelines by 40% through standardized processes Revenue Growth : Enabled initiatives that contributed to $4.8M in incremental revenue in 6 months Global Scalability : Framework adopted across all regions, supporting 160+ UX projects Team Empowerment : Increased UX maturity and autonomy across product teams Strategic Impact This initiative transformed UX research from a tactical function into a strategic growth engine. By linking every design decision to ROI and embedding a repeatable rollout process, Philip enabled Nu Skin to scale experimentation, reduce friction, and deliver user-centered experiences that drive business success.

By Philip Burgess | UX Research Leader Presenting UX research findings to executive stakeholders can be challenging. Executives often have limited time and focus on high-level outcomes rather than detailed data. To make your research impactful, you need to communicate clearly, highlight key insights, and connect your findings to business goals. This post explains how to present UX research results effectively to executives, ensuring your work influences decisions and drives product improvements. Clear UX research summary on tablet Understand Your Audience and Their Priorities Executives care about how UX research affects the business. Before your presentation, learn what matters most to them. Are they focused on increasing customer retention, reducing support costs, or speeding up product launches? Tailor your message to these priorities. Use simple language and avoid jargon. Executives may not be familiar with UX terms or methods, so explain concepts briefly and clearly. For example, instead of saying “heuristic evaluation,” say “expert review to find usability issues.” Focus on Key Insights and Business Impact When Presenting UX Research Findings Executives want to know what the research means for the company. Highlight the most important findings that relate to business goals. Use these strategies: Present top 3 to 5 insights that have clear implications. Show how these insights affect user satisfaction, conversion rates, or other metrics. Use concrete examples or quotes from users to make findings relatable. Avoid overwhelming them with raw data or lengthy reports. For example, if research shows users struggle with the checkout process, explain how this causes cart abandonment and lost revenue. Suggest improvements based on your findings. Use Visuals to Make Data Easy to Understand Visual aids help executives grasp complex information quickly. Use charts, graphs, and diagrams that highlight trends and comparisons. Keep visuals simple and focused on one message each. Consider these tips: Use bar charts or pie charts for quantitative data. Include screenshots or annotated images to illustrate usability problems. Use color coding to emphasize positive or negative trends. Avoid cluttered slides or tables with too many numbers. Visuals should support your story, not distract from it. Tell a Story That Connects Research to Action Structure your presentation like a story with a clear beginning, middle, and end: Set the context : Briefly explain the research goals and methods. Present findings : Share key insights with supporting visuals. Explain impact : Connect findings to business outcomes. Recommend next steps : Suggest specific actions or experiments. This narrative helps executives follow your logic and see the value of UX research. Keep Presentations Short and Interactive Executives have limited time. Aim for 15 to 20 minutes, focusing on the essentials. Leave time for questions and discussion. Encourage interaction by asking for their input or concerns. This shows respect for their perspective and helps align UX work with business needs. Provide a Clear Summary and Follow-Up Materials End your presentation with a concise summary slide that recaps the main points and recommended actions. This reinforces your message. After the meeting, share a brief report or one-pager with key findings and next steps. This allows executives to revisit the information and share it with others. Printed UX research summary report with charts Example: Presenting Usability Testing Results Imagine you conducted usability testing on a mobile app. Your key findings include: Users struggled to find the search bar, causing frustration. The onboarding process took too long, leading to drop-offs. Users liked the personalized recommendations feature. To present this to executives: Start by stating the goal: improve user engagement. Show a chart of task success rates before and after redesign. Share a user quote about difficulty finding the search bar. Explain how simplifying onboarding could increase retention by 10%. Recommend redesigning the search bar placement and shortening onboarding. This approach links research to clear business benefits. Final Thoughts Presenting UX research findings to executive stakeholders requires clarity, focus, and relevance. By understanding their priorities, highlighting key insights, using visuals, and telling a compelling story, you can make your research influence decisions. Keep presentations concise and interactive, and provide follow-up materials for ongoing impact.

By Philip Burgess | UX Research Leader User experience research often feels like a costly endeavor, requiring expensive tools, professional testers, and extensive resources. But what if you could gather valuable insights without spending any money? This post explores practical ways to conduct UX research on a tight or nonexistent budget. You will learn how to tap into free resources, leverage your network, and use simple methods that deliver meaningful results. Collecting user feedback through a basic online form Start with What You Have Before looking for external tools or participants, assess the resources already available to you. Your existing users, colleagues, and social networks can provide a wealth of information. Use your current user base : If you have a website or app, add a short feedback form or survey. Tools like Google Forms or Typeform offer free plans that are easy to set up. Ask colleagues or friends to test : Even non-experts can spot usability issues. Ask them to complete tasks while you observe or record their screen. Review existing data : Check analytics platforms like Google Analytics for user behavior patterns. Look for pages with high drop-off rates or unexpected navigation paths. These steps require no budget but can reveal key pain points and opportunities for improvement. Conduct Guerrilla Testing Guerrilla testing means approaching people in public places or online communities to get quick feedback. It’s fast, informal, and free. In-person guerrilla testing : Visit a café, library, or coworking space and ask strangers to try your product for a few minutes. Offer a small token of appreciation like a coffee. Online guerrilla testing : Post requests in forums, social media groups, or platforms like Reddit. Be clear about what you want and how long it will take. Keep tests short and focused : Limit tasks to 5-10 minutes to respect participants’ time and get concise feedback. This method helps you gather diverse opinions and observe real user interactions without formal recruitment. Use Free Remote Testing Tools for UX Research Several free tools allow you to conduct remote usability tests and interviews without spending money. Lookback.io offers a free tier for recording user sessions and interviews. Hotjar provides heatmaps and session recordings on a limited free plan. Microsoft Teams or Zoom can be used for remote interviews and screen sharing. Google Forms or SurveyMonkey help collect structured feedback. Combine these tools with your own recruitment efforts to reach users anywhere and gather detailed insights. Documenting UX research findings with notes and sketches Analyze Competitors and Similar Products Studying competitors or similar products can reveal what works well and what doesn’t. This indirect research requires no budget but sharp observation. Use competitor products yourself : Note features, navigation, and design elements that stand out. Read user reviews : Check app stores, forums, and social media for user complaints and praises. Map user journeys : Sketch how users move through competitor products to identify common patterns or gaps. This approach helps you benchmark your product and find inspiration for improvements. Leverage Social Media and Online Communities Online communities are rich sources of user opinions and discussions. Join relevant forums and groups : Platforms like Reddit, Discord, or specialized forums often have active users willing to share feedback. Ask open-ended questions : Encourage detailed responses about pain points or desired features. Observe conversations : Monitor threads related to your product or industry to spot trends and unmet needs. Engaging authentically in these spaces builds trust and uncovers insights you might miss with formal research. Document and Share Your Findings Collecting data is only useful if you organize and communicate it clearly. Create simple reports or presentations : Summarize key findings with screenshots, quotes, and charts. Use visual aids : Diagrams, user journey maps, and annotated screenshots help stakeholders understand issues. Prioritize issues : Highlight the most critical problems to address first based on impact and effort. Clear documentation ensures your research influences design decisions and product improvements.

By Philip Burgess | UX Research Leader User experience research shapes how products meet real user needs. Senior UX researchers carry the responsibility of guiding teams with insights that improve design and functionality. Yet, even experienced professionals can fall into common traps that limit their impact. Recognizing these pitfalls helps senior researchers sharpen their approach and deliver stronger results. Senior UX researcher reviewing user feedback data Overlooking the Value of Cross-Functional Collaboration in UX Research Senior UX researchers often work closely with designers and product managers. Still, one frequent mistake is isolating research from other teams. When research insights are siloed, they lose influence and fail to shape product decisions effectively. How to avoid this: Schedule regular meetings with design, development, and product teams to share findings. Involve stakeholders early in the research planning process to align goals. Translate research insights into clear, actionable recommendations tailored for each team. For example, a senior researcher at a software company improved collaboration by hosting weekly “insight sessions” where teams discussed user pain points and brainstormed solutions together. This practice increased buy-in and accelerated product improvements. Relying Too Much on Quantitative Data Alone Numbers and statistics provide valuable evidence, but senior UX researchers sometimes depend excessively on quantitative data. This approach can miss the nuances of user behavior and motivations that qualitative methods reveal. How to avoid this: Balance surveys and analytics with interviews, usability tests, and field observations. Use storytelling to bring qualitative insights to life for stakeholders. Combine data types to create a fuller picture of user experience. A senior researcher working on an e-commerce platform found that quantitative data showed high cart abandonment rates but did not explain why. By conducting user interviews, they uncovered confusion around shipping costs, leading to a redesign that boosted conversions. Ignoring the Context of Use Understanding where and how users interact with a product is crucial. Senior researchers sometimes focus narrowly on tasks or screens without considering the broader environment or emotional state of users. How to avoid this: Conduct contextual inquiries or field studies to observe users in their natural settings. Ask questions about users’ goals, frustrations, and routines beyond the product. Consider external factors like device type, location, and time constraints. For instance, a senior UX researcher studying a mobile app for public transit riders discovered that many users accessed the app during short waits at bus stops. This insight led to simplifying key features for quick interactions. Failing to Communicate Research Findings Clearly Even the best research loses value if it is not communicated effectively. Senior UX researchers sometimes present data in overly technical language or dense reports that stakeholders struggle to understand. How to avoid this: Use visuals like charts, personas, and journey maps to illustrate key points. Keep presentations concise and focused on business impact. Tailor communication style to the audience, whether executives or developers. One senior researcher improved stakeholder engagement by creating short video summaries of usability tests, making findings more relatable and memorable. Detailed user journey map with annotations and key touchpoints Neglecting to Update Research Methods The field of UX research evolves rapidly. Senior researchers can fall into routines, using the same methods without adapting to new tools, technologies, or user behaviors. How to avoid this: Stay informed about emerging research techniques and software. Experiment with remote testing, eye-tracking, or AI-assisted analysis. Seek feedback from peers and attend industry events to refresh skills. For example, a senior researcher integrated remote usability testing during the pandemic, which expanded participant diversity and improved study efficiency. Overconfidence in Personal Assumptions Experience builds intuition, but senior UX researchers sometimes rely too heavily on their own assumptions rather than validating them with users. This can lead to biased conclusions and missed opportunities. How to avoid this: Approach every project with curiosity and openness. Use hypotheses as starting points, not facts. Test assumptions rigorously with real users. A senior researcher once assumed users preferred a minimalist interface. Testing revealed that some users wanted more guidance, prompting a redesign that balanced simplicity with helpful cues. Senior UX researchers hold a key role in shaping user-centered products. Avoiding these common mistakes strengthens their impact and helps teams build better experiences. By fostering collaboration, balancing data types, understanding context, communicating clearly, updating methods, and challenging assumptions, senior researchers can lead with confidence and clarity.