<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agency Operations on Jon Munson</title>
    <link>https://www.jonmunson.co.uk/tags/agency-operations/</link>
    <description>Recent content in Agency Operations on Jon Munson</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.jonmunson.co.uk/tags/agency-operations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When it all kicks off: how to recover a project that&#39;s going sideways</title>
      <link>https://www.jonmunson.co.uk/posts/when-it-all-kicks-off-how-to-recover-a-project-going-sideways/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.jonmunson.co.uk/posts/when-it-all-kicks-off-how-to-recover-a-project-going-sideways/</guid>
      <description>&lt;p&gt;The project is on fire. A client is on the phone. Your shoulders are somewhere around your ears and you&amp;rsquo;re already drafting the apology email in your head.&lt;/p&gt;&#xA;&lt;p&gt;Stop. Put the email down.&lt;/p&gt;&#xA;&lt;p&gt;This isn&amp;rsquo;t specific to websites (my background is in web development teams) — though I say the same thing every time:&#xA;&lt;em&gt;it&amp;rsquo;s just a website, no-one is going to die.&lt;/em&gt;&lt;br&gt;&#xA;It works equally whether the thing that&amp;rsquo;s broken is a digital product, an AI rollout, or a process that&amp;rsquo;s just gone spectacularly wrong. When projects go sideways, most people&amp;rsquo;s instinct is to react. What actually helps is to reset.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
