<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design Thinking on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/design-thinking/</link><description>Recent content in Design Thinking 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/design-thinking/index.xml" rel="self" type="application/rss+xml"/><item><title>ODI vs. Design Thinking: Complementary or Competing?</title><link>https://myles-innovation.com/blog/odi-vs-design-thinking/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/odi-vs-design-thinking/</guid><description>&lt;h2 id="the-framework-wars-are-a-distraction--mostly"&gt;The Framework Wars Are a Distraction — Mostly&lt;/h2&gt;
&lt;p&gt;Walk into any innovation team in Munich, Vienna, or Zurich and you will find two camps. One swears by Design Thinking — they have the Post-it notes, the empathy maps, and the prototyping labs to prove it. The other camp has quietly adopted Outcome-Driven Innovation and wonders why they spent years brainstorming in circles.&lt;/p&gt;
&lt;p&gt;The internet treats these as competing religions. They are not. But the relationship between them is more nuanced — and more lopsided — than the diplomatic &amp;ldquo;they&amp;rsquo;re complementary&amp;rdquo; answer most consultants give.&lt;/p&gt;</description></item><item><title>Design Thinking vs. Jobs to Be Done: What Works Better?</title><link>https://myles-innovation.com/blog/design-thinking-vs-jtbd/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/design-thinking-vs-jtbd/</guid><description>&lt;h2 id="two-frameworks-one-question"&gt;Two Frameworks, One Question&lt;/h2&gt;
&lt;p&gt;Design thinking and Jobs to Be Done — both promise better products through better customer understanding. Both have prominent advocates, impressive client references, and substantial consulting communities built around them.&lt;/p&gt;
&lt;p&gt;But they are fundamentally different in their logic, their methods, and what they actually produce. A product team that understands both can deploy them with precision. A product team that knows only one has blind spots.&lt;/p&gt;</description></item></channel></rss>