<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Incident-Commander on Keith Kee KW</title>
		<link>https://keithkeekw.github.io/tags/incident-commander/</link>
		<description>Recent content in Incident-Commander on Keith Kee KW</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 18 Jul 2026 00:00:00 +0800</lastBuildDate>
		
			<atom:link href="https://keithkeekw.github.io/tags/incident-commander/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Incident Manager&#39;s OS: OODA × RACI × Incident Commander</title>
				<link>https://keithkeekw.github.io/posts/2026-07-18-incident-manager-os/</link>
				<pubDate>Sat, 18 Jul 2026 00:00:00 +0800</pubDate>
				<guid>https://keithkeekw.github.io/posts/2026-07-18-incident-manager-os/</guid>
				<description>&lt;p&gt;Speed alone isn&amp;rsquo;t enough. A fast team without clear roles is just organized noise — tasks duplicating, decisions stalling, everyone looking at everyone else while the incident escalates.&lt;/p&gt;&#xA;&lt;p&gt;The OODA Loop sets the rhythm. You need two more layers to make it work: &lt;strong&gt;role clarity&lt;/strong&gt; and &lt;strong&gt;decision ownership&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Think of this as an operating system for your incident response. Every OS manages three things — process scheduling (tempo), resource allocation (roles), and system calls (decisions) — so applications don&amp;rsquo;t have to reinvent the wheel. The Incident Manager&amp;rsquo;s OS does the same for crisis response. It is the shared foundation that handles the three things that break in every major incident:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
