5.3Communication planning

As a project's headcount grows, the number of possible communication channels among participants increases more sharply than intuition suggests. Adding members without understanding this structure can let communication complexity overwhelm project management and actually reduce productivity. This section covers calculating the number of channels and how to handle its growth, along with choosing a communication method and medium appropriate to the situation.

5.3.1Communication channels n(n-1)/2 and the rapid growth from adding members

• If a project has n participants, the potential number of communication channels among all possible one-to-one pairs is given by n(n-1)/2. This equals "the number of ways to choose a pair of 2 people from n." Even as headcount grows linearly, the channel count balloons at a rate close to the square of headcount, so the PM must always weigh the benefit of adding members against the cost of managing the resulting communication.
• Manual check: going from n=5 (10 channels) to n=8 (28 channels) is a 1.6x increase in headcount but a 2.8x increase in channels. n=5 gives 5×4/2=10; n=8 gives 8×7/2=28. Rather than avoiding additional headcount outright because of this nonlinear growth, an effective practical design judgment is to avoid a structure where everyone communicates directly across every channel, and instead introduce roles for aggregating and distributing information (e.g., a hub structure via team leads, a regular reporting line) to narrow the channels actually used.

5.3.2Push, pull, and interactive methods, and media selection

• Push communication is where the sender actively sends information to a specific recipient (email, notifications, circulated documents, etc.). It suits routine information that must reliably reach someone but is not urgent, though delivery is not the same as understanding or agreement. Pull communication is where the recipient actively retrieves information when needed (an intranet portal, a shared repository, a knowledge base, etc.). It is efficient for large volumes of standing information or when different recipients need different information, but has the limitation that information does not reach anyone unless they actively go look for it. Interactive communication—meetings, calls, chat exchanges, and the like—is where sender and recipient exchange information through dialogue. Because it can resolve misalignment on the spot, it is the most reliable option for complex issues or situations requiring agreement, but it is costly because it occupies participants' time simultaneously.
• Media selection is the judgment of combining the three methods above with a concrete means (in-person, video conference, chat, email, document) based on the urgency, complexity, audience size, and need for a record of the content being communicated. The standard practice is to match the means to the nature of the content: urgent and complex content (e.g., a major risk materializing) calls for interactive in-person or video conferencing; routine content where a record matters (e.g., a formal progress report) calls for a pushed document; large volumes of reference material call for a pull-based repository. Handling everything uniformly via email is inappropriate for situations requiring urgent response or agreement-building.

Suppose a project initially operated with a team of 5, giving a potential channel count at that point of 5×4/2=10. As the project grew, the team expanded to 8, and the PM calculated the new channel count as 8×7/2=28. Even though headcount grew only 1.6x (5 to 8), the channel count balloons 2.8x (10 to 28). Given this nonlinear growth, the PM judged that if everyone continued to communicate all information directly with everyone under the expanded team, the volume of information each member must track and the coordination overhead would explode, likely slowing decisions rather than speeding them. So the PM split the 8 members into two subteams (4 each), placed a team lead over each subteam, and redesigned the structure so that detailed exchanges within a subteam stay within that subteam, while sharing across subteams and to the whole group is consolidated through a hub structure via the team leads. As a result, the channels that the PM and members must actually track day to day were substantially narrowed. The PM further matched the communication method to the nature of the information: routine weekly progress used push (a progress report broadcast to stakeholders), large volumes of design documents and past meeting minutes used pull (consolidated in a shared repository for whoever needs them), and a serious quality defect discovered in manufacturing—a complex issue that could affect the delivery date—was judged too risky to leave to a one-way email, which could leave misalignment in place; the PM instead chose interactive communication by convening an urgent video conference. Had this quality-defect notification also been handled purely by email (push), there was a risk that different recipients would interpret the severity differently, delaying the initial response. As this shows, when headcount grows, the judgment this section calls for is to design the structure around the nonlinear surge in channels (narrowing the channels actually used via a hub structure or similar), and to switch the communication method based on the urgency and complexity of the content.

5.3.3Section summary

• The potential number of communication channels n(n-1)/2 balloons at a rate close to the square of headcount (e.g., 5→8 people takes channels from 10 to 28)
• When adding members, a structure that narrows the channels actually used, such as a hub structure (subteams plus a lead aggregating), is effective
• Push delivers but does not guarantee understanding/agreement; pull is efficient but assumes active retrieval; interactive is best for building agreement on urgent/complex issues