<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Strategy &amp; Planning on RoadmapOne</title>
    <link>https://roadmap.one/categories/strategy--planning/</link>
    <description>Recent content in Strategy &amp; Planning on RoadmapOne</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://roadmap.one/categories/strategy--planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Strategy for Product Leaders: Eight Frameworks for the AI Era</title>
      <link>https://roadmap.one/blog/posts/blog46-strategy-for-product-leaders/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-strategy-for-product-leaders/</guid>
      <description>The eight strategy frameworks every product leader should know in 2026—Playing to Win, 7 Powers, Good Strategy Bad Strategy, Wardley Maps, Blue Ocean, Porter&amp;rsquo;s Five Forces, Porter&amp;rsquo;s Generic Strategies, and SWOT. Each is a thinking scaffold that forces a specific conversation. Together they are the toolkit for strategy that survives AI-era disruption and actually connects to the roadmap.</description>
    </item>
    <item>
      <title>Product Portfolio Roadmaps: Why Your Roadmap Is a Portfolio Allocation Decision, Not a Feature List</title>
      <link>https://roadmap.one/blog/posts/blog47-product-portfolio-roadmaps/</link>
      <pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog47-product-portfolio-roadmaps/</guid>
      <description>Very few companies have one product. Most are portfolios — multiple products at different lifecycle stages, each needing a different operating model, a different team shape, and a different share of the roadmap. The roadmap IS the portfolio allocation decision. Here&amp;rsquo;s how to see your portfolio clearly, diagnose the common failure modes (including the &amp;lsquo;CEO-interest-led&amp;rsquo; anti-pattern), and allocate capacity per product using the frameworks that actually work.</description>
    </item>
    <item>
      <title>7 Powers: Hamilton Helmer&#39;s Durable Moats and the AI Reframe</title>
      <link>https://roadmap.one/blog/posts/blog46-2-seven-powers/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-2-seven-powers/</guid>
      <description>Hamilton Helmer&amp;rsquo;s 7 Powers is the rigorous definition of what actually makes a moat durable. In 2026, AI rewrites which Powers strengthen and which erode — and product leaders need a sharper view of which Power each squad is building.</description>
    </item>
    <item>
      <title>Blue Ocean Strategy: Value Innovation Reframed for the AI Era</title>
      <link>https://roadmap.one/blog/posts/blog46-5-blue-ocean-strategy/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-5-blue-ocean-strategy/</guid>
      <description>Blue Ocean Strategy&amp;rsquo;s value innovation canvas taught a generation of strategists to find uncontested market space through feature differentiation. In 2026, features are cloned in weeks and red oceans get redder faster. The surviving blue oceans are about channel, segment, and workflow — not features.</description>
    </item>
    <item>
      <title>Good Strategy Bad Strategy: Rumelt&#39;s Kernel as a Fluff Detector</title>
      <link>https://roadmap.one/blog/posts/blog46-3-good-strategy-bad-strategy/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-3-good-strategy-bad-strategy/</guid>
      <description>Richard Rumelt&amp;rsquo;s Good Strategy Bad Strategy offers a three-part kernel—diagnosis, guiding policy, coherent action—and a practical test for separating strategy from fluff. Apply it to your product roadmap before writing the business case.</description>
    </item>
    <item>
      <title>Playing to Win: The Strategy Cascade as a Forcing Function</title>
      <link>https://roadmap.one/blog/posts/blog46-1-playing-to-win/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-1-playing-to-win/</guid>
      <description>Roger Martin&amp;rsquo;s Playing to Win is a thinking scaffold, not a template. Use the five-question strategy cascade to force honest strategic answers—and to structure the business case no product should go on the roadmap without.</description>
    </item>
    <item>
      <title>Porter&#39;s Five Forces: What the AI Era Has Rewritten</title>
      <link>https://roadmap.one/blog/posts/blog46-6-porters-five-forces/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-6-porters-five-forces/</guid>
      <description>Porter&amp;rsquo;s Five Forces remains the right scaffold for diagnosing industry structure, but three of the five forces have structurally changed in the AI era. Threat of new entrants is effectively infinite, substitutes appear faster, and rivalry intensifies on one side. Two forces still work fine.</description>
    </item>
    <item>
      <title>Porter&#39;s Generic Strategies: Why Focus Is the Only Survivor in the AI Era</title>
      <link>https://roadmap.one/blog/posts/blog46-7-porters-generic-strategies/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-7-porters-generic-strategies/</guid>
      <description>Porter gave us three generic strategies: cost leadership, differentiation, focus. In 2026, AI has killed cost leadership as a durable moat in software, feature-based differentiation is cloned in weeks, and focus (segment specialisation combined with channel and brand) is the only surviving strategy. This changes everything about capacity allocation.</description>
    </item>
    <item>
      <title>SWOT Analysis: Why a SWOT Is Not a Strategy (and How to Use It Anyway)</title>
      <link>https://roadmap.one/blog/posts/blog46-8-swot-analysis/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-8-swot-analysis/</guid>
      <description>SWOT analysis has been the default situational-assessment tool for forty years, and in 1997 academics called for its recall. Twenty-nine years on, most organisations still produce the 40-factor, un-prioritised, never-actioned SWOTs the critics warned about. A SWOT isn&amp;rsquo;t a strategy. Here&amp;rsquo;s how to use it anyway.</description>
    </item>
    <item>
      <title>Wardley Maps: Situational Awareness for Product Leaders in the AI Era</title>
      <link>https://roadmap.one/blog/posts/blog46-4-wardley-maps/</link>
      <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog46-4-wardley-maps/</guid>
      <description>Wardley Maps are the map strategy has been missing. Plot your value chain against the evolution axis—genesis, custom, product, commodity—and you see which components your squads should pioneer, settle, or industrialise. In 2026, AI accelerates every component&amp;rsquo;s march toward commodity, and the map has to be redrawn more often.</description>
    </item>
    <item>
      <title>Business Case for a New Product: The 3-Page PID Template That Forces ExCo Alignment</title>
      <link>https://roadmap.one/blog/posts/blog45-business-case-pid/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog45-business-case-pid/</guid>
      <description>A business case for a new product is not a forecast — it&amp;rsquo;s the alignment artefact that forces every ExCo member to commit, in writing, to their functional contribution to the product&amp;rsquo;s success. This article covers the tight 3-page Project Initiation Document (PID) template that took Trayport to 62% CAGR, why PE-owned companies are better at this than anyone else, and why nothing should be allowed onto the roadmap until the PID is signed.</description>
    </item>
    <item>
      <title>OKR Examples for Product Teams: 30&#43; Objectives and Key Results That Actually Work</title>
      <link>https://roadmap.one/blog/posts/blog41-okr-examples/</link>
      <pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog41-okr-examples/</guid>
      <description>30+ OKR examples for product teams—framed as business problems, not features. Includes bad-to-good rewrites, real-world examples from Google and Intel, examples tagged by Run/Grow/Transform, and how each Objective connects to squad allocation on your roadmap.</description>
    </item>
    <item>
      <title>OKRs vs KPIs Explained: The Complete Guide for Product Teams</title>
      <link>https://roadmap.one/blog/posts/blog40-okr-vs-kpi/</link>
      <pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog40-okr-vs-kpi/</guid>
      <description>KPIs are what you watch. OKRs are what you chase. KPIs tell finance what happened last quarter. OKRs tell product teams what to change next quarter. Here&amp;rsquo;s the complete guide to the difference—with real examples, common mistakes, and how the two work together on your roadmap.</description>
    </item>
    <item>
      <title>The Product Operating Model: A Practical Guide From Inside Cagan&#39;s Trainline Case Study</title>
      <link>https://roadmap.one/blog/posts/blog39-product-operating-model/</link>
      <pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog39-product-operating-model/</guid>
      <description>The product operating model is how the best tech-powered companies work. I know because I was there — as CTO at Trainline, featured in Marty Cagan&amp;rsquo;s Transformed. Here&amp;rsquo;s what the product model actually looks like in practice, how we aligned 650 people around outcomes, and why I built RoadmapOne to make it repeatable.</description>
    </item>
    <item>
      <title>The Culture of Adequacy: Your Customers Don&#39;t Want Minimum — They Want Magnificent</title>
      <link>https://roadmap.one/blog/posts/blog36-culture-of-adequacy/</link>
      <pubDate>Mon, 16 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog36-culture-of-adequacy/</guid>
      <description>Many teams have been conditioned into adequacy: shipping the bare minimum of everything and the full potential of nothing. Here&amp;rsquo;s the spectrum from Minimum Product to Maximally Awesome Product, and why your crown jewels deserve obsessive, beautiful, category-killing investment.</description>
    </item>
    <item>
      <title>Crown Jewels: Why Your Most Important Feature Is Slowly Dying</title>
      <link>https://roadmap.one/blog/posts/blog35-crown-jewels/</link>
      <pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog35-crown-jewels/</guid>
      <description>Every product has two or three capabilities that disproportionately matter to customers. Over time, product teams lose sight of these crown jewels—until a competitor does them slightly better and the loss ratio spikes. Here&amp;rsquo;s how to identify, protect, and relentlessly improve the features that define your product.</description>
    </item>
    <item>
      <title>Ship It and Move On: The Recipe for a Mediocre Product</title>
      <link>https://roadmap.one/blog/posts/blog34-ship-it-and-move-on/</link>
      <pubDate>Wed, 04 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://roadmap.one/blog/posts/blog34-ship-it-and-move-on/</guid>
      <description>Your roadmap shows Feature X shipping in March, then the team immediately moves on. That&amp;rsquo;s the recipe for a mediocre product—an agglomeration of half-baked MVPs where nothing makes customers go &amp;lsquo;wow&amp;rsquo;. Here&amp;rsquo;s why great products need a second act.</description>
    </item>
  </channel>
</rss>
