When it comes to UX research, sharing your findings clearly and effectively is just as important as the research itself. After all, what good is uncovering user insights if they get lost in a sea of notes or confusing reports? That’s where findings templates come in handy. They help us organize data, highlight key takeaways, and make recommendations that actually get acted upon. So, how do we create findings templates in UX that are both practical and engaging? Let’s dive in. Why Use Findings Templates in UX? Templates might sound boring, but trust me, they’re a lifesaver. Imagine you’ve just wrapped up a usability test with a dozen participants. You have hours of recordings, notes, and observations. Without a structured way to present this, your insights might end up buried or misunderstood. Using findings templates in UX helps us: Standardize reporting so everyone on the team knows where to find what. Save time by not reinventing the wheel for every project. Focus on what matters by highlighting key insights and actionable recommendations. Improve communication between researchers, designers, and stakeholders. For example, a good template might have sections for the research goal, participant demographics, key findings, pain points, and suggested next steps. This structure keeps the report concise and easy to scan. Example of a UX findings report template on a laptop screen An organized findings template makes sharing insights a breeze. Key Elements of Effective Findings Templates in UX So, what should a findings template include? Here’s a breakdown of the essential parts that make your report clear and actionable: 1. Research Overview Start with a brief summary of the research purpose, methods used, and participant details. This sets the context and reminds readers why the study was conducted. 2. Key Findings This is the heart of your report. Present the most important insights clearly and concisely. Use bullet points or numbered lists to make them easy to digest. For example: Users struggled to find the checkout button on mobile. Confusing terminology led to task errors. Participants appreciated the personalized recommendations feature. 3. Supporting Evidence Back up your findings with quotes, screenshots, or data snippets. This adds credibility and helps stakeholders understand the “why” behind the insights. 4. Recommendations Here’s where you suggest concrete actions based on your findings. Be specific and prioritize changes that will have the biggest impact. For instance: Redesign the checkout button to be more prominent on mobile. Simplify language in the navigation menu. Enhance the recommendation algorithm to increase relevance. 5. Next Steps Outline what should happen after the report. Should there be follow-up testing? Design iterations? This keeps the momentum going. Using a findings and recommendations template can help you cover all these bases without missing a beat. What is the 5 5 5 Rule for Presentations? Ever heard of the 5 5 5 rule? It’s a handy guideline to keep presentations clear and engaging, especially when sharing UX findings. The rule says: No more than 5 words per line . No more than 5 lines per slide . No more than 5 slides per topic . Why does this matter? Because it forces you to be concise and focus on the essentials. When presenting findings, it’s tempting to cram every detail into slides. But too much text overwhelms your audience and dilutes your message. Applying the 5 5 5 rule means you’ll highlight key points, use visuals effectively, and keep your audience’s attention. It’s a simple trick to make your findings presentations more impactful. Presentation slide designed with the 5 5 5 rule for clarity Slides that follow the 5 5 5 rule keep your audience focused and engaged. Tips for Customizing Your Findings Template No two projects are the same, so your findings template shouldn’t be one-size-fits-all. Here are some tips to tailor your template for different contexts: Adjust for audience: Executives want high-level insights and business impact. Designers need detailed usability issues and user quotes. Customize sections accordingly. Use visuals: Charts, heatmaps, and screenshots can make findings more relatable and easier to understand. Keep it concise: Avoid jargon and long paragraphs. Use bullet points and short sentences. Highlight priorities: Use color coding or icons to show which issues are critical versus nice-to-have. Include a summary: A one-page executive summary can be a great addition for busy stakeholders. Remember, the goal is to make your findings easy to consume and act on. If your template feels too bulky or complicated, it’s time to simplify. Making Your Findings Templates Work for You Creating a solid findings template is just the start. To really make it work, you need to integrate it into your workflow: Use it consistently: The more you use the same template, the easier it gets to fill out and review. Get feedback: Ask your team what works and what doesn’t. Iterate on your template regularly. Train your team: Make sure everyone understands how to use the template and why it matters. Combine with storytelling: Numbers and bullet points are great, but stories stick. Use your template as a foundation, then add narrative to bring findings to life. By making findings templates a natural part of your process, you’ll boost clarity, save time, and help your team make better design decisions. Creating effective findings templates in UX isn’t rocket science, but it does require thought and practice. With the right structure, clear language, and a bit of creativity, you can turn raw data into compelling insights that drive real change. So, why not start building your own template today? Your future self (and your team) will thank you.

By Philip Burgess | UX Research Leader Finding the right place to launch or grow your UX research career can feel overwhelming. With so many job boards and career sites out there, it’s easy to get lost in the noise. I’ve spent years navigating this space, and I want to share the best UX research career sites that helped me find meaningful roles and connect with the right opportunities. Whether you’re just starting out or looking to take the next step, these sites offer a mix of job listings, resources, and community support tailored specifically for UX researchers. UX research job listings on a laptop screen UX Research Career Sites That Stand Out 1. UX Research Jobs on LinkedIn LinkedIn is more than just a professional network. It’s a powerful job search tool, especially for UX research roles. What makes LinkedIn stand out is its ability to connect you directly with hiring managers and recruiters. You can also see if you have any mutual connections at companies you’re interested in, which can be a huge advantage. Job alerts tailored to your preferences keep you updated. Company pages offer insights into culture and recent projects. Networking opportunities through groups and posts related to UX research. I found my first UX research role through LinkedIn by engaging with posts and reaching out to people in the field. It’s a great place to build your professional presence while hunting for jobs. 2. UXPA Job Board The User Experience Professionals Association (UXPA) hosts a job board focused exclusively on UX roles, including research positions. This site is ideal if you want a curated list of openings from companies that value UX research. Jobs range from entry-level to senior roles. Listings often include contract, freelance, and full-time positions. The site also offers resources like webinars and articles to boost your skills. I appreciated how the UXPA job board filters out unrelated roles, saving time and helping me focus on relevant opportunities. 3. Indeed’s UX Research Section Indeed is one of the largest job boards globally, and its UX research section is surprisingly comprehensive. It aggregates listings from company websites, recruitment agencies, and other job boards. Easy to use with filters for location, salary, and experience level. Includes company reviews and salary estimates. Allows uploading your resume for quick applications. While it’s broad, Indeed’s strength lies in volume. If you want to see a wide range of UX research jobs in one place, it’s worth checking regularly. Smartphone screen showing UX research job listings on a career platform 4. Glassdoor for UX Research Roles Glassdoor is known for company reviews, but its job search feature is equally valuable. For UX researchers, it offers insights into company culture, interview questions, and salary ranges alongside job listings. Read firsthand employee experiences. Prepare for interviews with shared questions. Compare salaries across companies and locations. I used Glassdoor to research companies before applying, which helped me tailor my applications and prepare better for interviews. 5. ResearchOps Community Job Board ResearchOps is a growing community focused on the operational side of UX research. Their job board features roles that emphasize managing research processes and teams. Great for mid-career researchers looking to specialize. Includes remote and international opportunities. Community-driven with discussions and events. Joining this community helped me understand the evolving landscape of UX research and find roles that matched my growing interests in research operations. Tips for Using UX Research Career Sites Effectively Set up job alerts on multiple sites to get notified instantly. Tailor your resume and portfolio for each application, highlighting relevant skills. Engage with communities on these platforms to build connections. Research companies using reviews and interview insights before applying. Keep your profiles updated with your latest projects and skills. What I Learned From Using These Sites When I started my UX research career, I focused on general job boards and missed out on specialized opportunities. Switching to sites dedicated to UX research made a huge difference. I found roles that matched my skills and interests better, and I connected with people who understood the field. The combination of job listings, community support, and resources helped me grow professionally and land roles that felt like a good fit. Moving Forward With Your UX Research Career Finding the right career site is just the first step. Use these platforms to stay informed, build your network, and keep improving your skills. The UX research field is evolving, and staying connected to the right resources will help you adapt and thrive. Explore these sites, set your goals, and take action. Your next UX research role could be just a few clicks away. Keep learning, stay curious, and don’t hesitate to reach out to others in the field. The right opportunity is waiting for you.

By Philip Burgess | UX Research Leader When launching a Minimum Viable Product (MVP), the goal is not to deliver a polished, final product but to learn quickly and validate assumptions. Many teams focus on traditional UX metrics like task completion rates or time on task, which measure performance. But for MVPs, these metrics can miss the point. Instead, tracking learning-focused UX metrics helps teams understand user behavior, uncover pain points, and iterate effectively. I’ve worked on several MVP projects where shifting the focus from performance to learning transformed how we gathered insights and improved the product. In this post, I’ll share practical ways to measure learning through UX metrics and explain why this approach matters for MVP success. Wireframe prototype on laptop screen Why Traditional UX Metrics Fall Short for MVPs Traditional UX metrics often emphasize efficiency and effectiveness: Task success rate Time to complete tasks Error rate These metrics work well when the product is stable and users are familiar with it. But MVPs are early-stage products designed to test hypotheses and gather feedback. Users may struggle because the product is incomplete or unfamiliar. Measuring performance alone can give a false sense of failure or success. For example, a low task completion rate might not mean the product is bad. It could mean users don’t understand the concept or the interface needs refinement. Instead of judging the product by these numbers, MVP teams should focus on what users learn and how they interact with the product. Metrics That Focus on Learning Here are some UX metrics that help measure learning during MVP testing: 1. User Exploration Patterns Track how users navigate through the product. Are they trying different features? Do they return to certain screens? This shows what interests users and where they get stuck. Heatmaps and click maps reveal popular areas. Session recordings show navigation paths. This data helps identify confusing elements or features that need clearer explanations. 2. User Feedback and Qualitative Data Collect direct feedback through surveys, interviews, or in-app prompts. Ask users what they understood, what confused them, and what they expected. Open-ended questions reveal insights beyond numbers. User quotes highlight specific pain points. This qualitative data complements behavioral metrics and uncovers why users act a certain way. 3. Hypothesis Validation Rate Define clear hypotheses before testing the MVP. For example, “Users will find it easy to create an account in under two minutes.” After testing, measure how often this holds true. Track how many users meet the criteria. Adjust the product based on results. This metric ties learning directly to your product goals and helps prioritize changes. 4. Time to First Key Action Instead of measuring total task time, focus on how long it takes users to perform the first meaningful action, like signing up or adding an item to a cart. Shorter times indicate clearer onboarding. Longer times suggest confusion or friction. This metric shows how quickly users grasp the core value of the product. 5. Drop-off Points and Abandonment Reasons Identify where users leave the product or stop using a feature. Combine this with feedback to understand why. Funnel analysis highlights drop-off stages. Exit surveys ask users for reasons. Knowing where and why users abandon helps prioritize fixes that improve learning and engagement. User interacting with mobile app prototype on tablet Applying Learning Metrics in Real MVP Projects In one project, we launched an MVP for a task management app. Instead of focusing on task completion, we tracked how users explored the app and what features they tried first. We noticed many users spent time on the calendar view but rarely created tasks. Interviews revealed confusion about how tasks linked to dates. Using this insight, we simplified the task creation process and added tooltips explaining the calendar integration. After the update, time to first task creation dropped by 40%, and user feedback became more positive. This learning-focused approach helped us improve the product faster than relying on traditional metrics alone. Tips for Measuring Learning Effectively Set clear learning goals before testing. Use a mix of quantitative and qualitative data. Avoid judging MVP success solely on performance metrics. Iterate quickly based on insights. Share findings with the whole team to align on next steps. By focusing on learning, you turn MVP testing into a powerful discovery process that guides product development. Measuring learning instead of performance changes how you understand user experience during MVP testing. It reveals what users really think, where they struggle, and what matters most. This approach helps teams build better products faster by focusing on real insights, not just numbers.

By Philip Burgess | UX Research Leader When I first started working in user experience, I often found myself overwhelmed by the wealth of qualitative data collected from interviews, usability tests, and open-ended surveys. These rich stories and observations revealed what users felt and thought, but I struggled to translate them into numbers that could guide design decisions or measure progress. Over time, I learned how to turn those qualitative insights into clear, trackable UX metrics that helped my team focus on what truly mattered. If you have ever faced the challenge of making qualitative data actionable, this post will walk you through practical steps to convert user stories and observations into measurable metrics. You will see how to build a bridge between the human side of UX and the need for data-driven decisions. Why Qualitative Insights Matter in UX Qualitative data captures the why behind user behavior. It reveals emotions, motivations, frustrations, and unmet needs that numbers alone cannot explain. For example, a user might say, “I feel lost when I try to find the checkout button,” which points to a usability problem that raw click data might not fully expose. However, qualitative insights often come in the form of anecdotes or themes, making it difficult to track improvements over time or compare different design versions. Without quantification, these insights risk being overlooked or dismissed in favor of easier-to-measure metrics. Steps to Turn Qualitative Data into Metrics 1. Identify Key Themes and Patterns Start by reviewing your qualitative data to find recurring themes. These might include: Confusion about navigation Frustration with loading times Satisfaction with product recommendations Group similar comments and observations to create categories that represent common user experiences. 2. Define Clear UX Metrics Based on Themes Once you have themes, think about how to measure them. For example: Navigation confusion could be tracked by the number of clicks to reach a goal or the frequency of “back” button usage. Loading frustration might be measured by average page load time or the number of users abandoning a page. Satisfaction can be captured through post-task ratings or Net Promoter Score (NPS). The key is to link qualitative themes to quantitative indicators that reflect user experience. 3. Create Surveys or Task-Based Tests to Collect Quantitative Data Design surveys or usability tests that ask users to rate specific experiences related to your themes. For example, after a task, ask users to rate how easy it was to find the checkout button on a scale from 1 to 5. This turns subjective feelings into numbers you can track. 4. Use Behavioral Analytics to Support Qualitative Findings Combine survey data with analytics tools that track user behavior. For instance, if users say they feel lost in navigation, check heatmaps or click paths to see where they hesitate or drop off. This triangulation strengthens your metrics. UX designer analyzing user feedback notes Analyzing qualitative feedback to identify key UX themes Practical Example: Improving an E-commerce Checkout Flow At one point, my team noticed many users abandoned their carts during checkout. Interviews revealed users felt overwhelmed by too many form fields and unclear progress indicators. We grouped these insights into two themes: form complexity and lack of progress feedback . To track improvements, we defined metrics: Average time to complete checkout Drop-off rate at each step User rating of checkout ease (collected via post-task survey) After redesigning the checkout with fewer fields and a progress bar, we monitored these metrics. The average completion time dropped by 30%, and user ratings improved from 2.8 to 4.2 out of 5. This clear data helped us justify the redesign and plan further improvements. Tips for Making UX Metrics Meaningful Keep metrics user-centered. Focus on what affects the user experience, not just business KPIs. Use a mix of qualitative and quantitative data. Numbers tell you what happens; stories explain why. Set benchmarks and goals. Track metrics over time to see if changes improve the experience. Communicate findings clearly. Use visuals like charts and user quotes to make data relatable. Be flexible. UX is complex, so adjust metrics as you learn more about user needs. Dashboard displaying UX metrics and satisfaction scores Tracking UX improvements through clear, measurable metrics

By Philip Burgess | UX Research Leader When I first started working on user experience (UX) projects, I often found myself reacting to problems after they had already affected users. It felt like I was always putting out fires instead of preventing them. Over time, I realized that the key to better UX was to build early-warning metrics based on solid research. These metrics help spot issues before they escalate, allowing teams to act quickly and improve the product continuously. In this post, I’ll share how I developed early-warning UX metrics from research, why they matter, and practical steps you can take to build your own. Whether you’re a UX designer, researcher, or product manager, these insights will help you catch problems early and create smoother user experiences. Why Early-Warning UX Metrics Matter Waiting for users to complain or for analytics to show a drop in engagement is too late. Early-warning metrics give you a heads-up on potential UX issues before they become widespread problems. This proactive approach saves time, reduces frustration, and improves user satisfaction. For example, if you notice a sudden increase in the time users spend on a specific task, it might indicate confusion or difficulty. Catching this early allows you to investigate and fix the problem before it affects many users. Early-warning metrics also help prioritize UX improvements. Instead of guessing which issues matter most, you can rely on data that points to real user pain points. Analyzing user interaction data to identify early UX issues How I Built Early-Warning UX Metrics from Research Step 1: Understand User Goals and Pain Points The foundation of any UX metric is a clear understanding of what users want to achieve and where they struggle. I start by conducting qualitative research such as user interviews, usability tests, and field observations. These methods reveal the tasks users perform and the obstacles they face. For example, during a usability test for an e-commerce app, I noticed users hesitated at the checkout page. This hesitation became a focus area for metric development. Step 2: Identify Key User Journeys and Tasks Next, I map out the critical user journeys and tasks that drive the product’s success. These are the moments where users interact most with the product and where issues can cause the biggest impact. In the e-commerce example, the checkout process, product search, and account creation were key journeys. I focused on metrics that could track user behavior in these areas. Step 3: Define Quantitative Metrics Linked to User Behavior With user goals and journeys clear, I translate qualitative insights into measurable metrics. These might include: Task completion rate Time on task Error rate Drop-off points Frequency of help requests For the checkout page, I tracked how many users completed the purchase, how long they took, and where they abandoned the process. Step 4: Set Thresholds for Early Warnings Metrics alone don’t help unless you know when to act. I set thresholds based on historical data or industry benchmarks. For example, if the task completion rate drops below 80%, or time on task increases by 30%, it triggers an alert. These thresholds act as early warnings, signaling that something may be wrong and needs investigation. Dashboard displaying UX metrics with early-warning alerts Step 5: Continuously Monitor and Refine Metrics Building early-warning metrics is not a one-time task. I set up dashboards and regular reports to monitor these metrics continuously. When an alert triggers, I dig deeper with additional research to understand the root cause. Over time, I refine the metrics and thresholds based on new data and changing user behavior. This ongoing process keeps the UX team informed and ready to act. Practical Tips for Building Your Own Early-Warning UX Metrics Start small: Focus on a few key tasks or journeys that matter most to your users. Use mixed methods: Combine qualitative research with quantitative data for a full picture. Involve your team: Share metrics with designers, developers, and product managers to get buy-in. Automate monitoring: Use tools like Google Analytics, Hotjar, or custom dashboards to track metrics automatically. Act on alerts: Treat early warnings as opportunities to improve, not just data points. Real-World Example: Improving a Mobile Banking App In one project, I worked with a mobile banking app that had a high drop-off rate during the funds transfer process. By combining user interviews and analytics, I identified confusion around the confirmation screen. I built early-warning metrics to track: Number of users reaching the confirmation screen Time spent on the screen Drop-off rate before final submission When the drop-off rate exceeded 15%, the team investigated and redesigned the confirmation screen with clearer instructions. After the change, the drop-off rate dropped to 5%, improving user satisfaction and reducing support calls. Building early-warning UX metrics from research transforms how you manage user experience. It shifts your approach from reactive to proactive, helping you catch issues early and make informed decisions. Start by understanding your users deeply, choose meaningful metrics, and keep monitoring them regularly. This way, you’ll create products that feel intuitive and reliable, long before users get frustrated.

By Philip Burgess | UX Research Leader When I first started working with user experience (UX) metrics, I believed every key performance indicator (KPI) was essential and worth tracking indefinitely. Over time, I learned that some metrics lose their value as products evolve, user behaviors shift, or business goals change. Holding on to outdated KPIs can cloud decision-making and waste resources. Knowing when to retire or "sunset" a UX metric is just as important as choosing the right ones in the first place. In this post, I’ll share my experience with identifying when a UX metric has outlived its usefulness and offer practical advice on how to sunset KPIs effectively. Dashboard showing UX metrics with highlighted data Why Some UX Metrics Become Less Useful Over Time At the start of a project, teams often pick KPIs based on initial goals like increasing user engagement or reducing errors. These metrics help track progress and guide design decisions. But as the product matures, the context changes: User behavior evolves : Features that once drove engagement may become standard or obsolete. Business priorities shift : The focus might move from acquisition to retention or from speed to accessibility. Data quality issues arise : Some metrics become noisy or unreliable due to changes in tracking methods or user segments. For example, I worked on a mobile app where the "time on task" metric was critical early on. We wanted users to complete onboarding quickly. After several redesigns, the onboarding process became so streamlined that time on task no longer reflected user satisfaction or success. Yet, the team kept monitoring it, which led to misleading conclusions. Signs That a UX Metric Should Be Sunsetting You can tell a KPI has outlived its usefulness by watching for these signs: The metric no longer aligns with current goals If your company shifts focus from acquiring new users to improving retention, metrics like "number of new sign-ups" become less relevant. The metric shows little variation or improvement When a KPI plateaus and doesn’t provide insight into changes or improvements, it may have reached its limit. The metric causes confusion or misleads decisions If teams interpret the metric differently or it contradicts other data, it might be time to reconsider its value. The metric is difficult or costly to collect accurately Sometimes, tracking a KPI requires complex instrumentation that no longer justifies the insights gained. The metric is replaced by a better alternative New tools or methods might offer more meaningful or actionable data. In one project, we noticed that "click-through rate" on a feature was stable but didn’t correlate with user satisfaction or retention. After introducing a qualitative survey, we realized that users clicked out of curiosity but didn’t find the feature useful. This insight led us to sunset the click-through rate KPI and focus on satisfaction scores instead. How to Sunset a UX Metric Without Losing Valuable Insights Sunsetting a KPI doesn’t mean ignoring it completely. Here’s a process I follow to retire metrics thoughtfully: Review the metric’s history and relevance Look at how the metric has performed over time and whether it still supports your goals. Discuss with stakeholders Involve product managers, designers, analysts, and others to get diverse perspectives on the metric’s value. Identify replacement metrics if needed Find KPIs that better capture the current user experience or business objectives. Archive the metric data Keep historical data accessible for reference or trend analysis. Communicate the change clearly Explain why the metric is being retired and how new metrics will guide decisions. Monitor the impact After sunsetting, watch for any gaps in insights or unintended consequences. In one case, I helped a team sunset a "page load time" metric after improving infrastructure. We replaced it with "time to interactive," which better reflected user experience. The transition involved training the team on the new metric and keeping the old data for six months to compare trends. UX team collaborating on metrics strategy with charts on whiteboard Avoiding Common Pitfalls When Sunsetting Metrics Sunsetting KPIs can be tricky. Here are some mistakes I’ve seen and how to avoid them: Letting metrics linger too long Don’t wait until a metric becomes completely irrelevant. Regularly review KPIs every quarter or after major releases. Removing metrics without alternatives Always have a plan for what to track next to avoid blind spots. Ignoring qualitative data Numbers don’t tell the whole story. Combine metrics with user feedback to understand why a KPI may no longer work. Failing to communicate changes Sudden removal of KPIs can confuse teams and stakeholders. Transparency builds trust. Overloading dashboards with too many metrics Focus on a few meaningful KPIs rather than tracking everything. Final Thoughts on Managing UX Metrics Over Time Tracking UX metrics is essential, but so is knowing when to let go of those that no longer serve your goals. Sunsetting KPIs keeps your data focused, relevant, and actionable. It frees your team to concentrate on what truly matters for your users and product growth. If you’re unsure whether a metric still adds value, start by asking: Does this KPI help us make better decisions today? If the answer is no, it might be time to retire it and explore new ways to measure success.

By Philip Burgess | UX Research Leader When teams work on improving user experience, they often face a common challenge: too many metrics pulling them in different directions. This scatter can slow progress and create confusion about what really matters. I learned early in my UX career that focusing on a single, clear metric can transform how a team collaborates and delivers value. This metric is often called the North Star UX metric . It acts as a guiding light, helping everyone move toward the same goal. In this post, I’ll share how to define a North Star UX metric that truly aligns teams, with practical steps and examples from my experience. Dashboard showing key user engagement metrics What Is a North Star UX Metric and Why It Matters A North Star UX metric is one key measurement that captures the core value your product delivers to users. It’s not just any metric but the one that best reflects how well your product meets user needs and drives business success. Why focus on one metric? Because it simplifies decision-making. When everyone understands what success looks like, teams can prioritize features, fix issues, and innovate with clarity. Without this focus, teams risk chasing vanity metrics or conflicting goals. For example, a streaming service might choose total watch time as its North Star metric because it reflects user engagement and satisfaction better than just counting sign-ups. How to Choose the Right North Star UX Metric Choosing the right metric takes thought and collaboration. Here’s a process I’ve found effective: Understand your product’s core value What is the main benefit your product offers users? For a fitness app, it might be helping users complete workouts regularly. Identify user behaviors that reflect this value Look for actions users take that show they are getting value. For the fitness app, it could be the number of completed workout sessions per week. Check if the metric is measurable and actionable You need reliable data and the ability to influence the metric through design and development. Validate with stakeholders Make sure product managers, designers, developers, and marketers agree on the chosen metric. Alignment here is crucial. Test and iterate Sometimes the first choice isn’t perfect. Track the metric and see if it drives the right outcomes. Adjust if needed. Examples of Effective North Star UX Metrics Different products require different metrics. Here are some examples from various industries: E-commerce site: Percentage of users who add items to cart and complete checkout SaaS product: Number of active users completing key workflows weekly News app: Average time spent reading articles per session Educational platform: Number of lessons completed per user per month Each of these metrics reflects a meaningful user action tied to the product’s value. How a North Star Metric Aligns Teams in Practice I once worked with a team struggling to improve a mobile app. Designers focused on UI polish, developers on performance, and marketers on acquisition. Without a shared goal, efforts felt scattered. We introduced a North Star metric: weekly active users completing a core task . This simple focus changed everything. Designers prioritized usability improvements that helped users complete the task faster. Developers optimized features that supported this flow. Marketers targeted campaigns to attract users likely to engage deeply. The result was a 25% increase in task completion within three months. The team felt more connected and motivated because everyone knew what success looked like. Whiteboard filled with UX metric ideas and team collaboration notes Tips for Keeping Your North Star Metric Relevant A North Star metric isn’t set in stone. As your product evolves, so should your focus. Here are some tips to keep it useful: Review regularly Schedule quarterly reviews to assess if the metric still reflects your product’s core value. Combine with supporting metrics Use other metrics to provide context but keep the North Star as the main focus. Communicate progress clearly Share updates on the metric with the whole team to maintain alignment and motivation. Encourage cross-team collaboration Use the metric as a rallying point for different teams to work together. Final Thoughts on Defining a North Star UX Metric Choosing one clear UX metric can transform how your team works and the value your product delivers. It focuses energy, simplifies decisions, and creates a shared sense of purpose. Start by understanding your product’s core value, pick a measurable user behavior that reflects it, and get buy-in from your team.

By Philip Burgess | UX Research Leader When I first started working in UX research, measuring user experience felt like trying to catch smoke with my bare hands. We relied heavily on surveys, interviews, and manual observation. These methods gave us valuable insights but often lacked precision and speed. Today, artificial intelligence (AI) is reshaping how we measure UX research, making the process faster, more accurate, and more insightful. I want to share how AI has transformed my approach to UX research measurement and what it means for the future of design. AI-powered UX analytics dashboard showing user behavior patterns Understanding Traditional UX Measurement Challenges Before AI entered the scene, UX research measurement had several limitations: Time-consuming data collection : Gathering user feedback through interviews or surveys took weeks or months. Subjective interpretation : Researchers had to manually analyze qualitative data, which could introduce bias. Limited scalability : It was difficult to analyze large user groups or complex interactions quickly. Delayed insights : By the time data was processed, user needs or behaviors might have shifted. I remember working on a project where we spent months collecting user feedback on a mobile app. By the time we analyzed the data, the market had already moved on, and some of our findings felt outdated. This experience made me eager to find better ways to measure UX. How AI Enhances UX Research Measurement AI brings several key improvements to UX research measurement that I have seen firsthand: Faster Data Processing and Analysis AI algorithms can process vast amounts of data in minutes. For example, AI-powered tools analyze user interactions, clicks, and navigation paths automatically. This speed allows researchers to get near real-time feedback and adjust designs quickly. Objective Pattern Recognition AI can detect patterns in user behavior that humans might miss. Machine learning models identify common pain points or successful features by analyzing user sessions without human bias. This objectivity improves the reliability of UX measurements. Scalability Across User Groups With AI, it’s possible to analyze data from thousands or even millions of users simultaneously. This scalability helps capture diverse user experiences and ensures that UX improvements benefit a broader audience. Integration of Multimodal Data AI can combine different data types—such as eye tracking, facial expressions, voice tone, and click behavior—to provide a richer understanding of user experience. This multimodal analysis offers deeper insights than traditional methods. UX researcher analyzing AI-generated heatmaps and user flow data on a laptop Practical Examples of AI in UX Measurement In one project, I used an AI tool that tracked user mouse movements and clicks on a website. The AI identified areas where users hesitated or struggled, highlighting confusing navigation elements. This insight helped the design team simplify the menu structure, which increased user satisfaction scores by 20% after implementation. Another example involved sentiment analysis of user feedback collected from chatbots. AI processed thousands of comments to detect common frustrations and positive remarks. This automated analysis saved weeks of manual review and helped prioritize feature improvements based on real user emotions. What This Means for UX Researchers AI does not replace human judgment but enhances it. Here’s what I’ve learned about working with AI in UX measurement: Focus on interpretation : AI provides data and patterns, but researchers must interpret these insights in context. Stay critical : AI models can have biases or errors, so validating findings with human expertise remains essential. Embrace continuous learning : AI tools evolve rapidly; staying updated helps researchers use the best methods. Collaborate across teams : AI-generated insights are most valuable when shared with designers, developers, and product managers. Looking Ahead: The Future of UX Research Measurement AI will continue to evolve and bring new possibilities for UX measurement. I expect more personalized user experience tracking, where AI adapts to individual user preferences in real time. Also, advances in natural language processing will improve how we analyze open-ended feedback and conversations. For UX researchers, this means embracing AI as a partner that expands our capabilities. By combining AI’s speed and scale with human creativity and empathy, we can build products that truly meet user needs.

By Philip Burgess | UX Research Leader I remember the first time I relied heavily on AI-generated metrics to evaluate a user experience (UX) project. The numbers looked impressive: high engagement scores, positive sentiment analysis, and smooth navigation paths. I felt confident presenting these findings to the team, convinced we had nailed the user journey. But soon, real user feedback told a different story. The AI metrics had painted an overly optimistic picture, missing critical pain points that only human insight could reveal. This experience taught me that while AI tools offer powerful ways to analyze UX data, they can also create false confidence. In this post, I want to share why AI metrics sometimes mislead UX professionals, how to spot these pitfalls, and what you can do to get a clearer understanding of your users. Why AI Metrics Can Mislead UX Research AI tools analyze vast amounts of data quickly, spotting patterns and trends that might take humans much longer to find. This speed and scale make them attractive for UX research. However, AI metrics often rely on algorithms trained on limited or biased data sets, which can skew results. For example, sentiment analysis tools might misinterpret sarcasm or cultural nuances in user comments, labeling frustrated users as satisfied. Heatmaps generated by AI might highlight popular areas on a page but fail to explain why users hesitate or abandon tasks there. Another issue is that AI metrics often focus on quantitative data, such as click rates or time spent on a page, without capturing the qualitative context behind user behavior. This lack of context can lead to conclusions that seem solid but miss the real reasons users struggle or succeed. AI-generated UX metrics on a computer screen AI-generated UX metrics can look impressive but may hide important user frustrations. Real Examples of False Confidence from AI Metrics In one project, an AI tool showed a high completion rate for a checkout process on an e-commerce site. The team celebrated the success, assuming the design was effective. However, follow-up interviews revealed many users abandoned their carts due to confusing payment options. The AI metric measured only completed transactions, missing the drop-off points and reasons behind them. In another case, an AI-powered heatmap highlighted a button as the most clicked element on a landing page. The team assumed users found it helpful. But user testing showed that many clicks were accidental or users were clicking repeatedly out of confusion. The AI metric did not differentiate between intentional and frustrated clicks. These examples show how relying solely on AI metrics can lead to overconfidence and missed opportunities for improvement. How to Avoid False Confidence in UX Findings To get the most from AI tools without falling into the trap of false confidence, I recommend these strategies: Combine AI metrics with human insight Use AI to gather data quickly, but always validate findings with user interviews, usability testing, or surveys. Human feedback provides context that AI cannot capture. Understand the limitations of your AI tools Learn how your AI algorithms work and what data they use. Be cautious about accepting results at face value, especially if the data set is small or biased. Look for contradictions If AI metrics show positive results but user feedback tells a different story, dig deeper. Contradictions often reveal hidden issues. Focus on qualitative data Use AI to identify patterns, then explore those patterns with qualitative methods to understand the "why" behind user behavior. Test assumptions regularly Don’t assume AI metrics are always accurate. Regularly test your assumptions with fresh data and user input. UX researcher documenting user feedback during testing Combining AI data with direct user feedback uncovers deeper insights. Moving Forward with Balanced UX Research AI tools are valuable for UX research, but they should not replace human judgment. When I started blending AI metrics with direct user engagement, my confidence in findings became more grounded and actionable. The key is to treat AI as a helpful assistant, not a final authority. If you are using AI metrics in your UX work, take time to question the data, seek user voices, and remain open to surprises. This approach will help you avoid false confidence and build experiences that truly meet user needs. Remember, numbers alone don’t tell the whole story. The best UX insights come from combining data with empathy and curiosity.

By Philip Burgess | UX Research Leader When I first joined a UX research team, our work revolved around manual data collection, lengthy interviews, and hours spent sifting through notes. The process was slow, and the pressure to deliver actionable insights often felt overwhelming. Over the past few years, I’ve witnessed a significant shift in how AI tools have transformed our daily tasks and the expectations placed on our team. This change is not just about faster workflows but also about redefining what a UX researcher’s role looks like today. A UX researcher reviewing AI-generated user data on a laptop AI Tools Changing Data Collection and Analysis One of the biggest changes AI has brought to UX research is in data collection and analysis. Traditionally, gathering user feedback involved scheduling interviews, conducting surveys, and manually coding responses. This process could take weeks, especially when dealing with large user groups. Now, AI-powered tools can automatically transcribe interviews, detect sentiment, and even identify patterns in user behavior from vast datasets. For example, natural language processing (NLP) algorithms can analyze open-ended survey responses quickly, highlighting common themes without human bias. This capability allows our team to focus more on interpreting results and less on tedious data processing. In my experience, using AI tools has cut down analysis time by nearly 50%, enabling us to deliver insights faster and iterate on designs more rapidly. This shift means team members are expected to be comfortable working alongside AI, understanding its outputs, and validating findings rather than performing every step manually. New Skills and Roles Emerging in UX Research Teams With AI handling repetitive tasks, the expectations for UX researchers have evolved. Teams now look for members who can: Interpret AI-generated data critically Combine quantitative AI insights with qualitative human observations Design experiments that leverage AI capabilities Communicate complex AI findings clearly to stakeholders For instance, I had to learn how to use machine learning models to predict user preferences based on past behavior. This required me to understand basic data science concepts and collaborate more closely with data analysts. The role expanded beyond traditional research methods to include technical skills and strategic thinking. This change also means that UX research teams are becoming more interdisciplinary. We work alongside AI specialists, data scientists, and developers to create research frameworks that integrate AI tools effectively. The expectation is no longer just about gathering user feedback but about building smarter systems that learn and adapt. Balancing AI Automation with Human Insight While AI offers powerful advantages, it cannot replace the human element in UX research. One challenge I’ve faced is ensuring that AI-generated insights do not overlook subtle user emotions or cultural nuances. AI can identify trends but may miss the context behind user behaviors. Our team has learned to use AI as a support tool rather than a decision-maker. For example, AI can flag unusual user patterns, but researchers must investigate further to understand the reasons. This balance requires critical thinking and empathy, skills that remain essential despite technological advances. Expectations now include the ability to question AI outputs and validate them through human-centered methods. This approach helps maintain research quality and ensures that designs truly meet user needs. UX research team collaborating with AI data visualizations on a screen Impact on Project Timelines and Deliverables AI has accelerated many parts of the UX research process, which changes how teams plan projects. Faster data analysis means shorter research cycles and more frequent testing. This speed raises expectations for continuous delivery of insights throughout the product development lifecycle. In one project, we used AI to monitor user interactions in real time, allowing us to identify pain points as they emerged. This proactive approach helped the design team make quick adjustments, improving the user experience before launch. However, this faster pace also demands better project management and clear communication. Teams must set realistic goals for what AI can achieve and avoid overreliance on automation. Managing expectations internally and with stakeholders is crucial to maintain trust and deliver meaningful results. Preparing for the Future of UX Research The integration of AI into UX research is still evolving, and teams must stay adaptable. Continuous learning is essential to keep up with new tools and methods. I recommend UX researchers: Explore AI-powered research platforms Develop data literacy and basic coding skills Collaborate with AI experts to understand tool capabilities Maintain a user-first mindset despite technological changes By embracing AI while preserving human insight, UX research teams can deliver richer, faster, and more accurate findings. This balance will shape the future of user experience design and the role of researchers within it. The shift I’ve experienced shows that AI is not just a tool but a partner in research. It raises the bar for what teams can achieve and challenges us to grow our skills. For anyone in UX research, the next step is clear: learn to work with AI and use it to deepen your understanding of users.

By Philip Burgess | UX Research Leader When you talk about a study during a job interview, hiring managers are not just hearing your words. They are listening for specific signals that show how you think, communicate, and apply knowledge. I’ve learned this the hard way after several interviews where I thought I nailed the explanation, only to realize later what I missed. Understanding what hiring managers focus on can help you present your study clearly and confidently, making a stronger impression. Hiring manager listening carefully to a study explanation Clarity and Simplicity One of the first things hiring managers listen for is how clearly you explain the study. They want to see if you can break down complex information into simple terms. If your explanation sounds like a jumble of jargon or technical details, it becomes hard to follow. Instead, focus on the core idea of the study and why it matters. For example, instead of saying, “The study used a multivariate regression analysis to determine the correlation between variables,” try, “The study looked at how different factors relate to each other to find the strongest connection.” This shows you understand the study deeply enough to explain it simply. Purpose and Relevance Hiring managers want to know why the study is important. When I explain a study, I always highlight its purpose early on. What question was the study trying to answer? How does it connect to the job or industry? This helps the listener see the value in what you’re sharing. For instance, if you studied customer behavior, explain how the findings could help improve product design or marketing strategies. This shows you think beyond the study itself and understand its practical use. Your Role and Contribution If you were part of the study, hiring managers listen closely to your role. They want to know what you did, what skills you used, and how you contributed to the results. This is your chance to showcase your strengths. When I explain my involvement, I focus on specific tasks I handled, such as designing the survey, analyzing data, or presenting findings. Saying something like, “I led the data analysis using Excel and identified key trends that shaped our recommendations,” gives a clear picture of your contribution. Results and Impact Numbers and outcomes catch attention. Hiring managers listen for concrete results that came from the study. Did it lead to a change, a new insight, or a solution? Sharing measurable outcomes makes your explanation more convincing. For example, “The study showed a 20% increase in customer satisfaction after implementing the new process,” tells a story of success. If you don’t have exact numbers, focus on the impact in qualitative terms, like improved understanding or better decision-making. Printed report showing study results with charts and graphs How You Handle Questions During or after your explanation, hiring managers often ask questions to test your understanding. They listen for how you respond. Do you stay calm and clear? Can you explain further without confusion? This part reveals your depth of knowledge and communication skills. I remember one interview where I was asked to explain why a certain method was chosen. Instead of guessing, I admitted I wasn’t sure but described how I would find the answer. This honesty and problem-solving approach impressed the interviewer. Storytelling and Engagement A study can be dry if you just list facts. Hiring managers listen for how you tell the story behind the study. Engaging storytelling makes your explanation memorable and shows your passion. Try to include a brief narrative: what sparked the study, challenges faced, or surprising findings. For example, “We initially thought X would happen, but the data surprised us by showing Y.” This keeps the listener interested and shows your critical thinking. Avoiding Common Pitfalls From my experience, some mistakes weaken study explanations: Overloading with technical details Speaking too fast or too slow Using unclear or vague language Forgetting to connect the study to the job role Ignoring the listener’s reactions or questions Being mindful of these helps keep your explanation focused and effective. Practice Makes Perfect Explaining a study well takes practice. I recommend rehearsing your explanation with a friend or mentor who can give feedback. Record yourself to check for clarity and pacing. The more you practice, the more natural and confident you will sound. Final Thoughts When you explain a study in an interview, hiring managers listen for clarity, relevance, your role, results, and how you handle questions. They want to see that you understand the study deeply and can communicate it in a way that connects to the job. By focusing on these areas and practicing your explanation, you can turn a simple study description into a powerful story that highlights your skills and value.

By Philip Burgess | UX Research Leader When I first started applying for UX research roles, I quickly realized that having a portfolio was not just a nice-to-have but a critical part of the hiring process. However, not all portfolios are created equal. Hiring managers look for specific qualities that show your skills, thought process, and impact. If you want your portfolio to stand out, you need to understand what they value most. A UX research portfolio displayed on a laptop with user journey maps and notes UX Research Portfolio: Clear Storytelling and Structure One of the first things hiring managers notice is how well you tell the story of your projects. A portfolio should not just list tasks or deliverables. It needs to walk the reader through your process in a clear and engaging way. That means: Starting with the problem you aimed to solve Explaining your research goals and methods Showing how you collected and analyzed data Highlighting key insights and how they influenced design decisions Demonstrating the impact of your work on the product or business When I revamped my portfolio, I focused on creating a narrative for each project. I included context about the challenge, my role, and the outcomes. This approach helped hiring managers understand not just what I did but why it mattered. Emphasis on Research Methods and Rationale Hiring managers want to see that you know how to choose the right research methods for different situations. Your portfolio should clearly explain why you selected certain techniques, such as interviews, usability testing, surveys, or ethnographic studies. It’s not enough to say you did a usability test; you need to explain why it was the best fit for the problem and what you learned from it. For example, in one project, I chose diary studies because the product involved long-term user behavior. I described how this method helped uncover patterns that short-term tests missed. This kind of detail shows that you think critically about research design. Demonstration of Analytical Skills and Insights Data collection is only part of the job. Hiring managers want to see how you analyze data and turn it into actionable insights. Your portfolio should include examples of how you synthesized findings, identified patterns, and made recommendations. Use visuals like affinity diagrams, journey maps, or charts to illustrate your analysis. When I added these to my portfolio, I noticed that hiring managers appreciated the clarity and depth of my insights. They could see how my research informed design decisions and improved user experience. Collaboration and Communication UX research rarely happens in isolation. Hiring managers look for evidence that you can work well with designers, product managers, engineers, and stakeholders. Your portfolio should highlight how you communicated findings and influenced the team. For instance, I included examples of presentations I gave or workshops I facilitated. I also described how I adapted my communication style for different audiences, whether technical teams or executives. This shows that you understand the importance of collaboration and can make your research accessible. UX researcher presenting research findings on a whiteboard with charts and notes Focus on Impact and Outcomes Hiring managers want to know that your research made a difference. Your portfolio should clearly show the results of your work, such as improved usability metrics, increased user satisfaction, or business growth. In one project, I tracked how changes based on my research reduced user errors by 30%. Including these kinds of measurable outcomes makes your portfolio more compelling. If you don’t have exact numbers, qualitative feedback or testimonials can also demonstrate impact. Attention to Presentation and Usability Since UX research is about improving user experience, your portfolio itself should reflect good design principles. Hiring managers expect a clean, easy-to-navigate layout with readable text and clear visuals. Avoid clutter and make sure your portfolio works well on different devices. I spent time refining the design of my portfolio to ensure it was intuitive and visually appealing. This attention to detail reinforced my skills and professionalism. Tailoring Your Portfolio for the Role Finally, hiring managers appreciate when candidates tailor their portfolios to the specific job. That means highlighting projects relevant to the company’s industry, product type, or research needs. It also means emphasizing skills that match the job description. Before submitting my portfolio, I reviewed the job posting carefully and adjusted the order and focus of projects to align with what the employer sought. This extra step showed that I understood their priorities and was a good fit. Building a UX research portfolio that catches the eye of hiring managers takes effort, but it pays off. Focus on telling clear stories, explaining your methods, showing your analysis, and demonstrating impact. Make sure your portfolio is easy to use and tailored to the role you want. By doing this, you’ll present yourself as a thoughtful, skilled researcher ready to contribute.