Change Management Communication for Financial Services

# Change Management Communication - Financial Services

## Purpose
Deploy when introducing significant changes such as new systems, restructures, or policy updates to manage the transition smoothly.

## When to Use
A phased communication plan for organisational changes covering announcement, rationale, impact assessment, FAQs, and feedback channels.

## Instructions
1. Review the template below and familiarise yourself with the structure
2. Replace all [bracketed placeholders] with your financial services business details
3. Customise the tone and formatting to match your brand
4. Save in your preferred tool (Slack or Notion)

---

# Change Management Communication Plan

**Change Title:** [Name of the Change, e.g. "Migration to New Project Management Platform"]
**Change Sponsor:** [Senior Leader Name and Title]
**Change Lead:** [Name]
**Effective Date:** [Date]
**Communication Plan Owner:** [Name]

---

## 1. Overview of the Change

**What is changing:**
[Two to three sentences describing the change in plain language. For example: "We are replacing our current project management tool, [Current Tool], with [New Tool]. This will affect how all teams track tasks, report progress, and collaborate on projects. The transition will take place over a four-week period starting [Date]."]

**Why we are making this change:**
- [Reason 1, e.g. "Our current tool does not support the workflow automation we need as we scale"]
- [Reason 2, e.g. "Client feedback indicates our project visibility needs improvement"]
- [Reason 3, e.g. "The new platform integrates directly with our CRM and accounting tools"]

**What stays the same:**
- [Reassurance 1, e.g. "Your team structure and reporting lines remain unchanged"]
- [Reassurance 2, e.g. "All existing project data will be migrated across"]

---

## 2. Communication Phases

### Phase 1: Awareness (Week 1)

**Audience:** All staff
**Channel:** Company-wide email + Slack announcement
**Key message:** "We are making a change to [area]. Here is what, why, and what to expect."

**Message content:**
"Team, I wanted to let you know about an upcoming change that will improve how we work together. Starting [Date], we will be transitioning from [Current State] to [New State]. This decision was made after [brief rationale]. Over the coming weeks, you will receive detailed information about what this means for your role and the support available to help you through the transition."

### Phase 2: Understanding (Week 2)

**Audience:** Department heads and team leads first, then all staff
**Channel:** Team meetings + detailed FAQ document
**Key message:** "Here is exactly how this affects your team, and here is your timeline."

**Activities:**
- Department-specific briefings with Q&A
- Publish detailed FAQ document (see Section 4 below)
- Identify and brief change champions in each team

### Phase 3: Preparation (Week 3)

**Audience:** All affected staff
**Channel:** Training sessions + how-to guides
**Key message:** "Here is how to get ready. Training and support are available."

**Activities:**
- Schedule and run training sessions
- Distribute quick-start guides
- Open dedicated support channel (e.g. Slack #change-support)
- Test run with pilot group

### Phase 4: Go-Live and Support (Week 4+)

**Audience:** All staff
**Channel:** Slack + email + drop-in support sessions
**Key message:** "The change is live. Here is where to get help."

**Activities:**
- Go-live announcement with celebration of the milestone
- Daily drop-in support for the first two weeks
- Collect feedback via short survey after Day 5 and Day 14
- Weekly update on adoption and any adjustments

---

## 3. Stakeholder Impact Assessment

| Stakeholder Group | Impact Level | Key Concerns | Support Required |
|-------------------|-------------|-------------|-----------------|
| [Group 1, e.g. Project Managers] | High | [e.g. "New workflows, retraining"] | [e.g. "Hands-on training, migration support"] |
| [Group 2, e.g. Senior Leadership] | Low | [e.g. "Reporting format changes"] | [e.g. "Dashboard walkthrough"] |
| [Group 3, e.g. Clients] | Medium | [e.g. "Portal access changes"] | [e.g. "Client communication, new login guide"] |

---

## 4. Frequently Asked Questions

**Q: Why are we making this change?**
A: [Clear, honest answer referencing the benefits and the problems being solved]

**Q: Will I lose any of my current data or project history?**
A: [Reassurance about data migration plans]

**Q: What training will be provided?**
A: [Details of training sessions, dates, and self-service resources]

**Q: Who do I contact if I have problems after go-live?**
A: [Support contact, channel, and hours]

**Q: What if this does not work as well as expected?**
A: [Contingency plan and feedback mechanism]

---

## 5. Feedback Channels

- Slack: #[channel-name]
- Email: [change-support@company.com]
- Anonymous feedback form: [Link]
- Weekly office hours: [Day] at [Time] with [Change Lead Name]

---

**Complexity:** advanced | **Setup time:** 30 minutes | **Tools:** Slack, Notion, Mailchimp

Note: This template has been tailored for financial services businesses in Australia. Adjust terminology and compliance references to match your specific context.