Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Chad McAllister, PhD and Chad McAllister. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Chad McAllister, PhD and Chad McAllister or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.
Player FM - Podcast App
Go offline with the Player FM app!

542: Research methods that drive smarter product management decisions – with Nick Cawthon

16:38
 
Share
 

Manage episode 486402260 series 1538235
Content provided by Chad McAllister, PhD and Chad McAllister. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Chad McAllister, PhD and Chad McAllister or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

UX research practices to maximize product team resources

Watch on YouTube

TLDR

During my conversation with Nick Cawthon, a UX research expert who drives innovation at Gauge and teaches at the California College of Arts, we explored how product teams can strengthen their customer research capabilities without slowing down development. Nick emphasized that while technology is accelerating design and development at unprecedented speeds, successful product managers must balance this velocity with strategic research methods like ethnographic studies and observational research. The key insight: Investing time upfront in understanding what customers actually need—not just what they say they want—prevents building dead-on-arrival products and saves significant development resources. Nick shared practical approaches for resource-constrained teams, including guerrilla research techniques at conferences and mixed methods combining qualitative insights with quantitative data.

Key Topics

  • De-risking product development through upfront customer research investment
  • Ethnographic research methods
  • Rapid research strategies
  • AI integration in research
  • Guerrilla research techniques
  • Building research capabilities within existing product teams without dedicated researchers
  • Service design perspective for understanding complete customer journey experiences

Introduction

We’re talking about research methods and tools that drive smarter product decisions. This is research that helps you uncover what customers really need, not just what they say they want. If you’ve ever wondered how to get better insights without slowing down development, this episode is for you. You’ll walk away with practical advice on how to strengthen your team’s research muscle, even if you don’t have a dedicated researcher.

To help us, our guest is Nick Cawthon. Nick has been shaping the UX and research space in San Francisco for decades. He’s spoken at Google’s Tech Talks, Stanford, and PARC. He is an adjunct professor at the California College of the Arts and a Data Science Program Mentor at the University of California. He now drives innovation at Gauge, which helps companies solve complex design challenges. They integrate mixed methods research approaches into product design process to create products customers want, need, and love.

The Evolution of UX Research in Product Development

Good product UX delights customers

The landscape of product development fundamentally shifted when Apple introduced the iPhone, and with it, a new understanding of what makes technology truly user-friendly. During my recent conversation with Nick Cawthon, a seasoned UX research expert who has been shaping the research space in San Francisco for decades, he reflected on this pivotal moment that transformed how we approach customer research methods.

Before 2010, Nick explained, anyone claiming to be a UX practitioner would raise eyebrows because the field simply wasn’t mainstream. The concept of user experience research was largely unknown outside specialized circles. However, the iPhone’s success sparked a question across the tech industry: Why do Apple’s products “just work” while others require extensive user manuals and troubleshooting?

The iPhone marked a fundamental shift from subjective design approaches to objective, research-driven product development. Nick described how designers previously operated from a place of personal expression, creating products based on individual aesthetic preferences rather than user needs. The iPhone era forced a dramatic change in methodology—designers could no longer rely on personal taste alone.

The transformation introduced behavioral sciences into mainstream product development. Research methods that were once confined to academic settings suddenly became essential tools for product teams. This evolution moved design from being an expression of self to a systematic approach focused on guiding users through experiences as intuitively as possible.

Nick noted that early attempts at understanding user behavior included primitive methods like heat maps and click tracking during the Web 1.0 era. These tools attempted to decode where users focused their attention, though the insights were often scattered and difficult to interpret.

This historical context matters for product managers because it highlights how recently customer research became integral to successful product development. Understanding this evolution helps explain why many organizations still struggle to implement effective research practices—they’re building capabilities that only became industry standard within the last fifteen years.

The shift from subjective to objective design thinking represents more than just a methodological change. It established the foundation for modern product management research strategies that prioritize user needs over internal assumptions, setting the stage for the sophisticated research approaches that drive successful products today.

The Need to Balance Speed with Strategic Thinking

One of the most pressing challenges facing product teams today is managing the tension between development velocity and strategic depth. The efficiency with which teams can move from concept to execution in both design and development is accelerating. At the same time, a deliberate slowdown is necessary in research and strategy phases. While teams can rapidly prototype and build, the most successful products emerge when organizations invest time in observational studies and ethnographic research before entering the development pipeline.

Fast Thinking (Execution)

Slow Thinking (Strategy)

Design tools
Component libraries
Automated development
Rapid prototyping

Ethnographic research
Observational studies
Strategic reflection
Customer empathy building

Product teams must understand which methods to choose based on the pace that allows for proper digestion and processing of insights. This isn’t about slowing down everything—it’s about strategic allocation of time resources. When development becomes more efficient, wise product leaders reinvest that saved time into better customer research and strategic thinking.

De-risking Product Development Through Customer Research

The concept of de-risking became central to Nick’s approach when working with clients who prioritized backend efficiency over frontend strategy. He developed this framework while consulting with an IT services firm that excelled at development execution but struggled with understanding whether they were building the right products for their clients.

Nick created the DOA (Dead on Arrival) framework, which helps teams identify products likely to fail before significant development resources are invested. This approach treats customer research methods as insurance policies that protect against building products nobody wants.

Ethnographic Research: Breaking Out of the Corporate Echo Chamber

Corporate environments naturally create what Nick called “vicious agreement”—a phenomenon where teams become trapped in cycles of mutual affirmation that prevent genuine innovation. Ethnographic research methods serve as an antidote to this problem by introducing outside perspectives into internal discussions. When research teams bring back authentic customer voices—complete with emotional reactions, unexpected pain points, and surprising use cases—it disrupts the comfortable internal narrative that teams have constructed.

Case Study: Global Ethnographic Research in Video Game Commerce

Product managers doing ethnography to understand customer needs

Nick shared an example of how ethnographic research methods can reveal cultural insights that transform product strategy. During the COVID-19 pandemic, he worked with a client who needed to understand how different subcultures within a multinational video game identified with each other and used in-game commerce features for buying and selling items.

Travel restrictions prevented traditional on-site ethnographic research, but the client needed deep cultural insights from seven different countries. Nick had to completely reimagine his research approach, coordinating with local interviewers and photographers across Brazil, Japan, France, the United Kingdom, Canada, and the United States.

This remote ethnographic research strategy proved remarkably effective. Rather than trying to understand global customers from a single perspective, Nick’s team gathered authentic voices from each region, documenting how different subcultures expressed their identity through virtual items and digital commerce within the game environment.

Cultural Insights That Shaped Product Strategy

The research revealed profound cultural differences that directly impacted product development decisions. Each country’s players approached virtual identity and commerce in fundamentally different ways, reflecting deeper cultural values that traditional market research might have missed.

These cultural insights directly informed product strategy in ways that would have been impossible without ethnographic research. The video game company knew which players were connected through their platform’s social features, enabling them to create targeted recommendation systems based on cultural preferences.

Rapid Research Methods for Time-Pressured Teams

Most product teams face the reality of competing priorities and compressed timelines, making extensive ethnographic studies seem impractical. Nick addressed this challenge by emphasizing that rapid research methods can be highly effective when designed with the same attention to user experience that teams apply to their actual products.

Like products, surveys themselves also need high quality UX. When someone agrees to participate in a survey or research study, they’re essentially becoming a user of your research process. If that experience is frustrating, confusing, or poorly designed, participants will abandon the research just like users abandon poorly designed products.

The mathematics of participant attention are unforgiving. Nick explained that researchers typically have five minutes of genuine participant attention, maybe ten minutes if compensation is involved. Within that narrow window, every aspect of the research experience must be carefully crafted to maintain engagement and gather meaningful insights.

Designing Elegant Surveys

The key to successful rapid research lies in creating elegant forms—survey instruments that feel pleasurable rather than burdensome to complete. These research tools avoid repetitive questions, maintain clear logical flow, and respect participants’ time investment.

Poor Survey Design

Elegant Survey Design

Repetitive questions
Confusing logic flow
Poor user experience
High abandonment rates
Unreliable data quality

Clear, focused questions
Logical conditional routing
Pleasurable completion experience
High completion rates
Quality insights gathered

Managing the Data Volume Challenge

Nick warned that increased data collection capabilities create new challenges. With more data comes the responsibility for more sophisticated analysis and interpretation. Teams must feel confident that their research questions are correct before launching large-scale data collection efforts.

The ease of survey deployment can tempt teams to gather data without sufficient strategic thinking about what they actually need to learn. Nick emphasized the importance of defining clear research objectives before designing any rapid research instrument, regardless of how simple the technology makes the deployment process.

Mixed Methods Approach: Combining Qualitative and Quantitative Research

The most valuable research insights emerge when teams combine the emotional depth of qualitative research with the statistical validation of quantitative data. Nick shared his philosophy about creating research approaches that preserve authentic human voices while providing the numerical evidence that drives organizational decision-making.

Nick described observing a colleague present research findings for a financial services company that demonstrated both the power and limitations of traditional research presentation methods. The presentation included all the expected elements: sticky notes, organized boards, pull quotes organized by themes, and detailed tables breaking down user needs by jobs-to-be-done frameworks and pain points.

However, Nick noted what was missing from this otherwise comprehensive research presentation: the actual voices of the human beings who had provided these insights. The research had been processed and organized in ways that removed the emotional context, tone, and sentiment that make customer feedback truly compelling and actionable.

Preserving Human Emotion in Research

Product managers must consider emotions in customer research

Nick recommended a video production approach to research presentation. Rather than simply organizing quotes into categories, he suggested creating supercuts of customer voices around specific themes. These compilations allow stakeholders to hear the actual language, tone, and emotional inflection that customers use when discussing problems or experiences.

The themes that emerge from this approach carry much more emotional weight when presented through actual customer voices rather than sanitized summaries. This emotional connection often drives more meaningful organizational change than statistical data alone.

When research involves written feedback, surveys, or other text-based data collection, Nick emphasized the importance of mapping those responses back to real human stories. This might require developing personas or conducting follow-up interviews, but the effort to maintain human connection in research findings significantly improves their impact.

Traditional Research Presentation

Mixed Methods with Human Voice

Organized sticky notes
Categorized themes
Statistical summaries

Pain point tables
Abstract insights

Video compilations of voices
Emotional tone preserved
Human stories maintained
Statistical validation included
Actionable insights with context

The Risk of Sanitizing Customer Feedback

During our conversation, I raised concerns about how organizations often sanitize customer feedback as it moves through internal processes. Teams learn valuable insights from customer research, then translate authentic customer language into corporate jargon before presenting findings to leadership.

Nick acknowledged this issue, particularly when research involves internal feedback that might reflect poorly on specific teams or individuals. He noted the delicate balance required when presenting customer feedback that might implicate someone’s job performance or strategic decisions.

Nick suggested a democratic approach to managing this challenge. Rather than filtering or sanitizing customer feedback, he recommended providing leadership with access to complete, unfiltered research data while presenting interpreted insights as examples rather than definitive conclusions.

This approach positions researchers as facilitators who demonstrate possible interpretations while allowing stakeholders to examine source material and draw their own conclusions. This transparency reduces the appearance of researcher bias while ensuring that authentic customer voices remain accessible to decision-makers.

Practical Research Strategies for Resource-Constrained Teams

Most product teams don’t have the luxury of dedicated researchers or extensive research budgets, but Nick shared practical strategies for gathering meaningful customer insights without significant resource investments. His approach focuses on being strategic about when, where, and how to connect with target customers.

Nick introduced the concept of guerrilla research through an example from his work with a highly technical and typically inaccessible target audience. His client needed insights from infrastructure DevOps professionals—individuals who Nick described as reclusive, introverted, and well-paid professionals who were nearly impossible to reach through traditional research methods.

These technical professionals typically avoided marketing outreach and weren’t easily influenced by conventional research recruitment approaches. However, Nick discovered that several times per year, these same individuals emerged from their usual isolation to attend industry conferences and networking events focused on open source technologies, AWS, and similar technical gatherings.

Nick attended these conference to talk with DevOps professionals. He analyzed their social media feeds and conference communications to identify when target personas would be attending specific events. Nick would then arrange brief research conversations between conference sessions, leveraging the natural networking atmosphere that conferences create.

This approach proved remarkably effective for reaching specialized personas who would be impossible to recruit through traditional methods. The conference environment created a natural context for professional conversations, and participants were often more willing to share honest feedback about products and services within the industry networking atmosphere.

Traditional Recruitment Challenges

Guerrilla Research Solutions

Hard-to-reach personas
Expensive recruitment costs
Low response rates
Artificial research environments
Limited access to specialists

Natural networking environments
Cost-effective access
Higher engagement rates
Authentic professional context
Direct access to specialists

Capturing Authentic Feedback

Nick shared an example of gathering feedback like “the one thing I hate most about your product,” delivered with the kind of directness that comes from peer-to-peer professional conversations. This level of honest, unfiltered feedback is often more valuable than carefully moderated focus group discussions or formal interview responses.

Budget and Time Management

For product teams concerned about research budgets, Nick pointed out that good researchers are available for project-based work that can be built into development budgets. However, he identified time allocation as often being more challenging than budget constraints.

The key insight for product managers involves strategic scheduling decisions. When building project timelines, teams must decide whether to front-load time investment in design and development phases or allocate time for research and strategy upfront. Nick strongly advocated for the latter approach.

Conclusion

The insights Nick Cawthon shared reveal that customer research represents far more than a preliminary step in product development—it’s a strategic capability that determines whether teams build products customers actually need or waste resources on solutions nobody wants. As AI tools accelerate design and development processes at unprecedented speeds, the most successful product teams will be those that reinvest efficiency gains into deeper customer understanding rather than simply faster delivery cycles. The democratization of research tools means that sophisticated customer insights are now accessible to any product team willing to develop systematic research capabilities, regardless of budget constraints or dedicated research personnel.

The path forward requires balancing technological acceleration with human understanding, treating research design with the same rigor applied to product design, and maintaining authentic customer voices throughout the product development process. Product managers who develop research skills, cultivate genuine customer empathy, and master the art of translating human needs into technical solutions will create sustainable competitive advantages that pure technological capabilities cannot replicate. In an era where development tools become quickly commoditized, deep customer understanding remains a differentiating factor that drives breakthrough products and lasting business success.

Useful Links

Innovation Quote

“Specialization is for insects.” – Kevin Farnham, Nick’s professor

Application Questions

1. Breaking Out of Echo Chambers: How could you identify whether your product team is trapped in “vicious agreement” about customer needs, and what specific steps could you take to introduce authentic external customer voices into your next strategic planning session?

2. Time Investment Strategy: Given your current project timelines, how could you reallocate time from design and development phases to invest more heavily in upfront customer research, and what efficiency gains from AI tools could you leverage to enable this strategic shift?

3. Guerrilla Research Implementation: How could your team use industry conferences, professional events, or online communities to conduct “guerrilla research” with hard-to-reach customer personas, and what specific approaches would work best for your target audience?

4. Service Design Perspective: How could you expand your current customer research beyond end-users to include all stakeholders affected by your product (like customer support teams, implementation specialists, or business partners), and what operational challenges might you discover that traditional user research would miss?

5. Mixed Methods Integration: How could you combine qualitative customer stories with quantitative validation in your next research presentation to preserve authentic customer voices while providing the statistical evidence your stakeholders expect, and what tools or techniques would help you maintain the emotional impact of customer feedback?

Bio

Product Manager Interview - Nick Cawthon

Nick Cawthon has been shaping the UX and research space in San Francisco for decades. He’s spoken at Google’s Tech Talks, Stanford, and PARC. He is an adjunct professor at the California College of the Arts and a Data Science Program Mentor at the University of California. He now drives innovation at Gauge, which helps companies solve complex design challenges. They integrate mixed methods research approaches into product design process to create products customers want, need, and love.

Thanks!

Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below.

Source

  continue reading

340 episodes

Artwork
iconShare
 
Manage episode 486402260 series 1538235
Content provided by Chad McAllister, PhD and Chad McAllister. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Chad McAllister, PhD and Chad McAllister or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

UX research practices to maximize product team resources

Watch on YouTube

TLDR

During my conversation with Nick Cawthon, a UX research expert who drives innovation at Gauge and teaches at the California College of Arts, we explored how product teams can strengthen their customer research capabilities without slowing down development. Nick emphasized that while technology is accelerating design and development at unprecedented speeds, successful product managers must balance this velocity with strategic research methods like ethnographic studies and observational research. The key insight: Investing time upfront in understanding what customers actually need—not just what they say they want—prevents building dead-on-arrival products and saves significant development resources. Nick shared practical approaches for resource-constrained teams, including guerrilla research techniques at conferences and mixed methods combining qualitative insights with quantitative data.

Key Topics

  • De-risking product development through upfront customer research investment
  • Ethnographic research methods
  • Rapid research strategies
  • AI integration in research
  • Guerrilla research techniques
  • Building research capabilities within existing product teams without dedicated researchers
  • Service design perspective for understanding complete customer journey experiences

Introduction

We’re talking about research methods and tools that drive smarter product decisions. This is research that helps you uncover what customers really need, not just what they say they want. If you’ve ever wondered how to get better insights without slowing down development, this episode is for you. You’ll walk away with practical advice on how to strengthen your team’s research muscle, even if you don’t have a dedicated researcher.

To help us, our guest is Nick Cawthon. Nick has been shaping the UX and research space in San Francisco for decades. He’s spoken at Google’s Tech Talks, Stanford, and PARC. He is an adjunct professor at the California College of the Arts and a Data Science Program Mentor at the University of California. He now drives innovation at Gauge, which helps companies solve complex design challenges. They integrate mixed methods research approaches into product design process to create products customers want, need, and love.

The Evolution of UX Research in Product Development

Good product UX delights customers

The landscape of product development fundamentally shifted when Apple introduced the iPhone, and with it, a new understanding of what makes technology truly user-friendly. During my recent conversation with Nick Cawthon, a seasoned UX research expert who has been shaping the research space in San Francisco for decades, he reflected on this pivotal moment that transformed how we approach customer research methods.

Before 2010, Nick explained, anyone claiming to be a UX practitioner would raise eyebrows because the field simply wasn’t mainstream. The concept of user experience research was largely unknown outside specialized circles. However, the iPhone’s success sparked a question across the tech industry: Why do Apple’s products “just work” while others require extensive user manuals and troubleshooting?

The iPhone marked a fundamental shift from subjective design approaches to objective, research-driven product development. Nick described how designers previously operated from a place of personal expression, creating products based on individual aesthetic preferences rather than user needs. The iPhone era forced a dramatic change in methodology—designers could no longer rely on personal taste alone.

The transformation introduced behavioral sciences into mainstream product development. Research methods that were once confined to academic settings suddenly became essential tools for product teams. This evolution moved design from being an expression of self to a systematic approach focused on guiding users through experiences as intuitively as possible.

Nick noted that early attempts at understanding user behavior included primitive methods like heat maps and click tracking during the Web 1.0 era. These tools attempted to decode where users focused their attention, though the insights were often scattered and difficult to interpret.

This historical context matters for product managers because it highlights how recently customer research became integral to successful product development. Understanding this evolution helps explain why many organizations still struggle to implement effective research practices—they’re building capabilities that only became industry standard within the last fifteen years.

The shift from subjective to objective design thinking represents more than just a methodological change. It established the foundation for modern product management research strategies that prioritize user needs over internal assumptions, setting the stage for the sophisticated research approaches that drive successful products today.

The Need to Balance Speed with Strategic Thinking

One of the most pressing challenges facing product teams today is managing the tension between development velocity and strategic depth. The efficiency with which teams can move from concept to execution in both design and development is accelerating. At the same time, a deliberate slowdown is necessary in research and strategy phases. While teams can rapidly prototype and build, the most successful products emerge when organizations invest time in observational studies and ethnographic research before entering the development pipeline.

Fast Thinking (Execution)

Slow Thinking (Strategy)

Design tools
Component libraries
Automated development
Rapid prototyping

Ethnographic research
Observational studies
Strategic reflection
Customer empathy building

Product teams must understand which methods to choose based on the pace that allows for proper digestion and processing of insights. This isn’t about slowing down everything—it’s about strategic allocation of time resources. When development becomes more efficient, wise product leaders reinvest that saved time into better customer research and strategic thinking.

De-risking Product Development Through Customer Research

The concept of de-risking became central to Nick’s approach when working with clients who prioritized backend efficiency over frontend strategy. He developed this framework while consulting with an IT services firm that excelled at development execution but struggled with understanding whether they were building the right products for their clients.

Nick created the DOA (Dead on Arrival) framework, which helps teams identify products likely to fail before significant development resources are invested. This approach treats customer research methods as insurance policies that protect against building products nobody wants.

Ethnographic Research: Breaking Out of the Corporate Echo Chamber

Corporate environments naturally create what Nick called “vicious agreement”—a phenomenon where teams become trapped in cycles of mutual affirmation that prevent genuine innovation. Ethnographic research methods serve as an antidote to this problem by introducing outside perspectives into internal discussions. When research teams bring back authentic customer voices—complete with emotional reactions, unexpected pain points, and surprising use cases—it disrupts the comfortable internal narrative that teams have constructed.

Case Study: Global Ethnographic Research in Video Game Commerce

Product managers doing ethnography to understand customer needs

Nick shared an example of how ethnographic research methods can reveal cultural insights that transform product strategy. During the COVID-19 pandemic, he worked with a client who needed to understand how different subcultures within a multinational video game identified with each other and used in-game commerce features for buying and selling items.

Travel restrictions prevented traditional on-site ethnographic research, but the client needed deep cultural insights from seven different countries. Nick had to completely reimagine his research approach, coordinating with local interviewers and photographers across Brazil, Japan, France, the United Kingdom, Canada, and the United States.

This remote ethnographic research strategy proved remarkably effective. Rather than trying to understand global customers from a single perspective, Nick’s team gathered authentic voices from each region, documenting how different subcultures expressed their identity through virtual items and digital commerce within the game environment.

Cultural Insights That Shaped Product Strategy

The research revealed profound cultural differences that directly impacted product development decisions. Each country’s players approached virtual identity and commerce in fundamentally different ways, reflecting deeper cultural values that traditional market research might have missed.

These cultural insights directly informed product strategy in ways that would have been impossible without ethnographic research. The video game company knew which players were connected through their platform’s social features, enabling them to create targeted recommendation systems based on cultural preferences.

Rapid Research Methods for Time-Pressured Teams

Most product teams face the reality of competing priorities and compressed timelines, making extensive ethnographic studies seem impractical. Nick addressed this challenge by emphasizing that rapid research methods can be highly effective when designed with the same attention to user experience that teams apply to their actual products.

Like products, surveys themselves also need high quality UX. When someone agrees to participate in a survey or research study, they’re essentially becoming a user of your research process. If that experience is frustrating, confusing, or poorly designed, participants will abandon the research just like users abandon poorly designed products.

The mathematics of participant attention are unforgiving. Nick explained that researchers typically have five minutes of genuine participant attention, maybe ten minutes if compensation is involved. Within that narrow window, every aspect of the research experience must be carefully crafted to maintain engagement and gather meaningful insights.

Designing Elegant Surveys

The key to successful rapid research lies in creating elegant forms—survey instruments that feel pleasurable rather than burdensome to complete. These research tools avoid repetitive questions, maintain clear logical flow, and respect participants’ time investment.

Poor Survey Design

Elegant Survey Design

Repetitive questions
Confusing logic flow
Poor user experience
High abandonment rates
Unreliable data quality

Clear, focused questions
Logical conditional routing
Pleasurable completion experience
High completion rates
Quality insights gathered

Managing the Data Volume Challenge

Nick warned that increased data collection capabilities create new challenges. With more data comes the responsibility for more sophisticated analysis and interpretation. Teams must feel confident that their research questions are correct before launching large-scale data collection efforts.

The ease of survey deployment can tempt teams to gather data without sufficient strategic thinking about what they actually need to learn. Nick emphasized the importance of defining clear research objectives before designing any rapid research instrument, regardless of how simple the technology makes the deployment process.

Mixed Methods Approach: Combining Qualitative and Quantitative Research

The most valuable research insights emerge when teams combine the emotional depth of qualitative research with the statistical validation of quantitative data. Nick shared his philosophy about creating research approaches that preserve authentic human voices while providing the numerical evidence that drives organizational decision-making.

Nick described observing a colleague present research findings for a financial services company that demonstrated both the power and limitations of traditional research presentation methods. The presentation included all the expected elements: sticky notes, organized boards, pull quotes organized by themes, and detailed tables breaking down user needs by jobs-to-be-done frameworks and pain points.

However, Nick noted what was missing from this otherwise comprehensive research presentation: the actual voices of the human beings who had provided these insights. The research had been processed and organized in ways that removed the emotional context, tone, and sentiment that make customer feedback truly compelling and actionable.

Preserving Human Emotion in Research

Product managers must consider emotions in customer research

Nick recommended a video production approach to research presentation. Rather than simply organizing quotes into categories, he suggested creating supercuts of customer voices around specific themes. These compilations allow stakeholders to hear the actual language, tone, and emotional inflection that customers use when discussing problems or experiences.

The themes that emerge from this approach carry much more emotional weight when presented through actual customer voices rather than sanitized summaries. This emotional connection often drives more meaningful organizational change than statistical data alone.

When research involves written feedback, surveys, or other text-based data collection, Nick emphasized the importance of mapping those responses back to real human stories. This might require developing personas or conducting follow-up interviews, but the effort to maintain human connection in research findings significantly improves their impact.

Traditional Research Presentation

Mixed Methods with Human Voice

Organized sticky notes
Categorized themes
Statistical summaries

Pain point tables
Abstract insights

Video compilations of voices
Emotional tone preserved
Human stories maintained
Statistical validation included
Actionable insights with context

The Risk of Sanitizing Customer Feedback

During our conversation, I raised concerns about how organizations often sanitize customer feedback as it moves through internal processes. Teams learn valuable insights from customer research, then translate authentic customer language into corporate jargon before presenting findings to leadership.

Nick acknowledged this issue, particularly when research involves internal feedback that might reflect poorly on specific teams or individuals. He noted the delicate balance required when presenting customer feedback that might implicate someone’s job performance or strategic decisions.

Nick suggested a democratic approach to managing this challenge. Rather than filtering or sanitizing customer feedback, he recommended providing leadership with access to complete, unfiltered research data while presenting interpreted insights as examples rather than definitive conclusions.

This approach positions researchers as facilitators who demonstrate possible interpretations while allowing stakeholders to examine source material and draw their own conclusions. This transparency reduces the appearance of researcher bias while ensuring that authentic customer voices remain accessible to decision-makers.

Practical Research Strategies for Resource-Constrained Teams

Most product teams don’t have the luxury of dedicated researchers or extensive research budgets, but Nick shared practical strategies for gathering meaningful customer insights without significant resource investments. His approach focuses on being strategic about when, where, and how to connect with target customers.

Nick introduced the concept of guerrilla research through an example from his work with a highly technical and typically inaccessible target audience. His client needed insights from infrastructure DevOps professionals—individuals who Nick described as reclusive, introverted, and well-paid professionals who were nearly impossible to reach through traditional research methods.

These technical professionals typically avoided marketing outreach and weren’t easily influenced by conventional research recruitment approaches. However, Nick discovered that several times per year, these same individuals emerged from their usual isolation to attend industry conferences and networking events focused on open source technologies, AWS, and similar technical gatherings.

Nick attended these conference to talk with DevOps professionals. He analyzed their social media feeds and conference communications to identify when target personas would be attending specific events. Nick would then arrange brief research conversations between conference sessions, leveraging the natural networking atmosphere that conferences create.

This approach proved remarkably effective for reaching specialized personas who would be impossible to recruit through traditional methods. The conference environment created a natural context for professional conversations, and participants were often more willing to share honest feedback about products and services within the industry networking atmosphere.

Traditional Recruitment Challenges

Guerrilla Research Solutions

Hard-to-reach personas
Expensive recruitment costs
Low response rates
Artificial research environments
Limited access to specialists

Natural networking environments
Cost-effective access
Higher engagement rates
Authentic professional context
Direct access to specialists

Capturing Authentic Feedback

Nick shared an example of gathering feedback like “the one thing I hate most about your product,” delivered with the kind of directness that comes from peer-to-peer professional conversations. This level of honest, unfiltered feedback is often more valuable than carefully moderated focus group discussions or formal interview responses.

Budget and Time Management

For product teams concerned about research budgets, Nick pointed out that good researchers are available for project-based work that can be built into development budgets. However, he identified time allocation as often being more challenging than budget constraints.

The key insight for product managers involves strategic scheduling decisions. When building project timelines, teams must decide whether to front-load time investment in design and development phases or allocate time for research and strategy upfront. Nick strongly advocated for the latter approach.

Conclusion

The insights Nick Cawthon shared reveal that customer research represents far more than a preliminary step in product development—it’s a strategic capability that determines whether teams build products customers actually need or waste resources on solutions nobody wants. As AI tools accelerate design and development processes at unprecedented speeds, the most successful product teams will be those that reinvest efficiency gains into deeper customer understanding rather than simply faster delivery cycles. The democratization of research tools means that sophisticated customer insights are now accessible to any product team willing to develop systematic research capabilities, regardless of budget constraints or dedicated research personnel.

The path forward requires balancing technological acceleration with human understanding, treating research design with the same rigor applied to product design, and maintaining authentic customer voices throughout the product development process. Product managers who develop research skills, cultivate genuine customer empathy, and master the art of translating human needs into technical solutions will create sustainable competitive advantages that pure technological capabilities cannot replicate. In an era where development tools become quickly commoditized, deep customer understanding remains a differentiating factor that drives breakthrough products and lasting business success.

Useful Links

Innovation Quote

“Specialization is for insects.” – Kevin Farnham, Nick’s professor

Application Questions

1. Breaking Out of Echo Chambers: How could you identify whether your product team is trapped in “vicious agreement” about customer needs, and what specific steps could you take to introduce authentic external customer voices into your next strategic planning session?

2. Time Investment Strategy: Given your current project timelines, how could you reallocate time from design and development phases to invest more heavily in upfront customer research, and what efficiency gains from AI tools could you leverage to enable this strategic shift?

3. Guerrilla Research Implementation: How could your team use industry conferences, professional events, or online communities to conduct “guerrilla research” with hard-to-reach customer personas, and what specific approaches would work best for your target audience?

4. Service Design Perspective: How could you expand your current customer research beyond end-users to include all stakeholders affected by your product (like customer support teams, implementation specialists, or business partners), and what operational challenges might you discover that traditional user research would miss?

5. Mixed Methods Integration: How could you combine qualitative customer stories with quantitative validation in your next research presentation to preserve authentic customer voices while providing the statistical evidence your stakeholders expect, and what tools or techniques would help you maintain the emotional impact of customer feedback?

Bio

Product Manager Interview - Nick Cawthon

Nick Cawthon has been shaping the UX and research space in San Francisco for decades. He’s spoken at Google’s Tech Talks, Stanford, and PARC. He is an adjunct professor at the California College of the Arts and a Data Science Program Mentor at the University of California. He now drives innovation at Gauge, which helps companies solve complex design challenges. They integrate mixed methods research approaches into product design process to create products customers want, need, and love.

Thanks!

Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below.

Source

  continue reading

340 episodes

Wszystkie odcinki

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play