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
"Different ops functions have different incentives; aligning those incentives could make leaps and bounds in collaboration."
Jon Fukuda Jake Burghardt Jose Coronado Natalie Dunbar Denise TillesAll the Ops: Successful cross-functional collaboration
September 10, 2025
"Anglos' State of Design Ops report is a really incredible baseline about where we are today."
Alana WashingtonTheme 3 Intro
October 1, 2021
"Combining the what we see in data with the why we get from user research is where true insights live."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
"Research run rampant — anyone feeling empowered to do research can sometimes cause quality challenges."
Nalini P. KotamrajuTwo Jobs in One: Being a “Leader who is a Researcher” and a “Researcher who is a Leader"
March 10, 2021
"Drivers continued the practice of hanging out in physical base camp spots despite platforms saying they wanted to get rid of them."
Prayag Narula Rida QadriHCI 2.0: Humanity Deserves the Attention that UX Research has to Offer
March 28, 2023
"Rapid low-fidelity prototypes let us get quick feedback without stakeholders focusing on minor visual details."
Yunyan Li Anna Le Jen KimUX Best Practices
June 11, 2021
"Our one metric that mattered was maximizing the number of VOС-tagged tickets solved – showing customer feedback made it to the roadmap."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Kill them with kindness. Be professional no matter how you’re feeling."
Dorelle RabinowitzThe Magic Word is Trust
June 15, 2018
"Anticipating and acting on risk turns uncertainty into inspiration for informed action."
Sarah BrooksTheme 3 Intro
December 10, 2021
Latest Books All books
Dig deeper with the Rosenbot
What strategies help UX teams translate usability findings into stakeholder-relevant outcomes like cost savings or risk reduction?
What are effective ways to network or build community when transitioning to a new industry?
What recent standards are improving interoperability between legacy EHR systems and startups?