Team Communication Plan
Design communication systems that keep teams aligned without overwhelming them.
Usage
- Audit current communication channels and pain points
- Define which channel serves which purpose (async vs sync, urgent vs routine)
- Establish response time expectations for each channel
- Create meeting cadences and formats for different needs
- Document the plan and review it quarterly
Examples
- Channel purpose matrix: Slack DM: urgent, needs response within 2 hours. Slack channel: team updates, 24h response OK. Email: external communication, formal decisions. Notion/Confluence: documentation, specs, decisions. Meetings: brainstorming, relationship building, complex decisions only
- Meeting cadence for a 6-person team: Daily standup (15min async in Slack), weekly team sync (30min video, agenda required), biweekly 1:1s (30min), monthly retrospective (60min), quarterly planning (half-day). Total meeting time: 3-4 hours/week. Everything else is async
- Status update template: Every Friday, each team member posts: "This week: [3 bullet accomplishments]. Next week: [3 bullet plans]. Blockers: [any, or 'none']." Takes 5 minutes to write, saves a 30-minute status meeting, creates a searchable record
Guidelines
- Default to async communication — most "urgent" messages can wait 2-4 hours. True emergencies are rare
- Every meeting needs: an agenda sent 24h ahead, a facilitator, a note-taker, and action items with owners and deadlines posted within 1 hour after
- Reduce notification fatigue: encourage team members to batch-check Slack 3-4 times/day instead of real-time monitoring
- "Could this meeting be an email?" is a valid question — protect your team's deep work time
- Over-communicate during uncertainty (reorgs, pivots, crises) and under-communicate during stable periods
- Review and prune channels quarterly — unused channels create noise and FOMO