<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ovenbird blog</title>
    <link>https://ovenbird.tech/blog/</link>
    <atom:link href="https://ovenbird.tech/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Processes, and why they get missed.</description>
    <language>en</language>
    <item><title>Where does the queue pile up? Finding the bottleneck before customers do</title><link>https://ovenbird.tech/blog/finding-the-bottleneck-before-customers-do</link><guid>https://ovenbird.tech/blog/finding-the-bottleneck-before-customers-do</guid><pubDate>2026-10-09T09:00:00Z</pubDate><description>Every process has one stage that sets its pace. A short guide to spotting it with Little&#x27;s law and utilisation, why adding people elsewhere doesn&#x27;t help, and how to simulate a change before making it.</description></item>
    <item><title>Four famous process failures, and the one thing they share</title><link>https://ovenbird.tech/blog/four-process-failures-and-what-they-share</link><guid>https://ovenbird.tech/blog/four-process-failures-and-what-they-share</guid><pubDate>2026-10-09T09:00:00Z</pubDate><description>Knight Capital&#x27;s $440 million, an AWS outage from a typo, the crash that invented the checklist, and the checklist that cut surgical deaths. Different industries, the same lesson about documented procedures.</description></item>
    <item><title>Training people on a process once is almost the same as not training them</title><link>https://ovenbird.tech/blog/training-once-is-the-same-as-not-training</link><guid>https://ovenbird.tech/blog/training-once-is-the-same-as-not-training</guid><pubDate>2026-10-09T09:00:00Z</pubDate><description>The forgetting curve applies to runbooks too. Why a single onboarding session on a procedure doesn&#x27;t hold, what retrieval practice and spaced refreshers change, and how to tell who actually knows the process.</description></item>
    <item><title>Why documented processes get skipped (and it isn&#x27;t laziness)</title><link>https://ovenbird.tech/blog/why-documented-processes-get-skipped</link><guid>https://ovenbird.tech/blog/why-documented-processes-get-skipped</guid><pubDate>2026-10-09T09:00:00Z</pubDate><description>Teams write the process down and still miss the step. The reasons are structural: distance, timing, stale documents and invisible adherence. What each one looks like on a real ticket, and what fixes it.</description></item>
    <item><title>How a correction should flow back into the document</title><link>https://ovenbird.tech/blog/how-a-correction-should-flow-back-into-the-document</link><guid>https://ovenbird.tech/blog/how-a-correction-should-flow-back-into-the-document</guid><pubDate>2026-10-09T09:00:00Z</pubDate><description>&quot;That&#x27;s wrong, we do it differently now&quot; is the most valuable sentence in operations and the most often lost. A design for the loop from correction to precedent to suggested edit to retraining.</description></item>
  </channel>
</rss>
