internal-comms

---
name: internal-comms
description: Use when drafting or sequencing an internal change-management announcement — a re-org, tool rollout, policy change, leadership transition, layoff, or acquisition — for an employee audience.
category: Business Operations
version: 1.0.0
tools: []
---

# Internal Change-Management Communications

Author the comms package for a specific internal change event — the primary announcement, the FAQ, manager talking points, and the touchpoint calendar — for an employee audience, not customers. The core decisions are timing, sequencing, channel mix, and what to deliberately not say.

## Why these fail

Internal change announcements fail in four predictable ways: no framework (written from instinct, magnitude mis-set, tone collides with content — celebratory framing for a job cut, "minor update" for a large layoff); no touchpoint sequencing (a single Slack post treated as the whole comms plan, when Prosci research shows 5-7 touchpoints is the floor for behavioral change); no FAQ scaffolding (the questions employees actually ask — "will my comp change?", "will I report to someone new?", "is this a precursor to layoffs?" — go unanswered and leak ambiguity into Slack); and no manager cascade (front-line managers learn at the same time as their reports, so when an IC asks a question the manager can't answer it — Prosci consistently rates the direct manager as the single most-trusted change-communication channel).

Anchor every decision in ADKAR (Prosci) and Kotter's 8-step change model, not intuition.

## When to use

A re-org, leadership change, tool rollout, policy or benefit change, layoff, or acquisition close needs internal announcement within 48 hours. A draft exists but there's no touchpoint calendar. An internal FAQ is needed but the obvious employee questions haven't been seeded. Manager talking points are needed for a coherent front-line cascade. A previous announcement landed badly and needs an anti-pattern audit before the next one.

## When not to use

Customer-facing launch comms, press releases, or blog posts are a different audience and trust model. Strategic multi-quarter narrative framing of a transformation arc is a different scope than one announcement. Executive change-strategy design (sponsor coalition, change-saturation analysis across a portfolio) is strategy; this is tactical authoring of one event. Authoring the underlying HR policy itself is out of scope — this assumes the policy decision is already made.

## Method

1. Intake the change: type (reorg, tool rollout, policy change, leadership change, layoff, acquisition, internal product launch, benefit change), audience segments, magnitude (low/medium/high/disruptive), effective date, available channels.
2. Assess magnitude-to-tone fit. A disruptive change with "exciting news" framing, or a high-magnitude change labeled "minor update," is a validation failure — magnitude and tone must agree. Structure the primary announcement as Kotter's 8 steps, each labeled: Establish Urgency, Build Coalition, Form Vision, Communicate Vision, Empower Action, Generate Wins, Sustain Momentum, Anchor in Culture. Tune tone by context — public-company tone stays more conservative (material-event awareness), startup tone can be more direct.
3. Plan touchpoints. Build a 7-touchpoint sequence keyed to T-minus/T-plus days relative to the effective date, each with a channel, an owner, an ADKAR stage (Awareness, Desire, Knowledge, Ability, Reinforcement), and a key message. Flag gaps (e.g. only 2 touchpoints for a disruptive change) and channel mismatches (e.g. Slack-only for a layoff, which needs a synchronous channel).
4. Draft the full package: pre-comm, announcement, FAQ, and follow-up, each touchpoint tagged to the ADKAR stage it serves and tailored per audience segment.
5. Run the anti-pattern sweep below before publishing — any single hit is a "do not send" signal.

## Anti-patterns

Slack-only announcement of a high or disruptive change — synchronous channels (town hall, manager 1:1) are required for trust-laden events. Passive voice for accountability ("decisions have been made") hides the decision-maker — name them. Magnitude downplay ("minor restructuring" for a large layoff) is the Better.com/Vishal-Garg failure mode. No manager talking points — the front-line cascade breaks on first contact. Celebratory framing for a job cut ("streamlining to focus on our mission") is a documented post-mortem failure pattern. Bundled clarifying questions instead of one at a time with a recommendation. No follow-up touchpoints — a single announcement is not a comms plan; the Prosci floor is 5-7. Skipping the FAQ — employees ask the questions anyway, and Slack will write the FAQ badly if you don't.

## Assumptions

The user has authority (or clear sponsor delegation) to publish; without it, this produces a draft, not a publication. The decision is already made — this helps announce a re-org already decided, not decide whether to re-org. Audience segments are named honestly — "all-hands" is rarely the right segment; managers, ICs, the affected team, and the unaffected team usually need different framing. The magnitude field is honest — a 30% reduction in force is disruptive, not high; mislabeling magnitude is the most common upstream error and breaks every downstream decision. The effective date is fixed — sliding it after publication is a separate trust event requiring its own comms cycle.

## Forcing-question library

Walk these one at a time, each with a recommended answer and its source, never bundled:

1. What is the magnitude — low, medium, high, or disruptive — and what specific employee impact defines that level? Recommended: assume one level higher than instinct; layoffs are always disruptive, never high. (Hiatt, *ADKAR*, 2006 — under-rating magnitude is the largest cause of resistance.)
2. Who finds out first, and in what order? Recommended: managers 24-48 hours ahead with talking points; affected team before unaffected; never in the same meeting as the public announcement. (Prosci Best Practices in Change Management — direct manager is the most-trusted change channel; skipping this step breaks the cascade.)
3. How many touchpoints across how many channels, and which ADKAR stage does each serve? Recommended: minimum 5, target 7, across at least 3 channels, each tagged to one ADKAR stage. (Prosci research — 5-7 touchpoints is the documented floor for behavioral-change adoption.)
4. What questions will employees ask immediately, and are the answers already written? Recommended: seed the FAQ with at least 7 questions covering comp, reporting line, location, role change, timing, why now, why us — biased toward the questions you wish nobody would ask. (Edelman Trust Barometer — internal trust collapses fastest when the obvious question goes unanswered.)
5. Who is the named accountable executive on the announcement and at the town hall, and have they confirmed both? Recommended: a single named human at VP level or above, present in person or on video, not delegating to the comms team. (Kotter, *Leading Change*, 1996 — invisible sponsors trigger a Step 1 failure that collapses the rest of the model.)
6. What is deliberately not being said, and why? Recommended: surface the omissions explicitly to legal and the sponsor — the unsaid will be inferred, so it's better to know what's being inferred. (Sucher & Gupta, MIT Sloan layoffs research, 2018 — what's omitted from a layoff announcement becomes the lead narrative externally.)
7. What does success look like at 30/60/90 days, and how is it measured? Recommended: name 3 measurable signals — regrettable-attrition delta, pulse-survey trust score, manager-cascade audit results. (Hiatt, *ADKAR*, 2006 — Reinforcement is the most-skipped stage; without measurement there is no reinforcement.)