<?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>Notes from Barkan</title>
    <link>https://trybarkan.com/blog</link>
    <atom:link href="https://trybarkan.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Activation, onboarding, and what we learn shipping an AI guide that onboards every user.</description>
    <language>en</language>
    <item>
      <title>When your AI support agent should stop talking</title>
      <link>https://trybarkan.com/blog/when-your-ai-support-agent-should-stop-talking</link>
      <guid isPermaLink="true">https://trybarkan.com/blog/when-your-ai-support-agent-should-stop-talking</guid>
      <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
      <dc:creator>Gabriel Lancelot</dc:creator>
      <description>Containment rewards an AI support agent for avoiding humans, even when the customer is still stuck. Design a handoff that preserves context and recovers trust.</description>
      <enclosure url="https://trybarkan.com/assets/images/og/when-your-ai-support-agent-should-stop-talking.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>Your AI agent's approval prompt is a permission boundary</title>
      <link>https://trybarkan.com/blog/ai-agent-approval-is-a-permission-boundary</link>
      <guid isPermaLink="true">https://trybarkan.com/blog/ai-agent-approval-is-a-permission-boundary</guid>
      <pubDate>Sat, 29 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Maxence Rabrais</dc:creator>
      <description>Design AI agent approvals around consequence, timing, exact action details, and one-shot consent so routine work stays fast without granting broad authority.</description>
      <enclosure url="https://trybarkan.com/assets/images/og/ai-agent-approval-is-a-permission-boundary.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>The second-workflow problem: why activation dies after the first win</title>
      <link>https://trybarkan.com/blog/the-second-workflow-problem</link>
      <guid isPermaLink="true">https://trybarkan.com/blog/the-second-workflow-problem</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Maxence Rabrais</dc:creator>
      <description>Teams optimize the first five minutes and lose users in week two. Learn why the second workflow decides activation, how to measure it, and how to fix it.</description>
      <enclosure url="https://trybarkan.com/assets/images/og/the-second-workflow-problem.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>Why Barkan reads the screen, not the docs</title>
      <link>https://trybarkan.com/blog/why-we-read-the-screen-not-the-docs</link>
      <guid isPermaLink="true">https://trybarkan.com/blog/why-we-read-the-screen-not-the-docs</guid>
      <pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Gabriel Lancelot</dc:creator>
      <description>Doc-trained assistants are confidently generic. Barkan grounds every answer in the live rendered interface. The reasoning, what we capture, and the trade-offs.</description>
      <enclosure url="https://trybarkan.com/assets/images/og/why-we-read-the-screen-not-the-docs.jpg" type="image/jpeg" length="0"/>
    </item>
    <item>
      <title>Nobody reads your documentation — and your activation rate proves it</title>
      <link>https://trybarkan.com/blog/nobody-reads-your-documentation</link>
      <guid isPermaLink="true">https://trybarkan.com/blog/nobody-reads-your-documentation</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>Maxence Rabrais</dc:creator>
      <description>Docs are written by experts, for generic readers, in another tab. See where activation actually leaks, why chat widgets didn't fix it, and what does.</description>
      <enclosure url="https://trybarkan.com/assets/images/og/nobody-reads-your-documentation.jpg" type="image/jpeg" length="0"/>
    </item>
  </channel>
</rss>
