The problem
Change management lives or dies on communication. Research consistently shows that employees who understand the reason for change and what it means for them are significantly more likely to engage positively than those who receive generic top-down announcements. Yet most change communications are exactly that: generic, top-down, and failing to address the questions that matter to the people on the receiving end.
Part of the problem is volume. A significant organisational change might require a leadership briefing document, an all-staff announcement email, a team briefing template for line managers, a FAQ document, a digital communications pack, and updates for the intranet. Creating all of this coherently, consistently, and quickly is a substantial writing task.
The other challenge is tone calibration. The message to the executive team is different from the message to frontline staff, even if the underlying facts are the same. Getting the register right for each audience requires careful thought.
The system
Step 1: Define the change communication brief (Claude)
Start by briefing Claude on the change itself:
"I am a change management consultant helping a client communicate [type of change — e.g., a restructure, a system migration, an acquisition] to their organisation. Here is the context:
- What is changing: [describe]
- Why it is changing: [describe]
- Timeline: [describe]
- Who is affected and how: [describe]
- Key concerns we anticipate: [describe]
- The client's values and communication style: [describe]
Before we write any communications, identify: the key messages that must be consistent across all communications, the top five questions employees are likely to ask, and any sensitive areas that need careful handling."
This step surfaces potential issues before you start writing.
Step 2: Create the messaging hierarchy (Claude)
"Based on this brief, create a messaging hierarchy for the change communication cascade. Include:
- The core narrative (one paragraph) — the consistent story that underpins all communications
- Leadership communication key points (for an executive briefing document)
- All-staff communication key points (for a company-wide announcement)
- Line manager briefing key points (for team-level conversations)
Flag where the same fact needs to be communicated differently to different audiences."
Step 3: Draft each communication (Claude)
Use individual prompts for each communication:
"Using the messaging hierarchy, write the all-staff announcement email. It should: explain what is changing and why in plain language, address the top three employee concerns directly, be honest about what is not yet known, and tell staff what happens next and when. Length: 300 words. Tone: honest, reassuring, and respectful. UK spelling, no em dashes."
Repeat for each communication format, adjusting the brief for each audience.
Step 4: Build the FAQ document (Claude then Notion AI)
"Create a comprehensive FAQ document for employees covering the 10 most likely questions about this change. For each question, provide a clear, honest answer. Flag any questions where the answer is 'we don't know yet' rather than fabricating a response."
Paste the FAQ into Notion and use Notion AI to check it for consistent tone and flag any answers that might come across as evasive or corporate.
The results
Before: A full change communication cascade taking 8 to 12 hours to write, often drafted by different people with inconsistent messages.
After: 3 to 4 hours for a complete, consistent communications package drafted by one consultant using a shared brief.
The consistency improvement is the biggest win. When communications are drafted from the same core narrative in the same session, they tell a coherent story. Employees at every level receive the same fundamental message, even if the language and emphasis differ. That coherence is what builds trust during change.
One consulting team used this workflow for a 400-person manufacturing company restructure. The HR director commented that it was the clearest change communication she had seen in 20 years of HR. The answer: the messages were consistent because they came from a single structured brief, not from six different people writing in silos.