<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Discovery-Quality on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/discovery-quality/</link><description>Recent content in Discovery-Quality on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/discovery-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>Good Discovery When AI Does the Talking</title><link>https://drlongnecker.com/blog/2026/07/ai-moderated-interviews-product-discovery-quality/</link><pubDate>Thu, 16 Jul 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/07/ai-moderated-interviews-product-discovery-quality/</guid><description>&lt;p&gt;Fifty customer interviews used to take three weeks: recruiting participants, scheduling calls, then waiting on a research team to synthesize the transcripts. That timeline shaped how product teams approached discovery for most of my career.&lt;/p&gt;
&lt;p&gt;An AI moderator can now run high volumes of structured interviews without the scheduling bottleneck that used to cap sample size. &lt;a href="https://www.nngroup.com/articles/ai-interviewers/"&gt;Nielsen Norman Group tested two AI interview tools in January 2026&lt;/a&gt; and found they capably handle structured, known-question interviews. That&amp;rsquo;s an independent study, not a vendor describing its own product. Vendors report even bigger numbers. &lt;a href="https://getperspective.ai/blog/2026-product-discovery-trends-what-300-teams-changed"&gt;Perspective AI&amp;rsquo;s review of roughly 300 product teams&lt;/a&gt; found a three-week research cycle compressing to about three days. Worth knowing, but a vendor&amp;rsquo;s account of its own customers is a different kind of evidence than NN/g&amp;rsquo;s controlled test.&lt;/p&gt;</description></item></channel></rss>