<?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>Articles · Many Branches Consulting</title>
  <link>https://blog.manybranches.co/</link>
  <description>Plain-language writing on AI governance, technology strategy, and the work itself.</description>
  <language>en</language>
  <atom:link href="https://blog.manybranches.co/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>You can’t govern what you can’t see</title>
    <link>https://blog.manybranches.co/you-cant-govern-what-you-cant-see</link>
    <guid isPermaLink="true">https://blog.manybranches.co/you-cant-govern-what-you-cant-see</guid>
    <description>Nobody in your firm decided to adopt AI. Twelve people decided quietly, one tool at a time. The first governance move is an inventory, and it takes an afternoon.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Verbal norms don’t survive a dispute</title>
    <link>https://blog.manybranches.co/verbal-norms-dont-survive-a-dispute</link>
    <guid isPermaLink="true">https://blog.manybranches.co/verbal-norms-dont-survive-a-dispute</guid>
    <description>The two most popular AI policies are a blanket ban and a shrug. Neither is written down, and both fail the same way. What holds up is a rulebook tiered to the risk of the work.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Where the prompt goes</title>
    <link>https://blog.manybranches.co/where-the-prompt-goes</link>
    <guid isPermaLink="true">https://blog.manybranches.co/where-the-prompt-goes</guid>
    <description>Training, retention, and human review are three different risks that firms collapse into one fear. Pulling them apart is most of the literacy this subject requires.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>The AI clause you already signed</title>
    <link>https://blog.manybranches.co/the-ai-clause-you-already-signed</link>
    <guid isPermaLink="true">https://blog.manybranches.co/the-ai-clause-you-already-signed</guid>
    <description>Long before your firm wrote an AI policy, it signed a stack of contracts with opinions about AI. The audit is reading your own paper, and it takes an afternoon.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Your liability policy may already exclude AI</title>
    <link>https://blog.manybranches.co/your-liability-policy-may-already-exclude-ai</link>
    <guid isPermaLink="true">https://blog.manybranches.co/your-liability-policy-may-already-exclude-ai</guid>
    <description>Insurers have started writing generative AI out of standard liability policies, one renewal at a time. The safety net many firms assume is there may already be gone.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>The tool is never the one who is responsible</title>
    <link>https://blog.manybranches.co/the-tool-is-never-the-one-responsible</link>
    <guid isPermaLink="true">https://blog.manybranches.co/the-tool-is-never-the-one-responsible</guid>
    <description>Fabricated citations now draw sanctions, and the sanctions now draw discipline. Human oversight counts for something only when “reviewed” is defined, budgeted, and signed.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>“How do you use AI?” is now a normal client question</title>
    <link>https://blog.manybranches.co/how-do-you-use-ai-is-now-a-normal-client-question</link>
    <guid isPermaLink="true">https://blog.manybranches.co/how-do-you-use-ai-is-now-a-normal-client-question</guid>
    <description>The firms that dread the question are the ones without an answer. A prepared, consistent disclosure turns AI from something you hope nobody raises into evidence that the firm runs on decisions.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>A roadmap is not a wish list of tools</title>
    <link>https://blog.manybranches.co/a-roadmap-is-not-a-wish-list-of-tools</link>
    <guid isPermaLink="true">https://blog.manybranches.co/a-roadmap-is-not-a-wish-list-of-tools</guid>
    <description>Most technology roadmaps are shopping lists with dates on them. A real one is a set of decisions, tied to business goals, sequenced so that each phase earns the next.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>A CTO’s judgment, a fraction of the cost</title>
    <link>https://blog.manybranches.co/a-ctos-judgment-a-fraction-of-the-cost</link>
    <guid isPermaLink="true">https://blog.manybranches.co/a-ctos-judgment-a-fraction-of-the-cost</guid>
    <description>The decisions are already arriving weekly, whether or not anybody in the building is equipped to make them. Fractional leadership rents the judgment without the executive payroll.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Supervised transformation, on subscription</title>
    <link>https://blog.manybranches.co/supervised-transformation-on-subscription</link>
    <guid isPermaLink="true">https://blog.manybranches.co/supervised-transformation-on-subscription</guid>
    <description>After the roadmap is written comes the unglamorous part, which is running it. Tooling, vendors, security, and reporting as a flat monthly engagement instead of a permanent scramble.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Built so you can stop</title>
    <link>https://blog.manybranches.co/built-so-you-can-stop</link>
    <guid isPermaLink="true">https://blog.manybranches.co/built-so-you-can-stop</guid>
    <description>Read a consultancy’s exits before its entrances. Our engagements are staged with real decision gates, deliverables you keep, and a credit mechanic that puts our money where the plan is.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Open tools, closed systems</title>
    <link>https://blog.manybranches.co/open-tools-closed-systems</link>
    <guid isPermaLink="true">https://blog.manybranches.co/open-tools-closed-systems</guid>
    <description>The AI your staff chat with and the AI that should touch confidential work are different machines. Bounded inputs, schema-checked outputs, and a human gate nobody can skip.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Opens lie, clicks lie less, visits tell the truth</title>
    <link>https://blog.manybranches.co/opens-lie-clicks-lie-less-visits-tell-the-truth</link>
    <guid isPermaLink="true">https://blog.manybranches.co/opens-lie-clicks-lie-less-visits-tell-the-truth</guid>
    <description>We built our own outreach tracking rather than buy a marketing suite. The honest reading of engagement data is the most useful thing the build taught us.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Nothing leaves the tools it lives in</title>
    <link>https://blog.manybranches.co/nothing-leaves-the-tools-it-lives-in</link>
    <guid isPermaLink="true">https://blog.manybranches.co/nothing-leaves-the-tools-it-lives-in</guid>
    <description>How we gave AI working memory over a firm’s knowledge without indexing a single document: live federated search, read-only scopes, and answers that cite their sources.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>How these articles were made</title>
    <link>https://blog.manybranches.co/how-these-articles-were-made</link>
    <guid isPermaLink="true">https://blog.manybranches.co/how-these-articles-were-made</guid>
    <description>A library arguing for AI disclosure owes you its own. Here is the machine that helped draft these pages, the linter that polices its voice, and the humans who sign.</description>
    <dc:creator>Adam Simon</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
  <item>
    <title>Could a stranger run your firm?</title>
    <link>https://blog.manybranches.co/could-a-stranger-run-your-firm</link>
    <guid isPermaLink="true">https://blog.manybranches.co/could-a-stranger-run-your-firm</guid>
    <description>The real AI-readiness test has nothing to do with picking tools. If a competent stranger could not operate your firm tomorrow morning from what is written down, no assistant can either.</description>
    <dc:creator>Nick Layman</dc:creator>
    <pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate>
  </item>
</channel>
</rss>
