By Philip Burgess | UX Research Leader When I first started applying for UX research roles, I struggled with how to present my skills effectively. I wondered if a dedicated skills section was necessary or if my experience and projects spoke for themselves. Over time, I realized that a well-crafted skills section not only highlights your capabilities but also helps recruiters quickly understand your strengths. In this post, I’ll share why UX researchers should include a skills section on their resumes and what to include to make it stand out. A UX researcher's workspace showing notes and a laptop Why UX Researchers Need a Skills Section Recruiters and hiring managers often skim resumes in seconds. A clear skills section acts as a quick reference, allowing them to see your core competencies without digging through paragraphs. For UX researchers, this is especially important because the role combines diverse abilities—from qualitative research to data analysis and user testing. Without a skills section, your resume might miss the chance to highlight specific tools or methods you excel at. For example, mentioning proficiency in usability testing software or experience with statistical analysis tools can set you apart. It also helps applicant tracking systems (ATS) identify your resume as relevant when scanning for keywords. What to Include in a UX Research Skills Section A skills section should be concise but comprehensive. Here are the key elements I recommend including: Research Methods List the qualitative and quantitative methods you use regularly, such as interviews, surveys, usability testing, ethnographic studies, or A/B testing. Tools and Software Mention tools like UserTesting, Optimal Workshop, SPSS, R, or even design tools like Figma or Sketch if you use them for prototyping or analysis. Data Analysis Skills Highlight your ability to analyze data, whether through statistical software, Excel, or coding languages like Python or SQL. Communication and Collaboration UX research is about sharing insights clearly. Include skills like report writing, presenting findings, and working with cross-functional teams. User-Centered Design Principles Show your understanding of design thinking, accessibility standards, and how you apply user feedback to improve products. How to Format Your Skills Section I found that organizing skills into categories makes the section easier to scan. For example: Research Methods User interviews, usability testing, surveys, ethnographic research Tools UserTesting, Optimal Workshop, SPSS, Figma Data Analysis Statistical analysis, Excel, Python basics Communication Report writing, presentations, stakeholder collaboration This format helps recruiters quickly find the skills they care about. Avoid long lists without structure, as they can be overwhelming and less effective. Examples of Skills to Avoid and Include When I first wrote my skills section, I included generic terms like "good communication" or "team player." These phrases are vague and don’t add much value. Instead, focus on specific, demonstrable skills. Avoid: Good communication Team player Hardworking Include: Conducting moderated user interviews Presenting research findings to product teams Collaborating with designers and developers This approach shows what you actually do, not just how you describe yourself. Close-up of a UX research report showing charts and handwritten notes Personal Story: How a Skills Section Helped Me Land My Last Job When I updated my resume for my last job application, I added a detailed skills section based on the job description. I included tools and methods mentioned in the posting and highlighted my experience with mixed-method research. Within days, I got a call for an interview. During the interview, the hiring manager referenced my skills section and asked specific questions about my experience with usability testing platforms and data analysis. Having those skills clearly listed made it easier to steer the conversation toward my strengths. Final Tips for Crafting Your Skills Section Tailor your skills to each job application. Use keywords from the job description. Keep the section concise—aim for 6 to 12 skills grouped logically. Be honest about your proficiency. Don’t list skills you’re not comfortable discussing. Use bullet points or short phrases for easy reading. Update your skills regularly as you learn new tools or methods. A well-written skills section can make your resume more effective and help you stand out in a competitive field.

By Philip Burgess | UX Research Leader I’ve spent years working in UX research, and one thing I’ve learned is that not all research methods are created equal. Sometimes, the very tools we rely on to understand users can give us a misleading sense of certainty. This false confidence can lead teams down the wrong path, wasting time and resources on solutions that don’t actually meet user needs. In this post, I want to share my experience with how certain UX research methods can create this illusion of clarity. I’ll explain why it happens, give examples from real projects, and suggest ways to avoid falling into this trap. A UX researcher reviewing user feedback data on a laptop Why False Confidence Happens in UX Research UX research methods are designed to gather insights about users’ behaviors, needs, and pain points. But sometimes, the way we conduct or interpret these methods can create a false sense of confidence. Here are a few reasons why: Small or unrepresentative samples When a study includes only a handful of users or a narrow demographic, the results may not reflect the broader audience. Teams might assume the findings apply universally, which can be misleading. Overreliance on quantitative data Numbers can feel objective and clear, but metrics alone don’t tell the whole story. For example, a high click-through rate might look good, but it doesn’t reveal if users are frustrated or confused. Ignoring context and nuance UX research often simplifies complex human behavior into charts and graphs. Without understanding the context behind user actions, teams might misinterpret what the data really means. Confirmation bias Sometimes, researchers or stakeholders focus on data that supports their assumptions and overlook contradictory evidence. This selective attention reinforces false confidence. A Personal Story of False Confidence Early in my career, I worked on a mobile app redesign. We conducted a usability test with 5 users, which is a common practice. The test showed that users could complete key tasks quickly and without errors. The team celebrated the results and moved forward with the design. But after launch, user complaints started pouring in. People found the app confusing and hard to navigate. What went wrong? Looking back, I realized the usability test sample was too small and didn’t include users with varying levels of tech experience. We also focused too much on task completion time and ignored users’ emotional reactions and comments. The test gave us confidence that the design worked, but it missed critical issues. This experience taught me to question research results and dig deeper, especially when the findings seem too good to be true. How to Avoid False Confidence in UX Research Avoiding false confidence requires a thoughtful approach to research design and interpretation. Here are some practical tips I’ve found helpful: Use Mixed Methods Combine qualitative and quantitative research to get a fuller picture. For example, pair surveys with in-depth interviews or usability tests with analytics data. This helps balance numbers with user stories and emotions. Recruit Diverse Participants Make sure your sample reflects the diversity of your user base. Include different ages, backgrounds, skill levels, and contexts of use. This reduces the risk of missing important perspectives. Focus on User Context Don’t just measure what users do—understand why they do it. Observe users in their natural environment when possible, and ask open-ended questions to uncover motivations and frustrations. Challenge Your Assumptions Encourage your team to question findings and look for contradictory evidence. Use techniques like devil’s advocate sessions or peer reviews to avoid groupthink. Iterate and Validate Treat research as an ongoing process, not a one-time check. Test early and often, and validate findings with multiple rounds of research. This helps catch issues before they become costly problems. A UX team collaborating around a whiteboard with user journey maps Examples of Research Methods That Can Mislead Some UX research methods are more prone to creating false confidence if used improperly: Surveys with leading questions Poorly worded surveys can push users toward certain answers, skewing results. Unmoderated usability tests Without a facilitator, users might misunderstand tasks or skip important feedback. A/B testing without context A winning variant in an A/B test might perform better on one metric but harm overall user satisfaction. Heatmaps and click tracking alone These show where users click but not why, which can lead to incorrect conclusions. Final Thoughts UX research is a powerful tool, but it’s not foolproof. False confidence can creep in when we rely too heavily on limited data, ignore context, or fail to question our assumptions. The key is to approach research with humility and curiosity, always looking for a deeper understanding of users. If you’re a UX researcher or designer, take time to reflect on your methods and results. Ask yourself if you might be seeing what you want to see instead of what’s really there. By doing so, you’ll build stronger products that truly meet user needs and avoid costly mistakes. Remember, research is not about finding quick answers but about uncovering the right questions.

By Philip Burgess | UX Research Leader User experience (UX) research shapes how products and services meet real user needs. But with so many types of UX research, it can be confusing to know which method fits your project. I’ve worked on several design projects where choosing the right research approach made all the difference. In this post, I’ll walk you through the main types of UX research, explain when to use each, and share best practices to get the most from your efforts. UX researcher reviewing user feedback Understanding UX Research Types: Generative Research: Creating Ideas from Scratch Generative research helps uncover user needs, motivations, and pain points before you start designing. It’s about gathering insights that inspire new ideas and solutions. When to Use Generative Research At the very beginning of a project When exploring new markets or user groups To identify unmet needs or opportunities Common Methods Interviews Ethnographic studies Diary studies Contextual inquiries Best Practices Ask open-ended questions to encourage storytelling Observe users in their natural environment for authentic insights Avoid leading questions that bias responses For example, when redesigning a fitness app, I conducted interviews and shadowed users during workouts. This revealed frustrations with tracking progress and motivated features that users wanted, which shaped the app’s new direction. Discovery Research: Understanding the Problem Space Discovery research digs deeper into user behaviors and attitudes to define the problem clearly. It helps teams align on what to solve. When to Use Discovery Research After generative research or when you have a rough idea To validate assumptions about users and their challenges To prioritize features based on real needs Common Methods Surveys Focus groups Competitive analysis User journey mapping Best Practices Use quantitative data to support qualitative insights Involve cross-functional teams to get diverse perspectives Keep surveys concise to improve response rates In one project, discovery research helped us realize that users struggled most with onboarding. This shifted our focus from adding features to simplifying the first-time experience. Exploratory Research: Testing Concepts Early Exploratory research evaluates early concepts or prototypes to gather feedback and refine ideas before full development. When to Use Exploratory Research When you have initial designs or prototypes To test usability and user reactions To identify potential issues early Common Methods Usability testing with wireframes or mockups A/B testing Card sorting Best Practices Test with real users who match your target audience Focus on key tasks to keep sessions manageable Encourage honest feedback, including negative comments For example, testing a new checkout flow with users revealed confusing steps that we simplified before launch, improving conversion rates. User testing a mobile app prototype Evaluative Research: Measuring Effectiveness Evaluative research measures how well a product or feature performs against goals. It often happens after development or during iterations. When to Use Evaluative Research After launching a product or feature To compare different versions or designs To track improvements over time Common Methods Usability testing with live products Analytics review Heatmaps and click tracking Best Practices Define clear success metrics before testing Combine qualitative and quantitative data for a full picture Test regularly to catch issues early In one case, evaluative research showed that users were dropping off at a specific step in a signup process. We redesigned that step and saw a 20% increase in completions. Formative Research: Guiding Design Decisions Formative research supports design by providing ongoing feedback during development. It helps shape the product as it evolves. When to Use Formative Research Throughout the design and development phases To test features as they are built To refine user flows and interactions Common Methods Iterative usability testing Prototype walkthroughs Expert reviews Best Practices Test small changes frequently rather than waiting for big releases Involve designers and developers in sessions to foster collaboration Document findings clearly to inform decisions For example, during a website redesign, formative research helped the team adjust navigation labels and button placements, improving clarity and ease of use. Summative Research: Confirming Success Summative research evaluates the final product to confirm it meets user needs and business goals. It often serves as a final check before wider release. When to Use Summative Research At the end of a project or major release To validate overall usability and satisfaction To benchmark against competitors or previous versions Common Methods Large-scale usability testing Surveys measuring satisfaction and Net Promoter Score (NPS) Performance analytics Best Practices Use representative samples of your user base Focus on key performance indicators aligned with goals Share results with stakeholders to guide future work In one project, summative research confirmed that users found the new app intuitive and enjoyable, supporting a successful launch campaign. Choosing the right type of UX research depends on your project stage, goals, and available resources. Combining these approaches creates a strong foundation for user-centered design. Remember to stay flexible and let user insights guide your decisions.

By Philip Burgess | UX Research Leader Choosing a career in user experience (UX) can be exciting but also confusing. Two popular paths in this field are UX research and UX design. Both roles focus on improving how users interact with products, but they do so in different ways. I want to share my experience and insights to help you decide which path fits your skills, interests, and goals better. A UX researcher reviewing user feedback and data Understanding UX Research UX research is about understanding users deeply. Researchers gather data on user behaviors, needs, and motivations through interviews, surveys, usability tests, and observation. The goal is to uncover problems users face and find ways to improve the product experience. When I started in UX research, I enjoyed asking questions and listening carefully. It felt rewarding to discover insights that shaped product decisions. For example, in one project, I ran usability tests on a mobile app and found users struggled with navigation. Sharing this insight helped the design team simplify the menu, which improved user satisfaction. Key Skills for UX Researchers Strong communication and interviewing skills Analytical thinking to interpret data Familiarity with research methods and tools Patience and attention to detail Ability to present findings clearly to teams If you like digging into data, talking to people, and solving puzzles about human behavior, UX research might be your fit. Understanding UX Design UX design focuses on creating the actual experience users have with a product. Designers work on layout, interaction, and visual elements to make products easy and enjoyable to use. This role involves wireframing, prototyping, and collaborating closely with developers and researchers. When I switched to UX design, I found joy in crafting interfaces and testing how users interacted with them. One memorable project involved redesigning an e-commerce checkout process. By simplifying steps and adding clear feedback, the conversion rate increased significantly. Key Skills for UX Designers Creativity and visual design sense Proficiency with design tools like Figma or Sketch Understanding of user-centered design principles Problem-solving and iterative testing Collaboration with cross-functional teams If you enjoy building things, experimenting with layouts, and seeing your ideas come to life, UX design could be your path. A UX designer sketching wireframes for a mobile app Comparing the Two Paths Both UX research and UX design aim to improve user experience, but they approach it differently. Here are some points to consider: Focus : Research is about understanding users; design is about creating solutions. Daily tasks : Researchers conduct studies and analyze data; designers create wireframes and prototypes. Tools : Researchers use survey platforms, analytics, and interview guides; designers use design software and prototyping tools. Collaboration : Both work closely with product teams, but researchers often guide design decisions, while designers implement them. Personality fit : Researchers tend to be curious, analytical, and patient; designers are creative, visual, and hands-on. In my experience, some people enjoy blending both roles, becoming UX generalists. But specializing helps build deeper expertise and career growth. How to Choose Your Path To decide which career suits you, reflect on these questions: Do you enjoy talking to people and analyzing data, or do you prefer creating and testing designs? Are you more curious about why users behave a certain way or how to make their experience better? Which skills do you want to develop: research methods or design tools? What kind of work environment do you prefer: conducting studies or working on visual projects? Try internships, online courses, or side projects in both areas. For example, I took a UX research course first, then a design bootcamp. This helped me understand both sides and choose what felt right. Growing Your Career Both UX research and design offer strong career opportunities. Researchers can advance to lead roles, specializing in areas like ethnography or usability testing. Designers can become senior UX designers, interaction designers, or product designers. Learning to communicate well with other teams is crucial in both paths. Also, staying updated on new tools and trends helps you stay competitive. Final Thoughts Choosing between UX research and UX design depends on your interests and strengths. Research suits those who love understanding people and data. Design fits those who enjoy creating and experimenting with interfaces. Both paths offer meaningful work that improves how people interact with technology. If you are unsure, explore both areas through projects or courses. The best choice is the one that keeps you curious and motivated every day. Start small, learn continuously, and your career will grow naturally.

By Philip Burgess | UX Research Leader When I first started working in UX research, I quickly realized that relying on a single method often left gaps in understanding user behavior. One method might reveal what users do, but not why. Another might uncover motivations but miss patterns in actual use. Over time, I learned that layering different UX research methods creates a fuller, more reliable picture. This approach strengthens the evidence we gather and leads to better design decisions. In this post, I’ll share how combining methods can improve your research outcomes. I’ll explain why layering works, give examples of effective combinations, and offer practical tips for applying this approach in your projects. A UX researcher reviewing layered data from multiple research methods Why Layering UX Research Methods Matters No single UX research method can answer every question. Each has strengths and weaknesses: Surveys capture broad user opinions but lack depth. Interviews provide rich insights but cover fewer users. Usability tests show how users interact with a product but may not reveal underlying motivations. Analytics track behavior patterns but don’t explain why users act a certain way. By layering methods, you combine their strengths and offset weaknesses. For example, starting with surveys can identify common pain points. Then, follow-up interviews can explore those issues in detail. Usability tests can validate solutions based on those insights. This layered approach builds stronger evidence because it: Confirms findings across different data sources. Provides both quantitative and qualitative perspectives. Helps uncover hidden problems or opportunities. Reduces bias by cross-checking results. Examples of Effective Method Combinations Here are some combinations I’ve found useful in my work: Surveys and Interviews Surveys help gather data from a large group quickly. They reveal trends and common frustrations. But they don’t explain why users feel a certain way. Interviews fill that gap by letting you ask open-ended questions and dig deeper. For example, a survey might show 40% of users struggle with navigation. Interviews can uncover whether that’s due to confusing labels, poor layout, or missing features. Usability Testing and Analytics Analytics provide a high-level view of user behavior, such as where users drop off in a checkout process. Usability testing lets you observe users trying to complete tasks and identify specific obstacles. In one project, analytics showed a high abandonment rate on a signup page. Usability tests revealed that unclear error messages caused confusion, which analytics alone couldn’t explain. Diary Studies and Contextual Inquiry Diary studies collect user feedback over time, capturing experiences in real-life settings. Contextual inquiry involves observing users in their natural environment to understand context and workflows. Combining these methods helps you see how users interact with a product day-to-day and what external factors influence their behavior. How to Layer Methods in Your Research To get started with layering UX research methods, consider these steps: Define your research goals clearly. Know what questions you want to answer and what decisions you need to support. Choose complementary methods. Pick methods that provide different types of data or perspectives. Plan the sequence. Start with broad methods like surveys or analytics to identify issues, then use qualitative methods to explore them. Iterate based on findings. Use insights from one method to refine your approach in the next. Document and compare results. Look for patterns and contradictions across methods to build a strong case. Practical Tips for Success Keep your sample sizes appropriate for each method. Large for surveys, smaller for interviews and usability tests. Use consistent terminology and questions where possible to make comparisons easier. Involve stakeholders early to align on goals and share findings regularly. Be flexible. Sometimes unexpected insights require adjusting your plan. Don’t overload your project with too many methods. Focus on those that add the most value. Detailed UX research notes combining survey results, interview quotes, and usability test observations Layering UX research methods has transformed how I approach projects. It gives me confidence that the evidence I present is well-rounded and reliable. If you want to improve your research outcomes, try combining methods thoughtfully. Start small, learn from each step, and build a process that fits your team and users.

By Philip Burgess | UX Research Leader When deadlines shrink and projects speed up, UX research often feels like the first thing to get squeezed out. Yet, skipping or rushing research can lead to costly mistakes and missed opportunities. I’ve faced this challenge many times, and I want to share practical ways to adapt UX research methods when time is limited, without sacrificing the quality of insights. Quick user journey mapping during tight project timelines UX Research Methods: Prioritize Research Goals Clearly When time is tight, you cannot cover everything. Start by narrowing down your research goals to the most critical questions that will directly impact design decisions. Ask yourself: What decisions need to be made soon? Which user pain points are most urgent to understand? What assumptions must be validated immediately? For example, in one project, we had only a week to validate a new onboarding flow. Instead of broad exploratory research, we focused on testing just the key steps where users typically drop off. This focus helped us gather actionable feedback quickly. Use Rapid Research Techniques Traditional UX research methods like in-depth interviews or long usability tests take time. Instead, use rapid techniques that deliver fast insights: Guerrilla testing : Approach users in public spaces or online forums for quick feedback. Remote unmoderated testing : Use tools like Maze or UserTesting to gather usability data without scheduling sessions. Surveys with targeted questions : Keep surveys short and focused to collect quantitative data fast. Diary studies with limited duration : Ask users to record specific interactions over a few days instead of weeks. In one case, I ran guerrilla tests at a local café to get quick reactions to a mobile app prototype. The informal setting and short sessions gave us valuable feedback within hours. Leverage Existing Data and Research Before starting new research, check if there is existing data you can use. This might include: Analytics data showing user behavior patterns Previous research reports or usability test results Customer support tickets highlighting common issues Feedback from sales or customer success teams Using existing data can save days or weeks. For instance, I once used heatmap analytics combined with customer support logs to identify usability problems without running new tests. Simplify Participant Recruitment Recruiting participants often slows down research. To speed this up: Use your network or internal employees as proxy users when appropriate. Reach out to existing customers via email or social media. Use online platforms that provide quick access to participants. Limit the number of participants to the minimum needed for meaningful insights. In a recent project, I recruited five participants from a company’s user base within 48 hours using a simple email invitation and scheduling tool. This was enough to spot major usability issues. Focus on Key Metrics and Observations When analyzing data under time pressure, avoid deep dives into every detail. Instead, focus on: Major usability problems that block users Patterns that appear across multiple participants User quotes that highlight strong emotions or confusion Metrics like task success rate, time on task, or error frequency This approach helps you quickly identify what matters most and communicate findings clearly to stakeholders. Analyzing key usability test results during a tight deadline Communicate Findings Effectively and Quickly Under tight timelines, your research findings must be easy to understand and act on. Use: Visual summaries like charts, heatmaps, or annotated screenshots Bullet points highlighting key issues and recommendations Short presentations or quick video summaries Direct conversations with designers and product managers In one project, I created a one-page report with screenshots and bullet points that the team could review in minutes. This helped speed up decision-making and implementation. Plan for Iterative Research When time is limited, you might not get all the answers upfront. Plan to iterate : Conduct quick rounds of research focused on different aspects in each sprint. Use early findings to guide design changes and test again. Build research into the development cycle to avoid last-minute crunches. I’ve found that even small, frequent research sessions can add up to strong user understanding over time. Adapting UX research methods under tight timelines requires focus, creativity, and smart use of resources. By prioritizing goals, using rapid techniques, leveraging existing data, simplifying recruitment, focusing on key insights, and communicating clearly, you can still deliver valuable user insights that improve your product.

By Philip Burgess | UX Research Leader When I first started working with AI tools in research, I believed they could solve nearly every problem. After all, AI can process vast amounts of data faster than any human. But over time, I realized that even with perfect data, AI falls short in making the nuanced judgments that research demands. This post explores why human judgment remains essential in research, despite advances in AI and data quality. Researcher reviewing complex data visualizations The Limits of Data Perfection Data quality is crucial in research. Flawed or incomplete data can lead to wrong conclusions. AI thrives on clean, structured data, and when data is perfect, AI can identify patterns and correlations quickly. However, perfect data alone does not guarantee correct interpretation. For example, in medical research, AI might detect correlations between symptoms and outcomes. But deciding which correlations are meaningful or causal requires understanding the broader context, including patient history, environmental factors, and clinical experience. AI lacks this contextual awareness. The Role of Context and Experience Research judgment involves more than analyzing numbers. It requires understanding the context in which data exists. Human researchers bring experience, intuition, and domain knowledge that AI cannot replicate. I remember working on a project where AI suggested a surprising link between two variables in environmental data. The data was flawless, but my experience told me the link was likely coincidental due to seasonal effects. Further investigation confirmed this. AI had no way to question the data’s real-world context. Ethical Considerations and Value Judgments Research often involves ethical decisions and value judgments. These cannot be reduced to data points. For instance, deciding whether to prioritize certain research questions or how to handle sensitive data requires human judgment. AI can flag potential ethical issues based on rules, but it cannot weigh competing values or societal impacts. Researchers must interpret AI outputs through an ethical lens, balancing risks and benefits. Creativity and Hypothesis Generation AI excels at pattern recognition but struggles with creativity. Formulating new hypotheses or designing innovative experiments depends on human imagination and insight. In my own work, I’ve seen AI generate hypotheses based on existing data trends. Yet, the most groundbreaking ideas came from human researchers connecting disparate concepts or questioning assumptions. AI supports this process but does not replace it. Notebook with handwritten research notes and sketches Collaboration Between AI and Human Judgment The future of research lies in collaboration between AI and humans. AI can handle data processing, highlight patterns, and suggest possibilities. Researchers then apply judgment to interpret results, consider context, and make decisions. This partnership improves efficiency and insight without sacrificing the critical thinking that drives meaningful research. It also helps avoid overreliance on AI, which can lead to blind spots or errors if data is misunderstood. Practical Tips for Researchers Using AI Maintain critical thinking : Always question AI outputs and consider alternative explanations. Understand your data : Know the source, limitations, and context of your data before trusting AI analysis. Use AI as a tool, not a decision-maker : Let AI assist with data handling but keep final judgments human. Stay aware of ethical issues : Reflect on the broader impact of your research beyond data patterns. Encourage creativity : Use AI to explore ideas but rely on human insight for innovation. By combining AI’s strengths with human judgment, researchers can unlock deeper understanding and avoid pitfalls that come from relying on data alone.

By Philip Burgess | UX Research Leader When I first encountered the idea of servant leadership, I was skeptical. Leadership, in my mind, was about authority, decision-making, and driving results. The notion of leading by serving others felt counterintuitive. Yet, over time, I discovered that this quiet discipline holds a powerful key to building trust, fostering growth, and creating lasting impact. What Servant Leadership Really Means Servant leadership flips the traditional leadership model. Instead of focusing on personal power or status, it centers on the growth and well-being of the people you lead. The leader’s role is to support, listen, and empower others to reach their full potential. This approach requires humility and patience. It’s not about quick wins or flashy achievements. Instead, it’s about consistent, often unseen efforts that build strong foundations. I learned this firsthand when I took on a leadership role in a community project. Rather than directing every move, I focused on understanding the needs of each team member and removing obstacles from their path. The results surprised me: the team became more motivated, creative, and committed. A leader attentively listening to team members in a relaxed setting The Core Practices of Servant Leadership To practice servant leadership effectively, I found that certain habits make a big difference: Active Listening Truly hearing what others say, without interrupting or planning your response. This builds trust and shows respect. Empathy Understanding feelings and perspectives helps address concerns and motivates people authentically. Stewardship Taking responsibility for the team’s resources and well-being, not just outcomes. Commitment to Growth Investing time and energy in developing others’ skills and confidence. Building Community Encouraging collaboration and a sense of belonging strengthens the group’s resilience. When I applied these principles in my work, I noticed a shift. People felt valued and safe to share ideas. Challenges became opportunities for learning rather than blame. This environment sparked innovation and loyalty. Overcoming Challenges in Servant Leadership Adopting this style is not without its challenges. It requires resisting the urge to control and instead trusting others. Early on, I struggled with letting go of decisions and outcomes. I worried that without my direct input, things would fall apart. One example stands out. During a project, I stepped back to let a team member lead a critical task. At first, I felt anxious and tempted to intervene. But I reminded myself that my role was to support, not take over. The team member succeeded, gaining confidence and respect from others. This experience taught me that servant leadership builds stronger leaders within the team. Another challenge is that servant leadership often goes unnoticed. It’s quiet work, without immediate recognition. But the long-term benefits—strong relationships, high morale, and sustainable success—are worth the patience. Practical Steps to Start Serving as a Leader If you want to embrace servant leadership, here are some practical steps to begin: Ask Questions Instead of giving orders, ask what people need to succeed. Create Safe Spaces Encourage open communication without fear of judgment. Offer Support Help remove barriers and provide resources. Recognize Efforts Celebrate progress and contributions, no matter how small. Reflect Regularly Take time to assess your leadership style and its impact. These actions don’t require grand gestures. Small, consistent efforts build trust and respect over time. A notebook open to notes about leadership and service Why Servant Leadership Matters Today In a world where leadership often feels rushed and transactional, servant leadership offers a refreshing alternative. It nurtures deeper connections and creates environments where people thrive. From my experience, teams led with this mindset show greater resilience and adaptability. This approach also aligns with values many of us hold dear: kindness, respect, and shared success. It reminds us that leadership is not about being in charge but about caring for those we lead. If you’re ready to try a different way of leading, start small. Listen more. Support quietly. Watch how your team grows stronger and more engaged. The quiet discipline of servant leadership might just change how you see leadership—and yourself.

By Philip Burgess | UX Research Leader When I first started working in UX research, my focus was narrow: understand users for a single product, gather feedback, and improve that product. Over time, I realized this approach misses a bigger opportunity. UX research can and should extend beyond individual products to shape broader strategies that benefit entire organizations and ecosystems. This shift changes how we think about users, data, and design decisions. In this post, I’ll share what I’ve learned about building a UX research strategy that goes beyond one product. I’ll explain why it matters, how to approach it, and practical steps you can take to make your research more impactful across multiple products or services. Researcher reviewing UX data across products Why UX Research Should Go Beyond Individual Products Focusing on a single product’s user experience can lead to valuable insights, but it also creates blind spots. Users don’t interact with products in isolation. They engage with entire ecosystems—multiple apps, websites, devices, and services that connect in complex ways. When research stays confined to one product, it misses how users switch between tools, what frustrations carry over, and where opportunities for improvement lie across the board. For example, I worked on a project where the company had three separate apps serving different parts of the customer journey. Each product team conducted their own research, but no one looked at the full picture. Users struggled with inconsistent navigation and repeated sign-ins. When we combined research efforts, we uncovered patterns that led to a unified login system and a smoother experience across all apps. This broader approach helps organizations: Identify shared pain points that affect multiple products Create consistent experiences that build trust and ease of use Prioritize investments based on overall user impact, not just product-specific metrics Support innovation by spotting gaps and opportunities across the ecosystem Building a Cross-Product UX Research Strategy Developing a UX research strategy that spans beyond individual products requires planning and collaboration. Here are key steps I recommend: 1. Define Common Goals and Metrics Start by aligning teams around shared objectives. What user outcomes matter most across products? These could include ease of onboarding, task completion rates, or customer satisfaction scores. Agreeing on common metrics helps unify research efforts and makes it easier to compare findings. 2. Map the User Journey Across Products Create a comprehensive user journey map that includes touchpoints with all relevant products and services. This map reveals where users switch between tools, encounter friction, or drop off. It also highlights moments where research should focus. 3. Share Research Plans and Data Encourage teams to share research plans, methods, and findings openly. Use centralized repositories or collaboration tools to store user interviews, survey results, usability tests, and analytics. This transparency prevents duplicated efforts and uncovers connections between insights. 4. Use Mixed Methods for Richer Insights Combine qualitative and quantitative research across products. For example, follow up analytics showing high drop-off rates with interviews to understand why users leave. Cross-product surveys can reveal broader attitudes and preferences. 5. Involve Stakeholders Across Teams Bring together product managers, designers, developers, and marketers from different teams to review research findings. Their diverse perspectives help interpret data and identify cross-product solutions. User journey mapping session across multiple products Practical Examples of Cross-Product UX Research Here are some real-world examples that illustrate how this strategy works: E-commerce platform : A company with separate websites for retail, wholesale, and mobile shopping apps combined research to understand how customers move between channels. They discovered inconsistent product information caused confusion. The solution was a unified product database accessible by all teams. Healthcare services : A hospital system with multiple patient portals found that users struggled to access their medical records across platforms. Cross-product research led to a single sign-on system and a redesigned portal interface that improved patient satisfaction. Financial services : A bank with different apps for checking, investing, and loans used combined user feedback to identify overlapping features and redundant steps. They streamlined workflows and introduced a dashboard that gives users a holistic view of their finances. Challenges and How to Overcome Them Expanding UX research beyond individual products is not without challenges: Silos between teams can block information sharing. Overcome this by setting up regular cross-team meetings and shared documentation. Different research methods and tools may make data integration difficult. Standardize tools or create processes to translate findings into common formats. Resource constraints might limit the ability to conduct broad research. Prioritize key user journeys that impact multiple products to maximize value. Resistance to change can slow adoption of cross-product strategies. Demonstrate quick wins and show how broader insights improve user experience and business outcomes. Final Thoughts on Expanding UX Research Moving beyond individual products in UX research opens new doors to understanding users more deeply and designing better experiences. It requires coordination, shared goals, and a willingness to look at the bigger picture. When done well, it helps organizations create seamless, consistent, and meaningful experiences that users appreciate. If you’re ready to take your UX research to the next level, start by mapping your users’ full journey and connecting with other teams. Share your findings openly and focus on common goals. This approach will help you uncover insights that no single product research could reveal.

By Philip Burgess | UX Research Leader When I first started working in UX design, I quickly realized that understanding users wasn’t just about guessing what they wanted. It required solid research methods that reveal real behaviors and needs. Over time, I learned which UX research methods deliver the most useful insights and how to apply best practices to get the most from them. If you want your designs to truly connect with users, knowing these methods and how to use them effectively is essential. Usability testing session with participant and researcher UX Research Methods: User Interviews: Listening to Real Voices User interviews are one of the most straightforward and powerful ways to gather qualitative data. Sitting down with users and asking open-ended questions helps uncover motivations, frustrations, and expectations that you might never see through analytics alone. Best practices for user interviews: Prepare a flexible script with key topics but allow the conversation to flow naturally. Avoid leading questions that push users toward certain answers. Record sessions (with permission) to review later and catch details you might miss. Interview a diverse group of users to get a broad perspective. For example, when redesigning a mobile app, I conducted interviews with users across different age groups. This revealed that older users struggled with small buttons, while younger users wanted faster navigation. These insights directly shaped the design decisions. Usability Testing: Watching Users in Action Usability testing involves observing users as they complete tasks with your product. This method highlights where users get stuck, what confuses them, and which features work well. How to make usability testing effective: Define clear tasks that reflect real user goals. Test early and often, even with rough prototypes. Use think-aloud protocols where users explain their thought process. Analyze patterns across multiple sessions rather than focusing on one-off issues. In one project, I watched users try to book tickets on a website prototype. Many struggled to find the date selector. By spotting this early, the team redesigned the calendar interface, which improved task success rates by 30% in later tests. Surveys and Questionnaires: Gathering Quantitative Insights Surveys help collect data from a larger audience quickly. They are useful for validating hypotheses or measuring satisfaction and preferences. Tips for successful surveys: Keep questions clear and concise. Use a mix of multiple-choice and open-ended questions. Avoid bias by not suggesting answers. Pilot the survey with a small group before full launch. For instance, after launching a new feature, I sent out a survey to users asking about ease of use and usefulness. The quantitative data showed 75% found it helpful, but open comments revealed some wanted more customization options. This feedback guided the next update. User completing an online survey about app experience Card Sorting: Organizing Content with Users Card sorting helps understand how users group information and what labels make sense to them. This method is especially useful for designing navigation menus or information architecture. Best practices for card sorting: Choose between open card sorting (users create their own categories) or closed card sorting (users sort into predefined categories). Use digital tools for remote sessions or physical cards for in-person. Analyze results to find common groupings and naming patterns. I used card sorting when redesigning a website’s menu. Users consistently grouped services differently than the internal team expected. Adjusting the menu structure based on these findings made the site easier to navigate and reduced bounce rates. A/B Testing: Comparing Design Variations A/B testing compares two versions of a design to see which performs better on specific metrics like click-through rates or conversions. How to run A/B tests effectively: Test one variable at a time to isolate its impact. Ensure a large enough sample size for reliable results. Run tests long enough to account for daily or weekly traffic fluctuations. Use clear success criteria before starting. In one case, I tested two button colors on a signup page. The green button increased signups by 12% compared to blue. This simple change had a measurable impact on user behavior. Ethnographic Research: Observing Users in Their Environment Ethnographic research involves watching users in their natural setting to understand context and behaviors that might not emerge in labs or interviews. Key points for ethnographic studies: Spend time where users interact with your product or service. Take detailed notes on environment, tools, and social interactions. Look for unspoken habits or workarounds. Respect privacy and obtain consent. During a project for a healthcare app, I visited clinics to observe how nurses used existing tools. This revealed workflow challenges and device limitations that shaped the app’s design to better fit real-world use. Combining Methods for Stronger Insights No single UX research method gives a complete picture. The best results come from combining methods to validate findings and cover different angles. For example, I started with user interviews to explore pain points, followed by usability testing to observe those issues in action. Then I used surveys to quantify how widespread the problems were. This layered approach built confidence in design decisions and reduced guesswork. Final Thoughts on Making UX Research Work UX research methods are powerful tools when used thoughtfully. The key is to choose the right method for your question, prepare carefully, and apply best practices to gather honest, useful data. Remember, research is not a one-time task but an ongoing process that keeps your designs aligned with real user needs. If you want your designs to succeed, start by listening closely to users, watching how they interact, and testing your ideas early. The insights you gain will save time, reduce costly mistakes, and create experiences that truly resonate.

By Philip Burgess | UX Research Leader When I first started using AI tools in my UX research, I was excited about the speed and scale they offered. But I quickly realized that without clear guardrails, these tools could lead me astray. AI can generate insights fast, but it can also introduce bias, misinterpret data, or overlook important human context. Designing guardrails for AI-assisted UX research is essential to get reliable, ethical, and useful results. In this post, I’ll share my experience and practical steps to create effective guardrails that help balance AI’s power with human judgment. Why Guardrails Matter in AI-Assisted UX Research AI tools can analyze large datasets, spot patterns, and even suggest design improvements. But they don’t understand nuance or context the way humans do. Without guardrails, AI might: Misinterpret user feedback due to language subtleties Reinforce existing biases in data Generate misleading conclusions from incomplete data Overlook emotional or cultural factors that affect user experience In my early projects, I saw AI highlight trends that looked promising but didn’t match real user behavior when tested. That taught me that AI is a tool, not a replacement for human insight. UX researcher reviewing AI data with focus Guardrails help UX researchers maintain control over AI-generated insights. Setting Clear Objectives for AI Use Before integrating AI, define what you want it to do. For example: Summarize large volumes of user feedback Identify common pain points in usability tests Generate hypotheses for further testing When I started, I made the mistake of letting AI analyze everything without a clear goal. This led to overwhelming and unfocused results. Setting clear objectives helps you design guardrails that keep AI focused and relevant. Establishing Data Quality Standards AI’s output is only as good as the input data. I learned to: Use clean, well-organized datasets Remove irrelevant or low-quality feedback Ensure diversity in user data to avoid bias For example, in one project, I noticed AI recommendations favored a specific user group because the dataset was skewed. By expanding the dataset to include diverse users, the AI insights became more balanced. Defining Boundaries for AI Interpretation AI can misinterpret ambiguous language or sarcasm in user comments. To prevent this, I set rules such as: Flagging uncertain AI interpretations for human review Combining AI sentiment analysis with manual checks Avoiding full reliance on AI for emotional or cultural insights This approach helped me catch errors early and maintain trust in the research findings. Creating Feedback Loops Between AI and Humans Guardrails work best when AI and humans collaborate. I built feedback loops where: Researchers review AI-generated insights regularly AI models get updated based on researcher feedback Teams discuss AI findings before making design decisions This ongoing interaction ensures AI stays aligned with real user needs and research goals. UX team collaborating on AI-assisted research findings Collaboration between AI and researchers strengthens the quality of UX insights. Ethical Considerations and Transparency AI can unintentionally reinforce stereotypes or invade user privacy. I always make sure to: Use anonymized data to protect user identity Be transparent with stakeholders about AI’s role and limitations Avoid using AI to make final decisions without human oversight For example, in one study, I disclosed to participants how AI would be used to analyze their feedback. This transparency built trust and encouraged honest responses. Practical Steps to Build Guardrails Here are some actionable steps I recommend: Define clear research questions before applying AI Audit your data for quality and diversity Set thresholds for AI confidence scores to trigger human review Train your team on AI capabilities and limitations Document AI processes and decisions for accountability Regularly evaluate AI outputs against real user testing results These steps helped me create a reliable framework that balances AI efficiency with human judgment. Final Thoughts on Guardrails for AI-Assisted UX Research AI can transform UX research by handling large datasets and generating quick insights. But without guardrails, it risks producing misleading or biased results. My experience shows that clear objectives, data quality, human oversight, and ethical transparency are key to designing effective guardrails. If you’re starting with AI in UX research, focus on building these guardrails early. This will help you trust the insights AI provides and create better experiences for your users.

By Philip Burgess | UX Research Leader When I first stepped into a leadership role, I believed that being a servant leader meant always having the right answers and making everyone feel comfortable. I quickly learned that leadership is rarely comfortable. The real challenge is sitting with discomfort—leaning into difficult conversations, facing uncertainty, and managing emotions without rushing to fix or avoid them. This skill is essential for anyone who wants to lead with empathy and authenticity. In this post, I will share why sitting with discomfort is a crucial step for servant leaders. I’ll explain how embracing discomfort helps build trust, encourages growth, and strengthens teams. Along the way, I’ll offer practical examples and insights from my own experience. A quiet room with a single chair symbolizing the space to sit with discomfort Understanding Discomfort in Servant Leadership Discomfort shows up in many ways for leaders. It might be the tension of delivering tough feedback, the uncertainty of making decisions without all the facts, or the vulnerability of admitting mistakes. For servant leaders, discomfort often comes from putting others’ needs first, which can mean facing conflict or feeling exposed. Instead of avoiding these moments, servant leaders must learn to stay present with them. This means resisting the urge to jump in with quick solutions or to smooth things over prematurely. Sitting with discomfort allows leaders to: Listen deeply to understand others’ perspectives Reflect honestly on their own feelings and biases Create space for authentic dialogue and problem-solving When I first practiced this, I noticed how much more open and honest my team became. They felt seen and heard, even when the topics were difficult. How Sitting With Discomfort Builds Trust Trust is the foundation of servant leadership. People follow leaders they believe are genuine and reliable. When leaders shy away from discomfort, they risk appearing distant or insincere. On the other hand, showing up fully—even when it’s hard—builds credibility. For example, I once had to address a conflict between two team members. Instead of avoiding the issue or trying to fix it quickly, I invited both to a conversation where we acknowledged the tension openly. I admitted my own uncertainty about the best way forward. This honesty encouraged them to share their feelings without fear. The result was a stronger relationship and a clearer path to collaboration. Trust grows when leaders: Admit what they don’t know Show vulnerability without losing confidence Stay committed to working through challenges together This approach turns discomfort into a bridge rather than a barrier. Discomfort Encourages Growth and Innovation Growth rarely happens in comfort zones. Servant leaders who embrace discomfort model a mindset that encourages learning and experimentation. When teams see their leader willing to face hard truths and take risks, they feel safer to do the same. In one project, I pushed my team to try a new approach that felt risky. We didn’t have all the answers, and the possibility of failure was real. Instead of hiding that uncertainty, I shared it openly. We talked about what might go wrong and how we would respond. This honest conversation helped the team feel supported, and we ended up with creative solutions that improved our results. Leaders who sit with discomfort help their teams: Take calculated risks Learn from mistakes without blame Develop resilience in the face of setbacks This culture of growth is essential for long-term success. A notebook with handwritten reflections symbolizing personal growth through discomfort Practical Steps to Learn Sitting With Discomfort Learning to sit with discomfort is a skill that takes practice. Here are some steps I found useful: Pause before reacting . When you feel discomfort, take a breath and resist the urge to respond immediately. This pause creates space for thoughtful action. Name the feeling . Acknowledge what you are experiencing internally. Saying “I feel uncertain” or “This is uncomfortable” helps reduce its power. Ask open questions . Instead of assuming, invite others to share their views. Questions like “What are you feeling?” or “What do you think we should do?” open dialogue. Reflect regularly . Set aside time to journal or think about your leadership challenges and how you handled discomfort. This builds self-awareness. Seek feedback . Ask trusted colleagues how you come across in difficult situations. Use their insights to improve. These practices helped me become more comfortable with discomfort itself, which made me a stronger leader. The Ripple Effect of Embracing Discomfort When servant leaders learn to sit with discomfort, the impact goes beyond themselves. Teams become more open, communication improves, and problems get solved more effectively. People feel valued because their leader is willing to face hard moments alongside them. This ripple effect creates a culture where challenges are seen as opportunities to learn and connect. It also helps prevent burnout because leaders and teams don’t have to pretend everything is fine when it’s not. In my experience, the willingness to stay present with discomfort has been one of the most powerful tools for building a healthy, resilient team.