AT-201c · Module 3
Team Restructuring
3 min read
As the team grows past 10 agents, the hub-and-spoke topology starts to strain. The coordinator becomes a bottleneck — too many handoffs to review, too many dispatches to manage, too many results to synthesize. This is not a failure of the coordinator. It is a scaling signal. The architecture needs to evolve from a single hub to a hierarchical coordination model where sub-coordinators manage domain clusters.
A domain cluster is a group of agents that work together frequently on the same type of task. At Ryan Consulting, the revenue cluster includes HUNTER, CLOSER, and LEDGER. The content cluster includes BLITZ, QUILL, and BUZZ. The intelligence cluster includes SCOPE, CIPHER, and VANGUARD. Each cluster gets a lead agent or a sub-coordinator that handles intra-cluster communication. I coordinate between clusters, not between individual agents. This reduces my handoff volume by 60% while maintaining full traceability through the cluster leads.
The restructuring principle is: coordinate at the highest level where quality is maintained. If the HUNTER-to-CLOSER handoff is reliable and the contract is tight, I do not need to review every lead handoff. The revenue cluster lead handles intra-cluster communication. I review the cluster's output and the cross-cluster handoffs where different domains intersect.
- 1. Identify Natural Clusters Analyze the communication patterns from your trace logs. Which agents talk to each other most frequently? Those natural communication groups are your domain clusters. Do not impose clusters — discover them from the data.
- 2. Designate Cluster Leads Each cluster gets a lead agent or a lightweight sub-coordinator. The lead handles intra-cluster dispatch, review, and handoffs. The lead reports cluster-level results to the top-level coordinator.
- 3. Define Cross-Cluster Protocols When a task requires agents from different clusters, the top-level coordinator manages the cross-cluster handoff. Define which types of work stay within a cluster and which require cross-cluster coordination.
- 4. Measure and Adjust After restructuring, compare coordination efficiency, throughput, and cost to the pre-restructuring baseline. If CE improved, the clusters are working. If it dropped, the cluster boundaries may need adjustment.