<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Field Notes — Deployed Skills</title>
    <link>https://deployedskills.com/field-notes</link>
    <description>Short reads on how teams actually ship AI.</description>
    <language>en-US</language>
    <lastBuildDate>Mon, 10 Aug 2026 21:14:05 GMT</lastBuildDate>
    <atom:link href="https://deployedskills.com/rss.xml" rel="self" type="application/rss+xml"/>
    
    <item>
      <title>Recurring Exception Decision Debt</title>
      <link>https://deployedskills.com/field-notes/recurring-exception-decision-debt</link>
      <guid>https://deployedskills.com/field-notes/recurring-exception-decision-debt</guid>
      <pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate>
      <description>The same exception keeps landing on the same busy person and gets read as a workload problem. Read across a month, the pattern says something different: a recurring exception is a decision never made, and every instance pays interest on the deferral.</description>
    </item>
    <item>
      <title>Knowledge Island Concentration Risk</title>
      <link>https://deployedskills.com/field-notes/knowledge-island-concentration-risk</link>
      <guid>https://deployedskills.com/field-notes/knowledge-island-concentration-risk</guid>
      <pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate>
      <description>Most founders can name one person whose departure would stall a specific capability inside of a week. Few have written those names down and counted how many there are. Concentration risk is a standing condition the owner is already carrying, present every day before the departure, not only on the day of.</description>
    </item>
    <item>
      <title>What Not to Fix</title>
      <link>https://deployedskills.com/field-notes/what-not-to-fix</link>
      <guid>https://deployedskills.com/field-notes/what-not-to-fix</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <description>Some operational drag is cheaper to keep than to fix, because every fix carries three costs: the build, the risk, and the hidden job the workaround was doing. The discipline is to treat keeping something alone as a real decision that expires when the business underneath it changes, not as a permanent exemption from fixing.</description>
    </item>
    <item>
      <title>The Headcount Reflex</title>
      <link>https://deployedskills.com/field-notes/the-headcount-reflex</link>
      <guid>https://deployedskills.com/field-notes/the-headcount-reflex</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <description>A team says it&apos;s underwater and three months later there&apos;s a new person on the team. The work is still late. The only thing that changed is headcount, and headcount was never the thing that was broken.</description>
    </item>
    <item>
      <title>Read the Duct Tape</title>
      <link>https://deployedskills.com/field-notes/read-the-duct-tape</link>
      <guid>https://deployedskills.com/field-notes/read-the-duct-tape</guid>
      <pubDate>Fri, 10 Jul 2026 20:41:00 GMT</pubDate>
      <description>The unofficial tracker, taped-up checklist, or side spreadsheet is often evidence of a system gap. Read the workaround before removing it.</description>
    </item>
    <item>
      <title>Where Automation Should Stop</title>
      <link>https://deployedskills.com/field-notes/where-automation-should-stop</link>
      <guid>https://deployedskills.com/field-notes/where-automation-should-stop</guid>
      <pubDate>Mon, 06 Jul 2026 02:06:00 GMT</pubDate>
      <description>There&apos;s a natural point where every automation effort arrives at the same question. It works. It&apos;s fast. It hasn&apos;t made a mistake yet. Should it also be the one that decides?</description>
    </item>
    <item>
      <title>The Middle Role No One Can Hire</title>
      <link>https://deployedskills.com/field-notes/the-middle-role-no-one-can-hire</link>
      <guid>https://deployedskills.com/field-notes/the-middle-role-no-one-can-hire</guid>
      <pubDate>Wed, 01 Jul 2026 10:45:00 GMT</pubDate>
      <description>Small companies often hide middle-management work inside scattered, fractional tasks that fall onto founders or nearby employees. Automation can help surface and divide that work, but only after the company defines how the work actually moves.</description>
    </item>
    <item>
      <title>Where Your Data Actually Lives</title>
      <link>https://deployedskills.com/field-notes/where-your-data-actually-lives</link>
      <guid>https://deployedskills.com/field-notes/where-your-data-actually-lives</guid>
      <pubDate>Thu, 25 Jun 2026 16:02:00 GMT</pubDate>
      <description>Two sources in the same company give different numbers for the same thing because no canonical source has been named. The fix is a single written decision naming which one counts, and it takes about an afternoon.</description>
    </item>
  </channel>
</rss>