https://myles-innovation.com/tags/product-requirements/Recent content in Product Requirements on MYLES — Strategy & Innovation ConsultingHugoenSun, 15 Mar 2026 00:00:00 +0100https://myles-innovation.com/blog/jtbd-product-requirements/Sun, 15 Mar 2026 00:00:00 +0100https://myles-innovation.com/blog/jtbd-product-requirements/<h2 id="the-most-dangerous-gap-in-product-development">The Most Dangerous Gap in Product Development</h2> <p>You did the research. You mapped the job. You captured 130 desired outcomes, surveyed 300 customers, and identified 15 outcomes with opportunity scores above 12. You know — with quantitative confidence — what your customers need.</p> <p>And then nothing happens.</p> <p>The JTBD insights sit in a research report. The product roadmap continues on its pre-existing trajectory. Engineering works on features that were decided before the research was complete. The beautifully constructed <a href="https://myles-innovation.com/blog/jtbd-canvas-guide/">JTBD Canvas</a> hangs on a wall, admired and ignored.</p>https://myles-innovation.com/blog/jtbd-vs-user-stories/Fri, 06 Mar 2026 00:00:00 +0100https://myles-innovation.com/blog/jtbd-vs-user-stories/<h2 id="a-false-competition-that-is-costing-product-teams-time">A False Competition That Is Costing Product Teams Time</h2> <p>Every few years, the product management community invents a new thing that is going to replace user stories. Design thinking replaced them. Now JTBD is replacing them. Except user stories keep showing up in sprint planning, and the teams that abandoned them for something more sophisticated often find themselves arguing about what a feature should do without any shared language to resolve the argument.</p>