<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Doug Bell</title>
    <description>The latest articles on DEV Community by Doug Bell (@doug_bell_2aeb61135f20467).</description>
    <link>https://dev.to/doug_bell_2aeb61135f20467</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3893706%2Fe5ddfc35-3caf-4baa-b669-62e1c2795b81.png</url>
      <title>DEV Community: Doug Bell</title>
      <link>https://dev.to/doug_bell_2aeb61135f20467</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/doug_bell_2aeb61135f20467"/>
    <language>en</language>
    <item>
      <title>Incident Index</title>
      <dc:creator>Doug Bell</dc:creator>
      <pubDate>Thu, 23 Apr 2026 07:23:24 +0000</pubDate>
      <link>https://dev.to/doug_bell_2aeb61135f20467/incident-index-3dld</link>
      <guid>https://dev.to/doug_bell_2aeb61135f20467/incident-index-3dld</guid>
      <description>&lt;p&gt;Incident Index helps teams run structured root cause analyses and generate stakeholder-ready incident reports without the usual post-incident write. Instead of collecting scattered notes and turning them into a document later, it guides the RCA session itself, capturing the timeline, causal factors, and 5 Whys in real time so the output is created as the work happens.&lt;/p&gt;

&lt;p&gt;Originally built to solve the frustration of rewriting incident reports after every review, Incident Index replaces that step with a simple, session-first workflow. Teams stay aligned during the discussion and walk away with a clear RCA and a report that can be shared with leadership or customers immediately.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>startup</category>
      <category>analysis</category>
    </item>
  </channel>
</rss>
