<?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>RCA on Chido Dike</title>
    <link>https://blog.chido.me/tags/rca/</link>
    <description>Recent content in RCA on Chido Dike</description>
    <image>
      <title>Chido Dike</title>
      <url>https://blog.chido.me/og-default.png</url>
      <link>https://blog.chido.me/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 09:20:00 +0100</lastBuildDate>
    <atom:link href="https://blog.chido.me/tags/rca/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RCA That Actually Cuts Recurrence</title>
      <link>https://blog.chido.me/posts/rca-recurrence/</link>
      <pubDate>Mon, 05 Oct 2026 09:20:00 +0100</pubDate>
      <guid>https://blog.chido.me/posts/rca-recurrence/</guid>
      <description>&lt;h2 id=&#34;the-ticket-that-came-back-with-a-new-number&#34;&gt;The ticket that came back with a new number&lt;/h2&gt;
&lt;p&gt;It&amp;rsquo;s Tuesday, 11:40. The major-incident bridge closed yesterday with a clean timeline, a polite &amp;ldquo;thanks everyone&amp;rdquo; and a promise that root cause would follow. Today the same symptom is back, under a different ticket number but in the same category, reported by the same annoyed colleague who has already told the story once.&lt;/p&gt;
&lt;p&gt;Your queue looks busy in the right way. Your problem record looks complete in the wrong way. There&amp;rsquo;s a five-whys slide, a parking-lot action reading &amp;ldquo;engage vendor&amp;rdquo;, and nobody has an owner and a date for when this failure stops happening on Monday mornings.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
