<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Customer Outcomes on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/customer-outcomes/</link><description>Recent content in Customer Outcomes 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/customer-outcomes/index.xml" rel="self" type="application/rss+xml"/><item><title>Customer Desired Outcomes: The Building Blocks of ODI</title><link>https://myles-innovation.com/blog/customer-desired-outcomes/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/customer-desired-outcomes/</guid><description>&lt;h2 id="the-concept-that-makes-odi-work"&gt;The Concept That Makes ODI Work&lt;/h2&gt;
&lt;p&gt;Every methodology has a core unit — the atom from which everything else is built. For Lean, it is waste. For Six Sigma, it is variation. For &lt;a href="https://myles-innovation.com/pillar/outcome-driven-innovation-guide/"&gt;Outcome-Driven Innovation&lt;/a&gt;, it is the &lt;strong&gt;customer desired outcome.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A desired outcome is the metric a customer uses to measure success when executing a job to be done. Not what they want to buy. Not the feature they request. Not the problem they complain about. The outcome — the specific, measurable result they are trying to achieve at each step of the job.&lt;/p&gt;</description></item><item><title>Agile Product Development with a Focus on Customer Outcomes</title><link>https://myles-innovation.com/blog/agile-product-development-customer-outcomes/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/agile-product-development-customer-outcomes/</guid><description>&lt;h2 id="agile-without-outcomes-is-just-fast-wrong"&gt;Agile Without Outcomes Is Just Fast Wrong&lt;/h2&gt;
&lt;p&gt;The promise of agile product development was compelling: shorter cycles, faster feedback, less waste from building the wrong things. Two decades after the Agile Manifesto, most software product teams work in some variant of agile. A growing proportion of hardware and industrial product teams have adopted agile-inspired elements. And yet the failure rate for product development — the proportion of products that fail to achieve meaningful market adoption — has not improved materially.&lt;/p&gt;</description></item></channel></rss>