Who Does What? Team Topologies for the Agentic Platform

The agentic platform defines what needs to be provided. Team Topologies defines who provides it, and how teams interact to make it happen. In the first article of this series, we asked the what: which systemic capabilities (context, guardrails, tooling) are needed to produce reliable applications at scale. The answer was the agentic platform, and at its core, the agentic factory: the mechanism where agents plan, code, test, and ship. But a platform does not build itself, and more importantly, it is not consumed the same way it is built. A fundamental question remains: who does what?

Unladen swallow - Olivier Wulveryck

The fourteenth ignite recording from DevOpsDays Zürich 2026 is online. 🎥

Timo Böhm against the Project Mindset. Operations is not a project. Security is not a project. Reliability does not have an end date. Yet we keep squeezing capabilities into projects with Gantt charts and budget caps.

Stop financing temporary fixes, start building long-lived, capable teams.

Watch on Vimeo: https://vimeo.com/showcase/12258234
Or YouTube: https://youtu.be/ixGTRr8VpQ4

#DevOpsDays #TeamTopologies

Next week, I will be at Flowtopic Live 2026. I'm looking forward to be with other practitioners, and I will give my talk "Team Topologies in the Age of AI".

I'm working with some companies that are adopting AI while maintaining flow and allowing platforms to emerge. What have been your experiences with it?

You can join via ➡️ https://www.flowtopia.io/flowtopia-live-2026

#FlowtopiaLive #TeamTopologies #AI

Hallo Mastodon 👋

Ich bin Lead Software Engineer aus Berlin und schreibe hier künftig über Softwarearchitektur, Entwicklung, Teamstrukturen.

Mich interessiert besonders, wie wir Softwaresysteme bauen, die nicht nur technisch funktionieren, sondern auch verständlich, wartbar und anpassungsfähig bleiben.

Sense. Learn. Adapt.

#introduction #SoftwareArchitecture #EventDrivenArchitecture #SoftwareEngineering #TeamTopologies

The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

Learn more here ➡️ https://2026.dddeurope.com/program/from-org-chart-to-designed-organization-making-the-invisible-visible-with-business-models-and-teams/

#DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
June 12.

The premise: you can't design teams without understanding how the business
creates value.

We'll connect Business Model Canvas to Team Interaction Modeling. Practical
heuristics that you will discover by working with your peers!

This is not a slideshow. A lab where you will share insights with others!

Use the link for a discount: https://ti.to/on3/aardling26/discount/SpeakerInvite

#DDDEurope #TeamTopologies #DomainDrivenDesign

You added colors to your org chart and called it Team Topologies.

The authors didn't mean that. They gave us patterns and heuristics for reasoning about the limits of teams' cognitive load and how it affects the flow of value.

We need to put the work into designing non-blocking services, streamlining team interactions, and ensuring value flows through the system.

Org charts show reporting lines. They don't show how value moves.

#TeamTopologies #FastFlowConf

Your org chart may be designing your software more than your architects are.

Learn how to help teams diagnose architecture at the source.

https://jeffbailey.us/blog/2026/05/13/how-do-i-use-conways-law/

#SoftwareArchitecture #ConwaysLaw #TechnicalLeadership #SystemsThinking #TeamTopologies #DistributedSystems #Architecture

How Do I Use Conway's Law?

An index of five focused guides on applying Conway's Law: smoothing platform friction, serving the org, diagnosing delivery, decoding software deployments, and pitching a better architectural design.

Jeff Bailey

Organisational Dysfunction of the Day

Team Topologies, the wrong way round

Context: Leadership has read Team Topologies. The insights are compelling: stream-aligned teams owning end-to-end delivery, platform teams reducing cognitive load, enabling teams building capability. A reorganisation is planned. Teams are renamed and restructured. The new topology is announced. People find themselves in stream-aligned teams that still wait for approval from the same architects, report to the same managers, and receive priorities from the same product managers who held the backlog before. The platform team is the old infrastructure team with a new name and a mandate to serve internal customers, though nobody agreed on what that means. The enabling team runs workshops that nobody has time to attend. Six months in, the cognitive load has not decreased. Delivery has not improved. Leadership concludes that the teams need to embrace the new model more fully. Another round of communication is planned, and product coaches are hired en masse to fix people.

OST explains: Team Topologies describes structural patterns that emerge from healthy organisations. Like DORA, it is a map of what good looks like, not a recipe for getting there. The patterns only function as intended when the teams operating them are genuinely self-managing, owning their work, coordinating among themselves, and making decisions without constant escalation. Imposing the topology from above while leaving the underlying design principle unchanged is a bureaucratic (DP1) move applied to a self-managing (DP2) framework. Stream-aligned teams become delivery units with a new name. Platform teams become service departments, and their internal customer model quietly recreates the same dependency it was meant to dissolve. Goodhart's law applies here as much as it does to DORA: the moment the topology becomes a target, it stops being a good topology. The book is right. The reorganisation missed the point.

#OpenSystemsTheory #SocioTechnical #OrgDesign #TeamTopologies

The Leanpub Podcast 🎙️ Feat. Alexey Krivitsky, Co-Author of 10X ORG: A Manager's Guide to Elevating Business Performance with People and AI

In this episode of the Leanpub Podcast, Len Epp interviews Alexey Krivitsky, co-creator of Org Topologies and co-author of 10X ORG.

The Leanpub Blog