<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team-Topologies on Eric Irwin</title><link>http://ericirwin.io/tags/team-topologies/</link><description>Recent content in Team-Topologies on Eric Irwin</description><generator>Hugo</generator><language>en-us</language><managingEditor>Eric.Irwin@gmail.com (Eric Irwin)</managingEditor><webMaster>Eric.Irwin@gmail.com (Eric Irwin)</webMaster><lastBuildDate>Sat, 07 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://ericirwin.io/tags/team-topologies/index.xml" rel="self" type="application/rss+xml"/><item><title>Borrowing from Team Topologies to Make Sense of Claude Agent Teams</title><link>http://ericirwin.io/posts/borrowing-from-team-topologies-for-claude-agent-teams/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/borrowing-from-team-topologies-for-claude-agent-teams/</guid><description>&lt;p&gt;There&amp;rsquo;s a habit I can&amp;rsquo;t turn off. Whenever I&amp;rsquo;m working on something — whether it&amp;rsquo;s organizing a project, structuring a team, or just figuring out how to approach a problem — my brain immediately goes to: &lt;em&gt;what&amp;rsquo;s the optimal shape for this?&lt;/em&gt; What information needs to flow, and between whom? Where are the boundaries?&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s the kind of thinking that Matthew Skelton and Manuel Pais gave a name and a framework to with &lt;em&gt;Team Topologies&lt;/em&gt;. If you haven&amp;rsquo;t read it, the short version is that it offers a set of mental models for how engineering teams should be structured — and not around org charts, but around the flow of value. How teams communicate, where cognitive load sits, what interaction modes make sense for a given type of work. It fundamentally changed how I think about engineering organizations, and honestly, it&amp;rsquo;s one of those frameworks that keeps paying dividends years after you first encounter it.&lt;/p&gt;</description></item></channel></rss>