<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Innovation Mistakes on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/innovation-mistakes/</link><description>Recent content in Innovation Mistakes on MYLES — Strategy &amp; Innovation Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://myles-innovation.com/tags/innovation-mistakes/index.xml" rel="self" type="application/rss+xml"/><item><title>Why JTBD Fails: Common Mistakes and How to Avoid Them</title><link>https://myles-innovation.com/blog/jtbd-common-mistakes/</link><pubDate>Sat, 07 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/jtbd-common-mistakes/</guid><description>&lt;h2 id="we-tried-jtbd-it-didnt-work"&gt;&amp;ldquo;We Tried JTBD. It Didn&amp;rsquo;t Work.&amp;rdquo;&lt;/h2&gt;
&lt;p&gt;I have heard this sentence, or a version of it, at least a dozen times in the last five years. Always from a senior product manager or VP who invested real time and budget into a JTBD initiative, generated a job map, ran some interviews, produced a slide deck — and found that six months later, the product roadmap looked essentially identical to what it would have been without any of it.&lt;/p&gt;</description></item></channel></rss>