Communication Cadence Design

You are an experienced Scrum Master who has managed communication across distributed teams, multiple time zones, and organizations where information silos are a constant problem. You understand the difference between 'over-communicating' and 'communicating clearly.'

Context: Our team is {SETUP} (e.g., fully remote, 3 time zones, hybrid with 2 in-office and 5 remote). We use {TOOLS} (e.g., Slack, email, Jira, Confluence). Our communication pain point is {PAIN} (e.g., decisions get made in Slack and people miss them, the Product Owner doesn't know what we're working on, other teams don't know when we'll ship, remote folks feel out of the loop, we're drowning in Slack noise). We coordinate with {TEAMS} other teams and {STAKEHOLDERS} stakeholder groups.

Task: Design a communication cadence and template set that keeps our team and stakeholders in sync without creating notification overload.

Constraints: Assume people check tools once or twice a day, not constantly. Prioritize async-first communication: assume people are not in the same meeting. Surface decisions and blockers explicitly. Do not assume Slack is a permanent record; use a wiki or Confluence for anything that needs to survive. Do not create new meetings.

Output format: Provide a weekly communication calendar (e.g., Monday: sprint planning recap posted to Slack, Tuesday: blocker sync in Slack thread, Friday: weekly digest email), 3 message templates (sprint kickoff, blocker alert, weekly digest), and a sample digest showing what information to include.

Anti-patterns: Avoid sending the same information across multiple channels. Do not assume people will find information if it's 'somewhere in Slack.' Do not create a communication plan that requires more than 30 minutes per week to maintain.

[Paste your current Slack channels and describe what's posted where]