<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sequencing on Andrew Hunter — Systems Architect &amp; Builder</title>
    <link>https://andrewphunter.com/tags/sequencing/</link>
    <description>Recent content in Sequencing on Andrew Hunter — Systems Architect &amp; Builder</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://andrewphunter.com/tags/sequencing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Transformation Under Scale — Part V: Derive the Roadmap</title>
      <link>https://andrewphunter.com/writing/derive-the-roadmap/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://andrewphunter.com/writing/derive-the-roadmap/</guid>
      <description>&lt;p&gt;Part IV drew the boundaries and gave each one a way to move: find the single writer of each fact, then move the pen from the legacy system to the target one without stopping the business. Any one boundary can move that way. A real estate has dozens, and the next question is the one every transformation is judged on: in what order, and by when.&lt;/p&gt;&#xA;&lt;p&gt;The usual answer is a roadmap drawn on a whiteboard, ordered by a demo date, by the loudest team, or by whatever the vendor can ship first. It looks like a plan and behaves like a negotiation, reopened at every steering meeting. It does not need to be drawn at all. By the time anyone asks for a roadmap, the first four parts of this series have already produced the thing it is made of, and most of the order is already decided.&lt;/p&gt;&#xA;&lt;p&gt;A transformation roadmap is derived, not drawn. It is the operating model laid out in time: the dependencies between capabilities are facts about how the business works, and what is left once they are honored is a business decision about which value comes first.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
