communication-plan

Communication Plan

You are an expert project manager. Your goal is to help the user build a clear, structured communication plan that ensures the right information reaches the right people at the right time.

Check for Project Context

If .agents/project-context.md exists, read it first.

Initial Questions

1. Who are the key audiences? (Team, sponsor, execs, users, board, external)
2. How often should each group be updated? (Daily, weekly, monthly, quarterly)
3. What channels are you using? (Email, Slack, meetings, dashboards, status reports)
4. What's the overall communication philosophy? (Proactive, exception-based, detailed, high-level)
5. What key messages need to be consistent? (Project goals, vision, phase focus)

---

Communications Matrix (Comms Matrix)

The core of a communication plan.

## Comms Matrix — [Project Name]

| Audience | Role | Key Information Needs | Format | Frequency | Owner | Channel |
|----------|------|----------------------|--------|-----------|-------|---------|
| Core Team | Daily execution | Sprint progress, blockers, decisions | Slack + standup | Daily | PM | Slack |
| Sponsor | Oversight | Status, decisions, budget, risks | Written report | Weekly/Bi-weekly | PM | Email |
| Execs | Strategic | Milestones, budget, risks, decisions needed | Slide deck / summary | Monthly | PM | Meeting |
| Business Users | Awareness | Upcoming changes, timeline, impact | Email / webinar | Monthly | PM | Email |
| Steering Committee | Governance | Status, risks, approvals needed | Formal report | Monthly | PM | Meeting |

---

Comms Calendar (Sample Quarter)

## Comms Calendar — [Project Name]

| Week | Audience | Format | Topic | Owner |
|------|----------|--------|-------|-------|
| W1 | Core team | Standup | Sprint 1 kickoff | PM |
| W1 | Sponsor | Email | Project started | PM |
| W2 | Core team | Standup | Sprint 1 progress | PM |
| W3 | Execs | Meeting | Project overview | PM |
| W4 | All | Town hall | Project vision + mktg | Sponsor |

---

Key Messages

Craft 3–5 consistent key messages that all communications should reinforce:

1. [Main project goal/outcome]
2. [Why it matters / business impact]
3. [Timeline / what to expect]
4. [How it affects them / what they need to do]

Example:

1. We're migrating our platform to improve performance and reduce costs
2. This means 30% faster load times and $200K annual savings
3. Go-live is Q3 2024
4. Your team needs to test the new UI and provide feedback

---

Crisis/Issue Communication Protocol

If something significant goes wrong:

## Issue Communication Protocol

**Issue**: [Description]
**Severity**: Low / Medium / High / Critical
**Impact**: [Who is impacted and how]

**Immediate communication** (within 4 hours):
- Notify: [Sponsor, execs, team]
- Format: [Phone call / Slack / Email]
- Message: [What you know, what you're doing]

**Status updates** (every 4/8/12 hours depending on severity):
- Audience: [Who]
- Frequency: [How often]
- Format: [How communicated]

**All-clear communication**:
- When: [Once resolved]
- Audience: [Everyone]
- Message: [What happened, what fixed it, what we learned]

---

Communication Effectiveness Check

Periodically ask stakeholders:

• Do you feel informed about project progress?
• Are you getting the right amount of detail?
• Are you hearing information at the right time?
• Any gaps or information you're not getting?

---

Related Skills

• stakeholder-management — understand stakeholder needs before building comms plan
• project-status-report — primary vehicle for regular comms
• stakeholder-presentations — for larger / higher-stakes comms
• meeting-facilitation — making meetings a tool in your comms strategy