A communication channel is an agreed way for project participants to exchange information. For an engineering manager, choosing channels is part of making collaboration predictable: people should know where to discuss a design, ask for support, or share an update. A channel might use Slack, email, or Microsoft Teams; agreeing on the tool is only one part of the plan. section 9.2.1 section 9.2.3
Set up channels as part of a communication framework:
- Identify who needs to communicate. Clarify project goals, deliverables, dependencies, and roles so updates reach the relevant people. section 9.2.3
- Give channels distinct purposes, such as technical-design discussion and general support, and agree how often working teams and stakeholders need updates. section 9.2.1 section 9.2.3
- Ask about communication preferences. Surveys and polls can help accommodate different teams’ practices; anonymous platforms can give people room to raise concerns. section 9.2.3 section 9.2.1
- Keep the arrangement focused. Too many channels can dilute their purpose; periodically check whether people can still find the right conversation. section 9.2.1
When communication breaks down
Repeated sprint spillovers may look like a delivery problem. In one team, investigation instead found duplicate work, an uncommunicated vacation, and slow code reviews. Clearer channels and stronger collaboration were part of addressing the underlying problem—not a substitute for checking other causes of underperformance. section 4.5.4
Include channels in project kickoff planning, then use them during execution alongside check-ins and feedback loops. During a leadership change, make room for candid communication as well as formal announcements. Ask: can everyone tell where to raise an issue and when to expect an update? section 10.3 section 13.3.1
