<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prioritization on MYLES — Strategy &amp; Innovation Consulting</title><link>https://myles-innovation.com/tags/prioritization/</link><description>Recent content in Prioritization on MYLES — Strategy &amp; Innovation Consulting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 04 Mar 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://myles-innovation.com/tags/prioritization/index.xml" rel="self" type="application/rss+xml"/><item><title>From Opportunity Scores to Product Roadmap Priorities</title><link>https://myles-innovation.com/blog/opportunity-scores-product-roadmap/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0100</pubDate><guid>https://myles-innovation.com/blog/opportunity-scores-product-roadmap/</guid><description>&lt;h2 id="the-prioritization-problem-that-data-was-supposed-to-solve"&gt;The Prioritization Problem That Data Was Supposed to Solve&lt;/h2&gt;
&lt;p&gt;Every product manager I have worked with has experienced the same meeting. The roadmap review. Everyone has opinions. The VP of Sales wants the CRM integration because a large customer mentioned it. The VP of Engineering wants the architecture refactor because the technical debt is becoming untenable. The CEO wants the feature she saw at a competitor&amp;rsquo;s booth last month. The product manager has twelve user stories all tagged &amp;ldquo;high priority.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>