<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Collaboration on hanneseichblatt.de</title><link>https://hanneseichblatt.de/series/ai-collaboration/</link><description>Recent content in AI Collaboration on hanneseichblatt.de</description><generator>Hugo</generator><language>en</language><copyright>© Hannes Eichblatt</copyright><lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hanneseichblatt.de/series/ai-collaboration/index.xml" rel="self" type="application/rss+xml"/><item><title>Case Study Paperclip: The Mission Pattern in Practice</title><link>https://hanneseichblatt.de/posts/case-study-paperclip-mission-pattern/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://hanneseichblatt.de/posts/case-study-paperclip-mission-pattern/</guid><description>&lt;p&gt;&lt;em&gt;This post builds on &lt;a href="https://hanneseichblatt.de/posts/structuring-collaboration/"&gt;Structuring Collaboration&lt;/a&gt;, which defined four AI collaboration modes: Lookup, Workshop, Companion, and Mission.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Mission is the hardest pattern to get right. You hand over a task definition and success criteria, and a trusted agent colleague works autonomously — checking back at decision points, not at every step.&lt;/p&gt;
&lt;p&gt;Most people understand Mission in theory. The difficulty is operational: how do you actually structure delegation so the agent knows what it&amp;rsquo;s working on, when it&amp;rsquo;s done, and when to stop and ask?&lt;/p&gt;</description></item><item><title>Towards an AI Collaboration Skill Tree</title><link>https://hanneseichblatt.de/posts/ai-collaboration-skill-tree/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://hanneseichblatt.de/posts/ai-collaboration-skill-tree/</guid><description>&lt;p&gt;Previous posts established the &lt;a href="https://hanneseichblatt.de/posts/four-modes-of-ai-collaboration/"&gt;four collaboration patterns&lt;/a&gt; and mapped &lt;a href="https://hanneseichblatt.de/posts/structuring-collaboration/"&gt;how organizations onboard agent colleagues&lt;/a&gt;. What&amp;rsquo;s missing is the individual&amp;rsquo;s instrument: a map of where you are, what&amp;rsquo;s locked, what to unlock next.&lt;/p&gt;
&lt;p&gt;RPG players know the skill tree. You pick a path, invest points, unlock gates, specialize. Prerequisites are encoded—no fireball until you&amp;rsquo;ve mastered spark. The tree tells you what to learn, in what order, and what becomes possible. AI adoption needs the same structure.&lt;/p&gt;</description></item><item><title>Structuring Collaboration: AI Adoption as Agentic Onboarding</title><link>https://hanneseichblatt.de/posts/structuring-collaboration/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://hanneseichblatt.de/posts/structuring-collaboration/</guid><description>&lt;p&gt;You&amp;rsquo;re leading a medium-sized tech organization &amp;ndash; 200-500 people across development, operations, analytics, and professional services. Your organization has decided to adopt AI capabilities strategically, not in a panic.&lt;/p&gt;
&lt;p&gt;I think we need to reframe this: &lt;a href="https://garden.hanneseichblatt.de/AI-Human-Collaboration"&gt;AI adoption is agentic colleague onboarding.&lt;/a&gt; You&amp;rsquo;re integrating a new kind of colleague into the way your teams work. The real question isn&amp;rsquo;t &amp;ldquo;which AI tools should we buy?&amp;rdquo; but &amp;ldquo;how do we adapt our &lt;a href="https://garden.hanneseichblatt.de/AI-Human-Collaboration"&gt;collaboration practices&lt;/a&gt; to work with them?&amp;rdquo;&lt;/p&gt;</description></item><item><title>Four Modes of AI Collaboration</title><link>https://hanneseichblatt.de/posts/four-modes-of-ai-collaboration/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://hanneseichblatt.de/posts/four-modes-of-ai-collaboration/</guid><description>&lt;p&gt;Most people I know use AI the same way: type a question, get an answer, move on. That works fine. But it&amp;rsquo;s one of four fundamentally different &lt;a href="https://garden.hanneseichblatt.de/AI-Engagement-Patterns"&gt;engagement patterns&lt;/a&gt;, and treating them as interchangeable is part of why AI-assisted work so often feels like it underdelivers.&lt;/p&gt;
&lt;h2 id="the-four-modes"&gt;The Four Modes&lt;/h2&gt;
&lt;p&gt;The patterns are best understood along two axes: how much context the agent keeps, and how much autonomy you give it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Lookup&lt;/strong&gt; is stateless. You bring a fully specified question; the agent answers it; nothing carries over. It&amp;rsquo;s the right tool for exactly what it sounds like: looking things up. Most people live here.&lt;/p&gt;</description></item></channel></rss>