<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Customer Needs on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/customer-needs/</link><description>Recent content in Customer Needs 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-needs/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Write Outcome Statements That Drive Product Decisions</title><link>https://myles-innovation.com/blog/outcome-statements-guide/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/outcome-statements-guide/</guid><description>&lt;h2 id="the-sentence-structure-that-predicts-product-success"&gt;The Sentence Structure That Predicts Product Success&lt;/h2&gt;
&lt;p&gt;Here is a claim that will sound absurd until you see it in practice: the single biggest determinant of whether your next product succeeds or fails is the quality of a few hundred sentences.&lt;/p&gt;
&lt;p&gt;Not your engineering talent. Not your marketing budget. Not your competitive intelligence. Sentences.&lt;/p&gt;
&lt;p&gt;Specifically, &lt;strong&gt;outcome statements&lt;/strong&gt; — the precisely formatted expressions of customer needs that form the backbone of &lt;a href="https://myles-innovation.com/pillar/outcome-driven-innovation-guide/"&gt;Outcome-Driven Innovation&lt;/a&gt;. Get them right, and you have a quantifiable map of every opportunity in your market. Get them wrong, and you are surveying noise.&lt;/p&gt;</description></item><item><title>Jobs to Be Done Method: A Guide for Product Managers</title><link>https://myles-innovation.com/blog/jtbd-method-product-managers/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/jtbd-method-product-managers/</guid><description>&lt;h2 id="why-a-forty-year-old-insight-is-still-misunderstood"&gt;Why a Forty-Year-Old Insight Is Still Misunderstood&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;Jobs to Be Done&amp;rdquo; sounds like an MBA buzzword. And yes, the framework comes from Harvard — developed by Clayton Christensen, then operationalized into a rigorous methodology by Tony Ulwick. But the reason it persists, decades after its introduction, is not because consultants like selling it. It is because the core insight keeps proving itself correct.&lt;/p&gt;
&lt;p&gt;The insight: &lt;strong&gt;People do not buy products. They hire products to do a job in their lives.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>The Opportunity Algorithm: Finding Underserved Customer Needs</title><link>https://myles-innovation.com/blog/opportunity-algorithm/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/opportunity-algorithm/</guid><description>&lt;h2 id="the-formula-that-replaced-gut-feeling"&gt;The Formula That Replaced Gut Feeling&lt;/h2&gt;
&lt;p&gt;Every product team has the same argument: &amp;ldquo;Which customer needs should we address first?&amp;rdquo; In most organizations, this debate is settled by seniority, volume, or salesforce pressure. The VP&amp;rsquo;s pet feature wins. The customer who shouted loudest wins. The deal that is about to close wins.&lt;/p&gt;
&lt;p&gt;The Opportunity Algorithm replaces this dysfunction with mathematics. It is the quantitative engine of &lt;a href="https://myles-innovation.com/pillar/outcome-driven-innovation-guide/"&gt;Outcome-Driven Innovation&lt;/a&gt;, and it does something that no brainstorming session, empathy map, or NPS score can do: it tells you, with statistical confidence, exactly which customer needs are underserved, appropriately served, or overserved in your market.&lt;/p&gt;</description></item></channel></rss>