← Vault Index
frameworks / kit-change-communication / change-communication-consultant-methodology.md
Source: frameworks/kit-change-communication/change-communication-consultant-methodology.md

Consultant Methodology — Change Communication

Where This Fits in the Engagement

Change communication planning is not a separate engagement. It's a layer that gets added to an existing operational build when the bottleneck shifts from design quality to organizational adoption.

With the two-beat model, structural planning (Beat 1) starts at project scaffolding. The full deliverable build (Beat 2) happens when the first build enters implementation — typically around Week 3-4. The system exists and it's good. But the team hasn't been introduced to it properly, and the evidence is showing up as resistance, confusion, or proxy communication.

How to Identify Beat 2 Readiness

You'll see it in session prep or in between-session communication. The pattern:

What the owner says: "One of my team members mentioned she feels micromanaged" or "I think we need to get the team on board" or "Should I send something to the team about this?"

What's actually happening: The team is experiencing the outputs of a system they were never introduced to. The process owner is communicating about the change through informal channels (Slack summaries, casual mentions) instead of structured walkthroughs. The owner hasn't made a direct statement to the full team establishing what's changing and who owns it.

The diagnostic question: Has the owner, in their own voice, told the full team: (1) what's changing, (2) who owns it, and (3) what it means for each person? If the answer is no — or if the answer is "sort of, through Slack" — Beat 2 triggers.

If Beat 1 was done at project scaffolding, the skeleton communication sequence already exists and the first step (owner announcement) is already in the project plan. Beat 2 is about populating the skeleton with real evidence and building the three deliverables.

Session Structure: Introducing the Deliverables

This is a single session, typically your regular weekly session. You're not adding a meeting. You're using 15-20 minutes of the existing session to introduce the communication layer before moving to the operational agenda.

Before the Session

Have all three deliverables built and QC'd. Review them yourself. Know the sequence cold — you're going to walk the owner through the communication plan, not read it to them.

Prepare the framing: you're not telling the owner they did something wrong. You're identifying a gap that's normal at this stage and filling it with a tool they can use immediately.

Opening (2-3 minutes)

Start with the evidence. Name the specific thing that surfaced — the team member's concern, the Slack message that was a summary instead of a walkthrough, the escalation that went to the owner instead of the process owner. Don't make it a problem. Make it a signal.

Frame: "This tells us the builds are ready, but the team hasn't been introduced to them in a way that sets everyone up to succeed. That's a sequencing issue, and it's normal at this stage. I built three tools to close the gap."

What you're doing here: Reframing resistance as a deployment sequencing problem, not a people problem. The owner shouldn't walk away thinking their team is the issue. They should walk away thinking "we built a great system and now we need to introduce it properly."

Walk Through the Communication Plan (5-7 minutes)

Show the document on screen. Walk through the sequence — not every row, but the logic:

"Your voice comes first. Before the process owner walks the team through the SOP, they need to hear from you that this is your decision and the process owner has your full authority. That's Step 1. Everything else depends on it."

Point to the gate row. Show that the downstream steps are blocked until Step 1 is complete.

Then show the First Win Protocol: "After the first cycle completes, you acknowledge the result in your existing CEO memo. One to two sentences. That's what shifts the team's perception."

What you're doing here: Giving the owner a visual they can hold onto. The communication plan is the artifact that didn't exist — it makes the pacing visible. Don't over-explain. Let the document do the work.

Introduce the Playbook (3-5 minutes)

"This is the tool you'll actually open Monday morning." Show the tab structure. Click through to the Team Meeting section. Let the owner read through the talking points.

Don't read the language blocks aloud. Let them read. Then ask: "Does this sound like you? What would you change?"

This is the moment where the owner takes ownership of the language. They'll modify phrases, swap words, add their own context. That's the goal. The playbook is a starting point — when they edit it, they've committed to delivering it.

What you're doing here: Transferring ownership of the communication from you to them. You built the framework. They make it theirs. The playbook is designed to be edited, not performed.

Brief the Sponsor Role (3-5 minutes)

"The Sponsor Activation Brief is the reference document — it explains the three moments where your voice matters most and gives you frameworks for the 1:1 conversations if someone has concerns after the walkthrough."

Walk through the three sponsor moments (team announcement, first win, 1:1 if needed). Show the 1:1 scenarios briefly — don't read them in detail. The owner will read these on their own when they need them.

Then introduce the coaching ask: "I'd like you to record the team meeting and any 1:1s you have about this. Send me the transcripts. I'll give you feedback on the communication patterns — this is a skill you're building, and it gets easier every time you do it."

What you're doing here: Framing the transcript request as coaching, not evaluation. The owner should feel supported, not observed. The transcripts give you coaching material and also reveal whether the team announcement landed as intended.

Close and Transition (2 minutes)

"You have three documents. The playbook is what you open before each conversation. The communication plan shows you the full sequence. The brief is the reference for why it works this way. Use the playbook Monday — that's the one that matters most this week."

Then transition to the rest of the session agenda (build reviews, outstanding items, etc.).

After the Session

Monitor for Execution

In the next session, ask: "How did the team meeting go?" Listen for:

Coaching from Transcripts

If the owner sends transcripts, review for:

Provide feedback in the next session — specific, behavioral, tied to moments in the transcript. "At the 4-minute mark, you said 'we're all going to figure this out together.' That's generous, but it undermines the authority frame. What you said at the 2-minute mark — '[operations manager] has my full authority on this' — that's the line that did the work. More of that, less hedging."

Watch for the Pattern

If the first close cycle completes and the owner doesn't acknowledge it in the CEO memo, prompt them: "The first cycle completed. Did you put something in the Friday memo?" If they didn't, coach them on why it matters and have them do it retroactively.

If a team member is still resistant after the SOP walkthrough and 1:1 conversation, that's now information — not a communication problem. The team member has seen the system, heard the owner's framing, and had a direct conversation. If they're still resisting, you're learning something about fit, not about communication.

Guardrails

Don't signal headcount conclusions. The change communication methodology reveals who adapts and who doesn't. That information belongs to the owner to act on. Never frame a team member's resistance as a hiring signal in the session. Let the close cycle provide the data.

Don't tell the owner what the problem is. Frame every gap as something you're solving together, not as something they did wrong. "The team hasn't been introduced to the system yet" — not "you didn't communicate this to your team."

Don't fabricate quotes. Every language block in the speech frameworks should be traceable to the owner's actual words or closely adapted from them. If you can't find a quote that fits, write the framework in generic terms and let the owner fill it in.

The coaching ask is optional. If the owner isn't comfortable recording, don't push. The playbook and communication plan work without transcripts. The transcripts make the coaching deeper, but they're not required.

Resistance is information, not failure. If the communication plan is executed correctly and a team member still resists, that tells you the issue isn't communication — it's fit, capability, or willingness. That's a different conversation for a later session.

Connection to Strategic Positioning

This work is what separates operational advisory from tool deployment. Anyone deploying AI agents or building SOPs will hit the same adoption wall. The change communication layer — sponsor activation, communication sequencing, first-win protocol, executive coaching around team leadership — is the work that makes technology stick and the work that compounds over time. Every time the owner gets better at leading operationally, the next build deploys easier.

This is also the hardest work to commoditize. An AI agent can build an SOP. A template library can provide communication frameworks. Nobody is sitting with the firm owner and saying "let me hear how you're talking to your team about this change, because the way you frame it determines whether they adopt it or resist it."

When building the case study from a completed engagement, this is the layer that demonstrates depth: "We didn't just build systems. We developed the owner's capacity to lead through operational change, and here's what that looked like after six months."