Change Communication Planning

What This Kit Does

This kit builds the communication layer that makes operational system deployments stick. It produces three client-facing deliverables — a Change Communication Plan, a Sponsor Activation Brief, and a Team Communication Playbook — that give the firm owner a clear sequence for introducing change to their team and the language to lead it.

The Gap It Fills

The Advisory OS deployment methodology (Design → Review → Implement → QC1 → Train → QC2 → Live → Optimize) handles what gets built and how it gets transferred. It does not handle who hears about the change, in what sequence, with what framing, from whom, before the build touches them. These are two parallel tracks — build deployment and change communication — and this kit addresses the second one.

Two-Beat Model

Change communication is not reactive. It starts when the project is scoped and completes when builds enter implementation.

Beat 1 — Structural Planning

When: Project scaffolding (Step 4 in engagement workflow — Project Plan + Blueprint)

Filter: Does this client have a team that will be affected by the builds? If yes, Beat 1 starts here. If the client is solo or the builds only affect the owner, skip this kit.

What gets built:

• Communication sequence skeleton — who will need to hear what, in what order, with what prerequisite
• Ownership mapping decision — who is gold (process owner) in the communication documents (always the firm owner, not the operations manager)
• Affected team identification — which team members will experience each build
• Likely resistance patterns based on constraint matrix (structural, not evidence-based yet)
• Project plan items for communication steps (so they don't get forgotten)

What you don't have yet: Real evidence. No resistance has surfaced. No Slack messages, no escalation patterns, no team member quotes. Beat 1 is structural planning — the skeleton that gets populated later.

Beat 2 — Evidence-Based Build

When: First build enters Implement in the deploy cycle. Evidence of team dynamics now exists.

What triggers it: At least one build has moved past Design and Review into Implement. The system exists, it's been approved, and it's about to touch people who haven't seen it yet. Look for these signals:

• Team member(s) expressing resistance to a process they haven't actually seen
• Process owner summarizing or paraphrasing the system instead of showing it directly
• Firm owner acting as participant rather than sponsor ("we're doing this" instead of "I decided this, here's who owns it")
• Team members escalating to the owner instead of to the designated process owner
• Owner hasn't made a direct statement to the full team about what's changing and why

What gets built: Three deliverables populated with real evidence from the engagement:

1. Change Communication Plan — sequencing grid with gate mechanism, First Win Protocol
2. Sponsor Activation Brief — team announcement framework, 1:1 scenarios from evidence, coaching ask, change network
3. Team Communication Playbook — interactive tabbed document (team meeting, 1:1 concerns, CEO memo, weekly check-in)

What you have now that you didn't in Beat 1: Real resistance patterns from actual conversations, client quotes showing the owner's voice, evidence of communication gaps, specific team dynamics.

What It Produces

Three HTML deliverables, all client-facing, all in the client's brand system:

File naming: [client]-change-communication-plan-[mon]-[yyyy].html, [client]-sponsor-activation-brief-[mon]-[yyyy].html, [client]-communication-playbook-[mon]-[yyyy].html

Required Inputs

Beat 1 (Structural Planning)

1. Project plan with build sequence and stakeholder map
2. Constraint matrix or diagnostic
3. Team roster from reference data

Beat 2 (Evidence-Based Build)

All Beat 1 inputs, plus:

1. The SOP or system being deployed
2. Evidence of team dynamics — email threads, Slack messages, session transcripts, consultant notes showing how the team is experiencing the change
3. Client quotes — direct language from the owner showing their voice and framing
4. Client brand system — typography, colors, ownership color mapping, design patterns

Key Principle

The owner of the communication plan is the firm owner — not the operations manager, not the consultant. Gold (process owner color) follows whoever owns the process in that specific document. In the SOP, the operations manager is gold because they own the operating process. In the communication plan, the firm owner is gold because they own how the team hears about it. Different documents, different process owners. This distinction matters for every ownership tag, border color, and legend across all three deliverables.

File Inventory