Produce a role-based communications strategy and message architecture for a transformation. Run this command once the structural decisions behind the communication are confirmed.
From change-managementnpx claudepluginhub anthropics/claude-plugins-community --plugin change-management-plugintransformation-name-or-scopeSave the output as a Word document (.docx) using the docx skill. Use Arial font, US Letter page size, professional formatting with proper heading levels, and tables formatted with light gray borders and header row shading.
Ask the practitioner for the following inputs if not already provided in the session context. Ask only for what is missing.
If the practitioner cannot provide confirmed structural decisions, produce a partial plan and flag explicitly which sections require structural confirmation before distribution. Do not omit this flag.
Produce the following output in sequence.
Transformation: [name] Timeline: [go-live or transition date] Plan Date: [today's date]
This plan is ready to go once the sponsor makes the decisions listed below. Messages are organized by audience, sender credibility, and phase. Tier 1 messages depend on confirmed structural decisions. Pre-decision communications can proceed immediately.
The following communications do not depend on structural decisions and can proceed immediately:
No Tier 1 message goes out until all decisions below are confirmed.
Decisions this plan will communicate. See Decision Register for current status.
| Decision | Owner | Effective Date | Confirmed? |
|---|---|---|---|
| [Specific structural decision — e.g., "SAP legacy module deactivated"] | [Named person] | [Date] | [Yes / Pending] |
Flag any pending decisions. Every communication built on a pending decision is announcing an intention, not a fact. Mark those communications as conditional and note what structural confirmation is required before they can be distributed.
For each audience segment, produce the three-question message framework.
[Audience Segment: Role / Function Group]
Repeat for each audience segment identified.
Assign senders by structural credibility tier.
Tier 1 — Structural decision announcements: [Name the sender for go-live confirmation, closed path notifications, and accountability activation messages. This sender must own the decision being announced, not just deliver the message.]
Tier 2 — Operational communications: [Name the senders for role-specific readiness updates and manager-to-team messages. These senders have operational credibility with the audience.]
Tier 3 — Program awareness: [Name the senders for milestone updates and general program information.]
If any Tier 1 communication lacks a confirmed Tier 1 sender, flag that gap. A structural decision announcement sent by someone who does not own the decision lacks credibility and will be perceived as program messaging, not structural fact.
Organize communications across three phases: pre-go-live, go-live week, and post-go-live 30/60/90 days.
For each phase, name the communication, the sender, the channel, the target date, and whether it depends on a confirmed structural decision (and if so, which one).
Pre-Go-Live Phase: [Awareness communications, role-specific preparation, closed path notifications]
Go-Live Week: [Day One confirmation, support structure activation, escalation path communication]
Post-Go-Live (30/60/90 days): [Adoption confirmation, structural condition status, next horizon preparation]
For each closed path, produce a notification template framework with:
This plan conveys structural decisions already made. It cannot make those decisions. If the decisions behind this plan are pending, the plan is announcing intentions. Intentions produce skepticism. Confirmed structural decisions produce behavior change.
A communications plan distributed before structural decisions are confirmed will tell people things that might not be true. When the decisions slip, the credibility of every future communication from the same senders takes the hit.