Thoughtworks Technology Podcast · Thoughtworks

Organizational design and Team Topologies after AI

·43 min·2 clips

Team Topologies is framed as the infrastructure for agency in AI teams.

Birgitta Bockeler opens the conversation by framing AI as a question for engineering organizations and, more broadly, knowledge work. Ken McGrage joins her as the other host. They are joined by Matthew Skelton and Manuel Paiz, who bring the Team Topologies perspective. The episode starts by narrowing the AI conversation to the kinds of use cases where organizational design actually matters. That framing matters because the guests are less interested in hype than in what changes in practice. They treat AI as something that may alter how groups are structured, how responsibilities are divided, and how work is maintained. The discussion also sits in the context of the second edition of the Team Topologies book, launching in September 2025. That upcoming release gives the episode a forward-looking edge without turning it into a launch pitch. The guests argue that some Team Topologies fundamentals still map well to AI-enabled work. They point to knowledge work as a domain where concepts, boundaries, and domain fidelity still matter. They also suggest that the same principles may be useful when thinking about how AI-based work gets organized. The conversation then turns to ownership and stewardship. The guests distinguish between software that can be treated as throwaway and software that must be cared for over time. A pension pot is used as a clear example of something that needs long-term stewardship. The point is not that AI removes maintenance. The point is that AI changes which systems can tolerate rough edges and which ones absolutely cannot. From there, the discussion moves into historical context and the reasons a thing is being evolved in a particular way. That leads naturally into domain modeling and the idea that language, meaning, and coupling still shape system design. The guests connect that back to Eric Evans and the long-standing discipline of ubiquitous language. The result is a conversation that treats AI as a reason to sharpen boundaries, not abandon them. The episode ends by pointing listeners toward the Team Topologies launch and its case studies. It also notes that questions about AI are likely to come up there too. The tone stays measured throughout, but the argument is clear. AI may change the texture of work, yet the need for good organizational design does not go away. This is especially relevant when companies need to decide what to automate, what to steward, and what to keep tied to human judgment. The episode is strongest when it stays inside those distinctions and lets them build on each other. It asks listeners to think about AI as an operating-model problem, not a novelty.

As heard by us

AI here is treated as an organizational design problem, not a product demo.

ThoughtWorks treats AI less like a shiny feature and more like a question of how organizations are built. The episode keeps returning to a practical tension: what deserves stewardship, what can be dropped, how shared meaning survives as systems change, and why Team Topologies…

Read the full review in PlayNext →

Why you'd press play

If AI is changing how your teams work, this helps you think beyond tools and toward how work is organized.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Thoughtworks Technology Podcast