<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title><![CDATA[GridWave FlowShift]]></title>
  <link>https://gridwaveflowshift.com/</link>
  <description><![CDATA[GridWave FlowShift is a small Edinburgh consultancy helping teams fix their workflows, plan better, and document what actually matters. Honest, practical, no fluff.]]></description>
  <language>en</language>
  <atom:link href="https://gridwaveflowshift.com/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title><![CDATA[How to run an operations audit on your own team]]></title>
    <link>https://gridwaveflowshift.com/notes/how-to-run-an-operations-audit.html</link>
    <guid>https://gridwaveflowshift.com/notes/how-to-run-an-operations-audit.html</guid>
    <description><![CDATA[Most organisations know something is not working. The harder part is knowing which something, and in what order to fix it. An operations audit is a structured way to find out. It does not have to be expensive or complicated, but it does have to be honest.]]></description>
    <pubDate>2026-05-20</pubDate>
  </item>
  <item>
    <title><![CDATA[Why process documentation fails and what to do instead]]></title>
    <link>https://gridwaveflowshift.com/notes/why-process-documentation-fails.html</link>
    <guid>https://gridwaveflowshift.com/notes/why-process-documentation-fails.html</guid>
    <description><![CDATA[We have seen a lot of process documentation. Some of it is excellent. Most of it is a 40-page PDF that lives in a shared drive folder called 'Operations' and has not been opened since the month it was created. The problem is almost never the content. It is the format.]]></description>
    <pubDate>2026-04-10</pubDate>
  </item>
  <item>
    <title><![CDATA[Capacity planning for small teams without a spreadsheet nightmare]]></title>
    <link>https://gridwaveflowshift.com/notes/capacity-planning-for-small-teams.html</link>
    <guid>https://gridwaveflowshift.com/notes/capacity-planning-for-small-teams.html</guid>
    <description><![CDATA[Most small teams do not do capacity planning. They do optimism planning. They look at the work coming in, assume everyone will be at full productivity, forget about meetings and admin and the unexpected thing that always happens, and say yes. Then they wonder why everything is late.]]></description>
    <pubDate>2026-03-15</pubDate>
  </item>
  <item>
    <title><![CDATA[Why change management plans fail in the first six weeks]]></title>
    <link>https://gridwaveflowshift.com/notes/change-management-why-plans-fail.html</link>
    <guid>https://gridwaveflowshift.com/notes/change-management-why-plans-fail.html</guid>
    <description><![CDATA[Change management has a reputation for being complicated. It is not, really. The complicated part is not the plan. It is the six weeks after the plan is announced, when the initial energy has worn off and the real friction starts.]]></description>
    <pubDate>2026-02-05</pubDate>
  </item>
  <item>
    <title><![CDATA[How to run quarterly planning pre-work that actually gets done]]></title>
    <link>https://gridwaveflowshift.com/notes/quarterly-planning-pre-work-guide.html</link>
    <guid>https://gridwaveflowshift.com/notes/quarterly-planning-pre-work-guide.html</guid>
    <description><![CDATA[The quarterly planning session is not where the thinking happens. The thinking happens in the ten days before, when people have time to reflect without an agenda in front of them. The session is where you compare notes. If nobody has done the thinking, the session is just a meeting.]]></description>
    <pubDate>2026-01-22</pubDate>
  </item>
</channel>
</rss>
