# team-topologies Published articles for team-topologies. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Thursday Notes on Architecture Trade-offs and High-Performing Teams DevFeed: [Thursday Notes on Architecture Trade-offs and High-Performing Teams]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-09-10T15:00:57Z Content type: opinion Language: en Sources: [Tech World With Milan Newsletter]() Topics: [Architecture & Design](), [Microservice]() Tags: [architecture](), [fault-tolerance](), [security](), [software-architecture](), [split](), [team-topologies](), [transactions]() ### AI overview This issue of Thursday Notes discusses architecture as a search for acceptable trade-offs, including reasons to split or merge services. It also explains how teams cycle through forming, storming, norming, and performing, and how leadership should adapt to each stage. ### Source excerpt Hey, Milan here. ## Team Topologies DevFeed: [Team Topologies]() Original publisher: [Read original article]() Author: Tom Published: 2026-04-26T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [DevOps](), [Architecture & Design](), [Software]() Tags: [architecture](), [business](), [cognitive-load](), [collaboration](), [conway-s-law](), [flow](), [leadership](), [management](), [platform](), [team-topologies](), [technology]() ### AI overview This article summarizes Team Topologies by Matthew Skelton and Manuel Pais, focusing on organizational design for software teams. It explains the four team types, three interaction modes, cognitive load, Conway's Law, the Reverse Conway Maneuver, and the Thinnest Viable Platform. ### Source excerpt Team Topologies Organizing Business and Technology Teams for Fast Flow Authors: Matthew Skelton, Manuel Pais Team Topologies is a must-read for anyone involved in building software at scale. It moves away from the "everyone should talk to everyone" fallacy and introduces a pragmatic, team-first approach to organizational design. By focusing on cognitive load and the flow of value, Skelton and Pais provide a clear vocabulary for discussing team structures and their interactions. ## Gremlin's unofficial reliability track for Gartner IOCS 2025 DevFeed: [Gremlin's unofficial reliability track for Gartner IOCS 2025]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-12-01T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [SRE](), [incident](), [Critical Infrastructure](), [AI Agent](), [genai]() Tags: [2025](), [agentic-ai](), [analysts](), [critical-infrastructure](), [gartner](), [incident](), [site-reliability](), [talks](), [team-topologies]() ### AI overview Gremlin presents an unofficial reliability-focused track for Gartner IOCS 2025, highlighting sessions on software-update risks, critical dependencies, SRE team structures, and the future of reliability in an AI agent world. ### Source excerpt Check out the Gremlin-curated unofficial track of reliability talks at Gartner IOCS 2025. ## Applying the Inverse Conway Manoeuvre to Existing Sociotechnical Systems DevFeed: [Applying the Inverse Conway Manoeuvre to Existing Sociotechnical Systems]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-04-15T06:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [systems](), [structure]() Tags: [architecture](), [collaboration-employee-happiness-software-architecture-team-topologies-technical-leadership-eng](), [conway-s-law](), [organizational-design](), [team-topologies]() ### AI overview The article examines whether the Inverse Conway Manoeuvre can change the architecture of existing sociotechnical systems by altering team structures and communication paths. It argues that existing teams, communication paths, and system architectures create significant difficulties for this approach, unlike greenfield environments. ### Source excerpt The Inverse Conway Manoeuvre in Existing Systems - It does not work! In 1968, Melvin E. Conway postulated a law about a connection between organizational design and system structure, which got pretty famous. The paper has the title "How Do Committees Invent?" and the law goes as follows: ## How the BBC Reorganized for Its WebCore Website Initiative DevFeed: [How the BBC Reorganized for Its WebCore Website Initiative]() Original publisher: [Read original article]() Author: Graeme Lindsay Published: 2022-03-07T11:18:47Z Content type: article Language: en Sources: [BBC]() Topics: [Website](), [Cloud](), [Serverless](), [Development](), [User Experience]() Tags: [cloud](), [conways-law](), [engineering](), [platform-engineering](), [refactor](), [reorganization](), [serverless](), [team-topologies](), [user-experience]() ### AI overview The BBC describes how its WebCore initiative to reimagine BBC Online required organizational changes alongside technical work. The article discusses the history of separate digital-service teams, duplicated capabilities and maintenance costs, and the role of shared platforms and team interactions in creating a single website strategy. ### Source excerpt Changing the organisation -- to build the technology right.In earlier blog posts, we explored how we moved BBC online to the cloud. This was part of a wider initiative called WebCore, which used a range of serverless technologies to reimagine the BBC website. There were technical challenges we faced integrating WebCore with our architecture, but this initiative has been as much a refactor of our organisation, with profound implications on the people within it. In this blog post, rather than focus just on the technical challenges, I want to share: Some of the organisational history that led to WebCore How we went about re-organising for success How we viewed the team topologies and interaction modes between teams How we view the role of the platform (and the Core teams who build it) in enabling many teams to interact with one another First -- some history... The BBC website is made up of several digital services, including iPlayer, Sounds, News and Sport. Each is a major service in its own right -- with millions of visits every week -- and they have grown independently of one another over several years. This was reflected in the way the organisation was shaped -- with separate departments owning each digital service. This shape meant each individual product achieved its own aims well, but it also meant the user experience across multiple services wasn't as seamless and consistent as it could have been. There were mismatched technologies and duplication between the services. Lots of features, despite being conceptually similar, were implemented multiple times -- with the total cost of maintenance also paid multiple times. Cross-cutting capabilities -- e.g., personalisation and analytics -- were major tasks that each product development team had to tackle themselves. WebCore is part of a strategy to re-imagine BBC Online and create a single website for all the digital services. Standardising onto a single technology set, building shared 'horizontal' capabilities, and sharing com ## How Platform Teams Can Enable Developer Experience DevFeed: [How Platform Teams Can Enable Developer Experience]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2022-02-05T12:49:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [Development](), [ci]() Tags: [ci](), [developer-experience](), [development](), [software-development-team-topologies-developer-productivity-engineering-excellence-organizationa](), [team-topologies]() ### AI overview The author shares lessons from establishing a platform and developer experience unit at BRYTER. The article argues that platform teams should enable other development teams to work independently instead of doing work for them, such as by providing reusable base configurations for common CI jobs. ### Source excerpt A platform team for next-level developer experience In this article, I am sharing my experience (and opinions) of how a platform team should be set up to provide great developer experience for other development teams.