<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Product Strategy on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/categories/product-strategy/</link><description>Recent content in Product Strategy 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/categories/product-strategy/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an Innovation Culture in Enterprise Organizations</title><link>https://myles-innovation.com/blog/innovation-culture-enterprise/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/innovation-culture-enterprise/</guid><description>&lt;h2 id="the-culture-delusion"&gt;The Culture Delusion&lt;/h2&gt;
&lt;p&gt;&amp;ldquo;We need to change our innovation culture.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;If I had a euro for every time a VP of Innovation said this to me, I could fund a reasonably sized Series A. It is the default diagnosis for every innovation failure: our products are mediocre because our culture does not support innovation. The prescription follows logically: change the culture.&lt;/p&gt;
&lt;p&gt;The result is a predictable parade of culture initiatives. Innovation labs. Hackathons. Failure celebrations (&amp;ldquo;fail fast, fail forward!&amp;rdquo;). Inspirational posters featuring Einstein quotes. Innovation ambassadors with colorful lanyards. Maybe a trip to Silicon Valley to absorb the California vibe.&lt;/p&gt;</description></item><item><title>From Customer Insights to Product Roadmap: The Translation Problem</title><link>https://myles-innovation.com/blog/customer-insights-product-roadmap/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/customer-insights-product-roadmap/</guid><description>&lt;h2 id="the-insight-graveyard"&gt;The Insight Graveyard&lt;/h2&gt;
&lt;p&gt;Every enterprise innovation team has one. A folder — digital or physical — full of research reports that nobody reads anymore. Customer interview transcripts. Ethnographic studies. Survey results. Design sprint outputs. Personas that were workshopped with great enthusiasm and then never referenced again.&lt;/p&gt;
&lt;p&gt;This is the insight graveyard. And its existence reveals the central failure of most enterprise product organizations: &lt;strong&gt;the inability to translate customer insights into roadmap decisions&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Innovation Metrics: Measuring What Matters Beyond Patent Counts</title><link>https://myles-innovation.com/blog/innovation-metrics-measurement/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/innovation-metrics-measurement/</guid><description>&lt;h2 id="the-vanity-metric-trap"&gt;The Vanity Metric Trap&lt;/h2&gt;
&lt;p&gt;How does your company measure innovation? If your answer includes patent counts, R&amp;amp;D spending as a percentage of revenue, number of ideas generated, or percentage of revenue from &amp;ldquo;new&amp;rdquo; products, you are measuring innovation theater — the appearance of innovation activity — rather than innovation effectiveness.&lt;/p&gt;
&lt;p&gt;These metrics are everywhere. Boards love them. Annual reports feature them. Innovation consultants benchmark against them. And they are, at best, weakly correlated with actual innovation outcomes.&lt;/p&gt;</description></item><item><title>Product Discovery: Methods for Finding What to Build Next</title><link>https://myles-innovation.com/blog/product-discovery-methods/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/product-discovery-methods/</guid><description>&lt;h2 id="the-backward-discovery-problem"&gt;The Backward Discovery Problem&lt;/h2&gt;
&lt;p&gt;Most enterprise product teams believe they do product discovery. They interview customers. They run surveys. They attend trade shows and listen to what the market is saying. They compile feature request lists from sales teams and support tickets.&lt;/p&gt;
&lt;p&gt;And yet, despite all this effort, their hit rate on new products hovers around the industry average: roughly six out of ten fail to meet business objectives.&lt;/p&gt;
&lt;p&gt;The problem is not that these teams skip discovery. The problem is that their discovery process is backward. They start with solutions and work back toward problems. They ask customers &amp;ldquo;what do you want?&amp;rdquo; instead of &amp;ldquo;what are you trying to accomplish?&amp;rdquo; They catalog feature requests instead of measuring unmet outcomes. They let the loudest voices — whether internal champions or key accounts — set the agenda.&lt;/p&gt;</description></item><item><title>Product Strategy for Enterprise Innovation Leaders</title><link>https://myles-innovation.com/pillar/product-strategy-enterprise-guide/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/pillar/product-strategy-enterprise-guide/</guid><description>&lt;h2 id="why-most-enterprise-product-strategies-fail-before-they-start"&gt;Why Most Enterprise Product Strategies Fail Before They Start&lt;/h2&gt;
&lt;p&gt;Here is a number that should disturb you: according to a 2023 study by the Product Development and Management Association (PDMA), &lt;strong&gt;40% of new products launched by established companies fail to meet their business objectives&lt;/strong&gt;. Not startups working with seed money and gut instinct — established enterprises with dedicated R&amp;amp;D budgets, experienced product teams, and decades of market knowledge.&lt;/p&gt;
&lt;p&gt;The problem is not a lack of strategy. Walk into any product planning meeting at a Fortune 500 company and you will find strategy documents. Plenty of them. The problem is that most enterprise product strategies are built on a foundation of sand: internal assumptions dressed up as customer insights, competitive benchmarking mistaken for differentiation, and roadmaps driven by the loudest executive rather than the most important customer outcome.&lt;/p&gt;</description></item><item><title>Product Strategy Frameworks: A Comparative Guide</title><link>https://myles-innovation.com/blog/product-strategy-frameworks/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/product-strategy-frameworks/</guid><description>&lt;h2 id="the-framework-problem"&gt;The Framework Problem&lt;/h2&gt;
&lt;p&gt;Enterprise product leaders are not short of frameworks. They are drowning in them. Porter&amp;rsquo;s Five Forces. Blue Ocean Strategy. Lean Startup. Design Thinking. Jobs to Be Done. The JTBD Growth Strategy Matrix. Each comes with its own books, consultants, certifications, and promises.&lt;/p&gt;
&lt;p&gt;The result is not clarity but confusion. Product teams cherry-pick elements from multiple frameworks without understanding their underlying assumptions. They apply startup methodologies to enterprise contexts. They use competitive analysis tools to answer customer needs questions. And they wonder why their product strategies produce middling results.&lt;/p&gt;</description></item><item><title>Product-Market Fit for B2B: Enterprise-Specific Considerations</title><link>https://myles-innovation.com/blog/product-market-fit-b2b/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/product-market-fit-b2b/</guid><description>&lt;h2 id="the-product-market-fit-myth-in-enterprise-b2b"&gt;The Product-Market Fit Myth in Enterprise B2B&lt;/h2&gt;
&lt;p&gt;Marc Andreessen&amp;rsquo;s famous formulation — &amp;ldquo;product-market fit means being in a good market with a product that can satisfy that market&amp;rdquo; — has become gospel in the startup world. And in the startup world, it works reasonably well. You launch a product, observe whether customers are pulling it out of your hands, and know within months whether you have fit.&lt;/p&gt;
&lt;p&gt;Try applying this to a crane manufacturer selling to construction companies across Europe. Or a medical device company with an 18-month regulatory approval cycle. Or an agricultural equipment maker whose customers buy once every seven years.&lt;/p&gt;</description></item><item><title>Value Proposition Design Using Jobs to Be Done</title><link>https://myles-innovation.com/blog/value-proposition-design-jtbd/</link><pubDate>Sun, 15 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/value-proposition-design-jtbd/</guid><description>&lt;h2 id="the-value-proposition-precision-problem"&gt;The Value Proposition Precision Problem&lt;/h2&gt;
&lt;p&gt;Every B2B company has a value proposition. Most of them sound the same.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;We deliver innovative solutions that help our customers improve efficiency and reduce costs.&amp;rdquo; Change the company name and this sentence could describe any industrial manufacturer in Europe. It communicates nothing specific. It differentiates from nothing. It resonates with no one in particular.&lt;/p&gt;
&lt;p&gt;The problem is not that product teams lack effort or intelligence. The problem is that traditional value proposition design methods — even well-regarded ones like Osterwalder&amp;rsquo;s Value Proposition Canvas — lack the precision needed to create propositions that genuinely resonate with specific customer segments.&lt;/p&gt;</description></item><item><title>Developing Product Strategy: From Vision to Roadmap</title><link>https://myles-innovation.com/blog/developing-product-strategy-vision-roadmap/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/developing-product-strategy-vision-roadmap/</guid><description>&lt;h2 id="what-passes-for-product-strategy-in-most-companies"&gt;What Passes for Product Strategy in Most Companies&lt;/h2&gt;
&lt;p&gt;Let us be direct: what gets called &amp;ldquo;product strategy&amp;rdquo; in most B2B companies is a PowerPoint presentation with a vision statement on slide three and a feature list on slide seventeen. In between: market trend observations, competitive comparisons, and an optimistic revenue projection that nobody seriously believes.&lt;/p&gt;
&lt;p&gt;That is not a strategy. That is a wish list with context.&lt;/p&gt;
&lt;p&gt;A real product strategy answers three questions with precision:&lt;/p&gt;</description></item><item><title>When to Engage Product Strategy Consultants (And When Not To)</title><link>https://myles-innovation.com/blog/product-strategy-consultants-when/</link><pubDate>Sun, 08 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/product-strategy-consultants-when/</guid><description>&lt;h2 id="the-honest-answer-no-consultant-will-give-you"&gt;The Honest Answer No Consultant Will Give You&lt;/h2&gt;
&lt;p&gt;Most articles about whether to hire product strategy consultants are written by product strategy consultants. That tells you something about their objectivity. I will give you a different answer — one that sometimes means recommending you do not hire us.&lt;/p&gt;
&lt;p&gt;The decision to engage external product strategy help is not primarily about capability. Most competent product organizations have capable people. The question is whether external expertise can change the outcome in a way that justifies the cost, the disruption, and the inevitable internal politics that come with outside involvement. Sometimes the answer is yes. Often it is no. The difference lies in the specific conditions your organization faces.&lt;/p&gt;</description></item><item><title>Innovation Portfolio Management: Balancing Core and New</title><link>https://myles-innovation.com/blog/innovation-portfolio-management/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/innovation-portfolio-management/</guid><description>&lt;h2 id="the-portfolio-that-manages-you"&gt;The Portfolio That Manages You&lt;/h2&gt;
&lt;p&gt;Most companies that believe they manage an innovation portfolio are actually managed by one. They have existing product lines that generate the revenue used to fund next-generation development. Those existing lines have customers, commitments, and internal advocates who are very good at making the case for incremental improvement. New growth opportunities have hypothetical future value and internal advocates who are newer, less senior, and less skilled at organizational politics.&lt;/p&gt;</description></item><item><title>Measuring Product Innovation: Metrics That Actually Matter</title><link>https://myles-innovation.com/blog/product-innovation-metrics/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/product-innovation-metrics/</guid><description>&lt;h2 id="the-measurement-theater-problem"&gt;The Measurement Theater Problem&lt;/h2&gt;
&lt;p&gt;Every VP of Product or Innovation I speak with can tell me how many new products they launched last year, how many patents their engineers filed, and what their R&amp;amp;D spending is as a percentage of revenue. Almost none of them can tell me whether those launches addressed the customer outcomes that were most underserved, what proportion of their R&amp;amp;D investment targeted genuinely unmet needs, or how the satisfaction of their customers&amp;rsquo; most important outcomes has changed over the past three years.&lt;/p&gt;</description></item><item><title>The Product Leader's Guide to Customer-Centric Decision Making</title><link>https://myles-innovation.com/blog/customer-centric-decision-making/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/customer-centric-decision-making/</guid><description>&lt;h2 id="the-gap-between-believing-in-customers-and-deciding-based-on-them"&gt;The Gap Between Believing in Customers and Deciding Based on Them&lt;/h2&gt;
&lt;p&gt;Almost every product organization claims to be customer-centric. The language is everywhere: customer obsession, voice of the customer, putting the customer first. It appears in mission statements, company values, and product strategy decks. It is invoked in roadmap meetings as a rhetorical trump card — &amp;ldquo;but what do the customers actually want?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;And yet the majority of product decisions in B2B companies are not made based on systematic, quantified customer evidence. They are made based on the opinions of internal advocates, the loudest customer complaint from the most recent sales call, the competitive feature that the market analyst flagged in a report, or the engineering team&amp;rsquo;s judgment about what is technically interesting. The customer is present in the language but absent from the evidence.&lt;/p&gt;</description></item></channel></rss>