<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Traverse on Tenu Tech Brief</title>
    <link>https://cluster-site.onrender.com/tags/traverse/</link>
    <description>Recent content in Traverse on Tenu Tech Brief</description>
    <generator>Hugo -- 0.146.0</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 24 Feb 2026 06:04:39 +0000</lastBuildDate>
    <atom:link href="https://cluster-site.onrender.com/tags/traverse/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Plan vs. planning: Why continuous planning must traverse time</title>
      <link>https://cluster-site.onrender.com/posts/plan-vs.-planning-why-continuous-planning-must-traverse-time/</link>
      <pubDate>Fri, 20 Feb 2026 12:00:00 +0000</pubDate>
      <guid>https://cluster-site.onrender.com/posts/plan-vs.-planning-why-continuous-planning-must-traverse-time/</guid>
      <description>• planning: Why continuous planning must traverse time Plans capture a moment in time. • Planning must move through time. • Most enterprises are not short on plans. • They have str</description>
    </item>
  </channel>
</rss>
