<?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>Plain Ops Articles</title>
    <link>https://www.plainopsconsulting.com/operator-insights/</link>
    <description>Articles about operating decisions, work flow, reliability and what changes results.</description>
    <language>en-US</language>
    <atom:link href="https://www.plainopsconsulting.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>What Never Gets Proposed</title>
      <link>https://www.plainopsconsulting.com/operator-insights/what-never-gets-proposed/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/what-never-gets-proposed/</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>Some IT improvements never make it into the backlog because people expect them to be rejected. The right people never get to consider them.</description>
    </item>
    <item>
      <title>Buy the Tool After You Know How the Work Should Run</title>
      <link>https://www.plainopsconsulting.com/operator-insights/buy-the-tool-after-the-workflow/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/buy-the-tool-after-the-workflow/</guid>
      <pubDate>Mon, 26 Oct 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>Before choosing a work-management platform, establish the decisions about intake, priority, ownership, handoff and acceptance that the software must represent.</description>
    </item>
    <item>
      <title>Fast, Confident, and Unreliable Is Not Just an AI Problem</title>
      <link>https://www.plainopsconsulting.com/operator-insights/fast-confident-and-unreliable/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/fast-confident-and-unreliable/</guid>
      <pubDate>Wed, 21 Oct 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>A website reviewer reported defects that did not exist. Why confident contributors need source boundaries, evidence and independent checks.</description>
    </item>
    <item>
      <title>IT Infrastructure Roadmap: Why an $8.5M Buy List Had to Be Rebuilt</title>
      <link>https://www.plainopsconsulting.com/operator-insights/it-infrastructure-roadmap-before-buy-list/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/it-infrastructure-roadmap-before-buy-list/</guid>
      <pubDate>Sat, 12 Sep 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>An $8.5M infrastructure proposal had technology and pricing but no defensible requirements or TCO model. Here is what changed before leadership could approve the investment.</description>
    </item>
    <item>
      <title>The postmortem has to survive the room</title>
      <link>https://www.plainopsconsulting.com/operator-insights/the-postmortem-has-to-survive-the-room/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/the-postmortem-has-to-survive-the-room/</guid>
      <pubDate>Mon, 24 Aug 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>A mature postmortem preserves the failure, moves accountability upward, and keeps the incident timeline from becoming a list of people to blame.</description>
    </item>
    <item>
      <title>The Assembly Lines: You can’t scale what you can’t name.</title>
      <link>https://www.plainopsconsulting.com/operator-insights/the-assembly-lines/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/the-assembly-lines/</guid>
      <pubDate>Tue, 10 Mar 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>IT work gets easier to manage when the dominant work flows are named and each one has a clear entry, owner, states, handoffs, and finish condition.</description>
    </item>
    <item>
      <title>The Intake Gate: No context, no start</title>
      <link>https://www.plainopsconsulting.com/operator-insights/the-intake-gate/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/the-intake-gate/</guid>
      <pubDate>Mon, 02 Mar 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>Work should not begin until there is enough context to know who needs it, what finished means, roughly what it will consume, and what changes if it starts now.</description>
    </item>
    <item>
      <title>The WIP Trap: If everything is started, nothing finishes</title>
      <link>https://www.plainopsconsulting.com/operator-insights/the-wip-trap/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/the-wip-trap/</guid>
      <pubDate>Mon, 23 Feb 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>Too much active work makes elapsed time unstable, because work spends more time waiting between touches. Activity can rise while completion and predictability fall.</description>
    </item>
    <item>
      <title>The Urgent Trade: If urgent enters, something leaves</title>
      <link>https://www.plainopsconsulting.com/operator-insights/urgent-trade/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/urgent-trade/</guid>
      <pubDate>Mon, 16 Feb 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>Urgent work is legitimate and it is not free. When urgent work starts, the displaced work and its consequence have to be named at the same time.</description>
    </item>
    <item>
      <title>The One Queue Rule: If there are two backlogs, the org runs on escalation</title>
      <link>https://www.plainopsconsulting.com/operator-insights/the-one-queue-rule/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/the-one-queue-rule/</guid>
      <pubDate>Mon, 09 Feb 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>One queue means one authoritative ordering of work. It does not mean one tool, one list, or one work type. Without a shared ordering, escalation becomes the ordering.</description>
    </item>
    <item>
      <title>The Side Door Problem: Why IT Spend and Delivery Keep Surprising You</title>
      <link>https://www.plainopsconsulting.com/operator-insights/side-door-problem-it-intake-ledger/</link>
      <guid>https://www.plainopsconsulting.com/operator-insights/side-door-problem-it-intake-ledger/</guid>
      <pubDate>Thu, 05 Feb 2026 12:00:00 +0000</pubDate>
      <dc:creator>Nick Vaernhoej</dc:creator>
      <description>Work that enters outside the visible intake path still consumes capacity. When it isn't recorded, owned, and ordered with everything else, cost and delivery surprises are predictable.</description>
    </item>
  </channel>
</rss>