Cross-Team Coordination measures the effort, latency, and friction involved when a change requires collaboration between multiple teams. High coordination costs manifest as long lead times, excessive meetings, blocked PRs, and design-by-committee outcomes. Reducing coordination overhead through clear APIs, ownership boundaries, and self-service platforms allows teams to move independently without sacrificing system coherence.
Overhead of coordinating changes across team boundaries. Technically easy, socially complex.
A double-edged sword. Monorepos make cross-team changes technically easy (one commit) but socially complex (multiple CODEOWNERS must approve). Without clear ownership, developers modify shared code without understanding downstream impact. With good tooling, coordination overhead drops vs polyrepo.
CRITICALLY AMPLIFIED: Multi-team PRs requiring approval from CODEOWNERS across non-overlapping TZs can take a week. Each question or concern adds a 12+h round-trip. Three rounds of clarification = a full week lost.
Cross-team coordination overhead grows quadratically. Monorepos make it technically easy but socially complex with multiple CODEOWNERS across team boundaries.
Multi-team PRs require approval from all CODEOWNERS. Timezone differences can add days.
Cross-cutting changes require sync meetings between teams.
Devs batch cross-team changes to minimize coordination rounds. Updating a shared API + 15 consumers in one PR.
Waiting for other teams to approve/review your changes is frustrating, especially with deadline pressure.
Larger blast radius = more teams need to be aware and coordinate. Directly proportional.
Overlap enables synchronous cross-team coordination for complex changes that would take a week via async.