Conway's Law and the Cost of Cross-Boundary Queues
In 1968, computer programmer Melvin Conway observed that organizations design systems that mirror their own communication structures. Building on this insight, Matthew Skelton and Manuel Pais authored Team Topologies (2019), demonstrating that when a stream-aligned team must wait on three separate functional silos—security, database administration, and platform approval—to ship a routine change, collaboration overhead skyrockets.
When teams complain of "too many meetings," the meetings are frequently a symptom of unresolved structural dependencies. Because asynchronous handoffs lack clear service-level expectations, leads schedule recurring synchronization calls just to negotiate priority.
Measure Flow Efficiency, Not Busyness
Flow efficiency compares active touch time against total elapsed time (touch time plus wait time). In many corporate environments, flow efficiency sits below 15%—meaning a task takes ten days to finish not because the work is slow, but because it waits eight and a half days in review and handoff queues.
Signals That Reveal Real Collaborative Health
When evaluating whether a team's collaborative habits help or hinder delivery, inspect the interfaces between people.
| Collaboration Question | Signal to Observe | Counter-Signal / Safeguard | What Action It Informs |
|---|---|---|---|
| Are peer reviews acting as a learning loop or a bottleneck? | Time to First Review Response & Review Round-Trips | Post-Merge Defect Rate & Review Batch Size | Agreeing on smaller change batches (under 250 lines/words) and dedicated daily review windows. |
| Do specialists have enough uninterrupted time to solve hard problems? | Weekly Count of Unbroken 2+ Hour Focus Blocks per Person | Team Responsiveness to Agreed Support Channels | Consolidating scattered 30-minute meetings into core collaboration hours or no-meeting mornings. |
| Is knowledge trapped in a single person's head? | Review Participation Distribution (Bus Factor / Lottery Factor) | Onboarding Time for Adjacent Team Members | Pairing on unfamiliar modules and rotating incident or triage duty with shadow support. |
Protecting Deep Work While Staying Responsive
As Georgetown professor Cal Newport argued in Deep Work (2016), and Gloria Mark's attention research at UC Irvine confirmed, recovering full cognitive depth after an interruption takes over twenty minutes. However, total isolation also starves teammates who need a quick unblocking answer.
Team Working Agreement Adjustments
- Define explicit response-time expectations (e.g., peer reviews acknowledged within 4 business hours, not 4 minutes) so people can close chat apps during focus blocks.
- Track external blockers on the team board with a visible day-counter so leadership can clear cross-department queues.
- Audit recurring status meetings every eight weeks: replace verbal round-robins with written ledger updates and reserve synchronous time for complex trade-off debates.