<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Industrial on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/industrial/</link><description>Recent content in Industrial 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/industrial/index.xml" rel="self" type="application/rss+xml"/><item><title>JTBD for B2B: How Enterprise Product Teams Use Jobs Theory</title><link>https://myles-innovation.com/blog/jtbd-b2b-enterprise/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/jtbd-b2b-enterprise/</guid><description>&lt;h2 id="jtbd-was-built-for-consumer-products-b2b-needs-something-different-right"&gt;JTBD Was Built for Consumer Products. B2B Needs Something Different. Right?&lt;/h2&gt;
&lt;p&gt;Wrong.&lt;/p&gt;
&lt;p&gt;This is the most common objection I hear when presenting Jobs to Be Done to B2B product teams: &amp;ldquo;Our market is different. We have buying committees, not individual consumers. Our sales cycles are 12 months, not 12 minutes. Our customers are engineers, not milkshake buyers. JTBD does not apply here.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;It applies here more than anywhere. And the reason is precisely the complexity that B2B teams cite as the objection.&lt;/p&gt;</description></item></channel></rss>