Independence,autonomy,too many small teams | Kislay Verma

team-organizationautonomysoftware-engineeringmanagement

Abstraction: Why over-splitting teams destroys autonomous delivery capacity

Key points:

The "two-pizza team" concept was meant to minimize cross-team communication and enable end-to-end customer value delivery, not just operational independence
Organizations mistakenly slice problem spaces too finely (e.g., "Data Ingestion Team," "Data Processing Team," "Data Release Team" instead of one "Data Delivery Team"), multiplying coordination overhead
True autonomy is a customer-facing construct: a team is autonomous only when it delivers value to the customer independently, not merely when it executes independently
Amdahl's Law explains the ceiling: every extra worker imposes non-parallelizable, exponentially increasing communication overhead
Theory of Constraints view: the organization should be seen as a factory floor where the only way to increase output is to broaden bottlenecks across the whole value chain, not optimize local steps
Scaling autonomous teams is recursive: as teams grow they re-fragment into sub-teams, recreating the independence-vs-autonomy problem at larger scale

Connections: Kislay Verma · Team Autonomy · Software Team Organization · Theory Of Constraints