<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operational Excellence on Christa Burger</title><link>https://christaburger.com/tags/operational-excellence/</link><description>Recent content in Operational Excellence on Christa Burger</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://christaburger.com/tags/operational-excellence/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Productivity Is Too Vague. Show the Burden Removed.</title><link>https://christaburger.com/blog/ai-productivity-is-too-vague/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/ai-productivity-is-too-vague/</guid><description>&lt;p&gt;&amp;ldquo;AI improves productivity&amp;rdquo; is true and also not very useful.&lt;/p&gt;
&lt;p&gt;Productivity where?&lt;/p&gt;
&lt;p&gt;Which burden got lighter?&lt;/p&gt;
&lt;p&gt;What changed?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Did we reduce rework?&lt;/li&gt;
&lt;li&gt;Did we prevent something from being forgotten?&lt;/li&gt;
&lt;li&gt;Did we make decisions cleaner?&lt;/li&gt;
&lt;li&gt;Did we improve evidence?&lt;/li&gt;
&lt;li&gt;Did we reduce manual reconstruction?&lt;/li&gt;
&lt;li&gt;Did we make the next step obvious?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That is what I care about.&lt;/p&gt;
&lt;p&gt;Not vague productivity.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Specific relief with receipts.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is how AI use cases should be explained.&lt;/p&gt;</description></item><item><title>Unnamed Work Becomes Weather</title><link>https://christaburger.com/blog/unnamed-work-becomes-weather/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/unnamed-work-becomes-weather/</guid><description>&lt;p&gt;Unnamed work becomes weather.&lt;/p&gt;
&lt;p&gt;It just happens.&lt;/p&gt;
&lt;p&gt;People feel it. People complain about it. People plan around it. Nobody owns it.&lt;/p&gt;
&lt;p&gt;This is true in teams, households, operations, governance, and AI workflows.&lt;/p&gt;
&lt;p&gt;The first act of control is often &lt;strong&gt;naming&lt;/strong&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Name the recurring burden&lt;/li&gt;
&lt;li&gt;Name the decision point&lt;/li&gt;
&lt;li&gt;Name the review&lt;/li&gt;
&lt;li&gt;Name the handoff&lt;/li&gt;
&lt;li&gt;Name the risk&lt;/li&gt;
&lt;li&gt;Name the evidence trail&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Once something has a name, it can have an owner.&lt;/p&gt;</description></item><item><title>Accountability Should Not Require Archaeology</title><link>https://christaburger.com/blog/accountability-should-not-require-archaeology/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/accountability-should-not-require-archaeology/</guid><description>&lt;p&gt;If accountability requires archaeology, the system is under-designed.&lt;/p&gt;
&lt;p&gt;People should not need to dig through inboxes, Slack threads, meeting notes, and the memory of whoever was least distracted at the time.&lt;/p&gt;
&lt;p&gt;That is not a process.&lt;/p&gt;
&lt;p&gt;That is a scavenger hunt with legal exposure.&lt;/p&gt;
&lt;p&gt;AI should make this better.&lt;/p&gt;
&lt;p&gt;Every meaningful AI-assisted workflow should be able to answer:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What did it do?&lt;/li&gt;
&lt;li&gt;What inputs did it use?&lt;/li&gt;
&lt;li&gt;What changed?&lt;/li&gt;
&lt;li&gt;What did it recommend?&lt;/li&gt;
&lt;li&gt;What did a human approve?&lt;/li&gt;
&lt;li&gt;Where is the evidence?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This is not just a security or compliance concern.&lt;/p&gt;</description></item><item><title>"I Think We Talked About This" Is Not a Control</title><link>https://christaburger.com/blog/i-think-we-talked-about-this-is-not-a-control/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/i-think-we-talked-about-this-is-not-a-control/</guid><description>&lt;p&gt;The worst time to document a decision is after something goes wrong.&lt;/p&gt;
&lt;p&gt;Everyone is calm. Everyone remembers clearly. No one is searching email for &amp;ldquo;final_final_ACTUAL_USE_THIS_ONE_v7.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Obviously.&lt;/p&gt;
&lt;p&gt;AI can help us stop doing this.&lt;/p&gt;
&lt;p&gt;It can capture decisions as they happen:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What was known?&lt;/li&gt;
&lt;li&gt;What was decided?&lt;/li&gt;
&lt;li&gt;Who decided it?&lt;/li&gt;
&lt;li&gt;What changed later?&lt;/li&gt;
&lt;li&gt;What evidence existed at the time?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That is incredibly valuable.&lt;/p&gt;
&lt;p&gt;But only if we design for it.&lt;/p&gt;
&lt;p&gt;Otherwise AI just helps us create more outputs with less traceability.&lt;/p&gt;</description></item><item><title>Heroics Are Usually a Design Problem</title><link>https://christaburger.com/blog/heroics-are-a-design-problem/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://christaburger.com/blog/heroics-are-a-design-problem/</guid><description>&lt;p&gt;I used to be more impressed by heroic effort.&lt;/p&gt;
&lt;p&gt;The late-night push. The last-minute save. The frantic deck rescue. The spreadsheet that emerges from the ashes wearing a tiny cape.&lt;/p&gt;
&lt;p&gt;Now I mostly see heroics as a signal: a broken system relying on the goodwill of one person — or their insecurities — to keep functioning.&lt;/p&gt;
&lt;p&gt;Sometimes heroics are necessary. Workloads can fluctuate wildly.&lt;/p&gt;
&lt;p&gt;But that is also a lazy acceptance.&lt;/p&gt;</description></item></channel></rss>