Invest in implicit coordination (shared models, conventions, templates) over explicit channels — implicit scales without consuming bandwidth

Why This Is a Rule

Explicit coordination — meetings, messages, status updates — consumes bandwidth proportional to the number of connections. With N agents, explicit coordination scales as O(N²) in the worst case: each agent potentially needs to communicate with every other. Doubling the team quadruples the potential communication load. This is why large teams spend most of their time in meetings.

Implicit coordination — shared mental models, naming conventions, templates, documented standards, routine patterns — consumes zero additional bandwidth as the agent count grows. When everyone follows the same naming convention, nobody needs to ask "what did you name the file?" When everyone shares the same decision framework, nobody needs a meeting to align on approach. The coordination is embedded in the shared structure rather than transmitted through communication channels.

The investment priority follows: spend coordination budget on building implicit mechanisms (one-time cost that scales) rather than adding explicit channels (ongoing cost that grows with team size). A 4-hour investment in documenting conventions eliminates hundreds of hours of "how should we..." conversations over the following year.

When This Fires

• When coordination overhead is growing as team/system complexity increases
• When the same types of questions, misalignments, or handoff issues keep recurring
• When deciding where to invest coordination budget (Cap coordination at 15-25% of total hours — new coordination mechanisms must fit within budget or displace existing ones)
• When scaling a system that currently works with explicit coordination but won't scale

Common Failure Mode

Adding meetings to fix alignment problems: "We have misalignment → let's add a sync meeting." This adds explicit coordination bandwidth. A better investment: create a shared template, document the convention, or establish a standard that prevents the misalignment from occurring. The template costs 2 hours to create and eliminates the recurring misalignment; the meeting costs 30 minutes per week indefinitely.

The Protocol

(1) When a coordination problem recurs, ask: "Can this be solved by a shared convention, template, or standard rather than a meeting or message?" (2) If yes → invest in the implicit mechanism: document the convention, create the template, establish the standard. One-time cost. (3) If the problem genuinely requires case-by-case communication → add the explicit channel but keep it within the coordination budget (Cap coordination at 15-25% of total hours — new coordination mechanisms must fit within budget or displace existing ones). (4) For each existing explicit coordination mechanism, ask: "Could an implicit mechanism (convention, template, standard) replace this?" If yes → invest in the implicit mechanism and retire the explicit one. (5) Measure: as implicit mechanisms accumulate, explicit coordination time should decrease. If it doesn't → the implicit mechanisms aren't addressing the actual coordination needs.