<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Qualitative Research on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/qualitative-research/</link><description>Recent content in Qualitative Research on MYLES — Strategy &amp; Innovation Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://myles-innovation.com/tags/qualitative-research/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Conduct a JTBD Interview: Questions, Process, and Template</title><link>https://myles-innovation.com/blog/jtbd-interview-guide/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/jtbd-interview-guide/</guid><description>&lt;h2 id="why-most-customer-interviews-produce-useless-data"&gt;Why Most Customer Interviews Produce Useless Data&lt;/h2&gt;
&lt;p&gt;Your team runs customer interviews. You hear phrases like &amp;ldquo;it would be great if&amp;hellip;&amp;rdquo; and &amp;ldquo;we really need a way to&amp;hellip;&amp;rdquo; and &amp;ldquo;our biggest pain point is&amp;hellip;&amp;rdquo; You diligently record these insights, synthesize them into themes, and feed them into your product roadmap.&lt;/p&gt;
&lt;p&gt;And then you build the features, launch them, and discover that adoption is lukewarm.&lt;/p&gt;
&lt;p&gt;The problem is not that you talked to the wrong customers. The problem is that you asked questions designed to extract feature requests when you should have been asking questions designed to extract desired outcomes. Traditional customer interviews are solution-oriented — they probe what customers want in a product. JTBD interviews are outcome-oriented — they probe what customers are trying to accomplish and how they measure success.&lt;/p&gt;</description></item></channel></rss>