Don’t call it AI: Turn words into numbers with quantitative ethnography
Summary
Business stakeholders are always pushing for greater efficiency, faster turnarounds. Qualitative researchers are always looking for more contact with users, and greater engagement with findings and reporting. Quantitative ethnography (and epistemic network analysis) offers a compromise: by trading structure and semantics for human sensemaking in the analysis part of research, perhaps both groups can get what they want.
I’ve had the opportunity to conduct quantitative ethnographic analyses in enterprise studies involving dozens of products, and impacting hundreds of thousands of end-users. Stakeholders were willing to accept a different kind of analysis, and engage more deeply with the process, in exchange for quicker answers.
In this talk, I’ll share how quantitative ethnography differs from qualitative ethnography, the tradeoffs you’ll have to make, and the kinds of results you can expect. This isn’t a tools talk, but you won’t need to do any math, either. I’ll close with a look into the near future, one where you can talk with as many users as will take your call with effectively zero additional analysis work; where you can have the analysis running live during your session, and have the user participate in the sensemaking process on-the-fly; and the dream of every product manager, one where stakeholders can have dashboards of evidence updated live as users talk.
Key Insights
-
•
Quantitative ethnography unifies qualitative ethnographic methods with quantitative statistical validation, avoiding typical mixed-methods back-and-forth.
-
•
Formalizing coding rules in a detailed code book is essential to scale qualitative insights and enable automation.
-
•
Defining mechanistic signifiers, such as keywords or phrase rules, is necessary to automate qualitative coding effectively.
-
•
Intra-sample statistical analysis uses each coded line as a data point rather than each respondent, enabling meaningful stats from small sample sizes.
-
•
Partnering with data scientists is critical because quantitative ethnography requires specialized, adjusted statistical methods that differ from conventional ones.
-
•
Researchers must regularly validate coding accuracy and statistical assumptions over time, a process called closing the interpretive loop.
-
•
Quantitative ethnography can scale from a handful of interviews to thousands of verbatim responses, maintaining rigor at all scales.
-
•
Epistemic network analysis helps identify and quantify relationships between qualitative codes within the text data.
-
•
Large language models can automate parts of quantitative ethnography but require sacrificing some control over code definitions and initial synthesis.
-
•
Quantitative ethnography opens the possibility for near-real-time insights by automating coding and saturation metrics during ongoing data collection.
Notable Quotes
"Business stakeholders push researchers for faster turnarounds and numbers, often favoring surveys over deep interviews."
"Quantitative ethnography isn’t mixed methods; it’s a unified method using both qualitative theory and quantitative validation."
"If you can’t come up with a rule for something, you can’t code it."
"Each coded line is a data point, which enables statistical power even with small numbers of respondents."
"Partner with data scientists to pick and adjust statistical tests because quantitative ethnography requires new assumptions."
"Closing the interpretive loop means regularly checking that your coding and stats hold up as new data arrives."
"Epistemic network analysis reveals meaningful connections between codes, suggesting but not proving why ideas cluster."
"Large language models cluster text using semantic relationships rather than shared vocabulary like traditional QDA."
"Using generative AI math lets you skip stats, but you lose control over what codes start your synthesis."
"If rules and stats update in real time, you could know when saturation is reached as data streams in."
Or choose a question:
More Videos
"94% of companies exclude disability from their diversity and inclusion initiatives, a major missed opportunity to advance accessibility."
Sheri Byrne-HaberThe Importance of Accessible Design Systems
January 8, 2024
"I got a no. The message I was hearing was, scale the best you can with what you have and make it work."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"Hypertext notes coexist on the same level and link to each other arbitrarily, creating emergent structures."
Jorge ArangoExploding the Notebook: How to Unlock the Power of Linked Notes (2nd of 3 seminars)
April 19, 2024
"Customer experience refers to the collection of interactions someone has with the brand, agnostic of channel or touchpoint."
Sarah WilliamsA Framework for CX Transformation
June 11, 2021
"Being extra flexible with scheduling and logistics leads to richer, more authentic insights from participants living paycheck to paycheck."
Yasmine KhanChecking Bias and Listening to Financially Vulnerable Americans
March 30, 2020
"Design operations is about being that resilient force on behalf of everyone else in your organization."
Dave MaloufTheme 3: Introduction and Provocation
January 8, 2024
"For OKRs to work, incentives have to focus on learning, customer centricity, and evidence-based decision making, not just delivery."
Jeff GothelfWho does what by how much?
November 20, 2025
"The hardest part is acting on feedback, which requires integrating tools and aligning multiple teams like research, product, marketing, and customer success."
Aleksandra Korczynska Caroline Jarrett Justyna ParmeeSurvey Tools
March 12, 2026
"The three in the box model is business, design, and technical representation, plus legal and compliance in regulated environments."
Frank DuranPartnership Playbook: Lessons Learned in Effective Partnership
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
Why is human storytelling stewardship still essential despite advances in AI and research democratization?
How have changes in communication technologies historically affected collective knowledge building, and what might AI's role be?
Why is interoperability and API access critical in modern user research tooling ecosystems?