Elizabeth CarpenterScenario
Two business units have combined after an acquisition. Employees are uncertain about leadership, roles, customer commitments, and possible workforce implications.
SELF-DIRECTED CONCEPT · DEFENSE TECHNOLOGY INTEGRATION
The First
90 Days
An executive and employee communications system designed to steady a fictional organization through integration, clarify what leaders can say, and turn employee questions into the next communication cycle.
Evidence note: This is an independent portfolio concept. The organization, scenario, dates, statements, and measures are fictional or proposed. No employer or client relationship is implied.
INTEGRATION BRIEF 01LEADERS · MANAGERS · EMPLOYEES
Stability.
Clarity.
Confidence.
90-DAY COMMUNICATIONS SYSTEM01 / 03
THE ASSIGNMENT
Communicate the integration before the information vacuum does.
Communications remit
Create one system for executive messages, manager conversations, employee guidance, escalation, listening, and measurement across the first 90 days.
Core constraint
Leaders must acknowledge uncertainty without speculating. Managers need useful guidance before employees ask them to interpret incomplete decisions.
Success definition
Employees can distinguish what is decided, what is still under review, where to find updates, and how to raise a question that receives an answer.
01 / THE SYSTEM
One message architecture. Different jobs for every channel.
The work starts with decision clarity, not volume. Executives set direction, managers create local meaning, and employee channels preserve a dependable source of truth.
State confirmed decisions and their practical effect.
Name open questions and who owns the decision.
Give a date or trigger, even when the answer is not ready.
Make the immediate next step specific and realistic.
Route questions into a visible response and content cycle.
02 / MESSAGE ARCHITECTURE
Build trust by separating fact, intent, and process.
| Message layer | What the audience needs | Proof or boundary | Immediate action |
|---|---|---|---|
| Business rationale | Why the organizations are integrating and what value the combination is intended to create. | Use approved strategic rationale. Do not imply customer or financial outcomes that have not occurred. | Leaders use the same two-sentence explanation. |
| Customer continuity | Whether teams, commitments, and points of contact change now. | Confirm only operational decisions cleared by program and customer leaders. | Customer-facing teams use an approved response path. |
| Workforce implications | What is decided about roles, reporting lines, locations, and timelines. | Separate confirmed changes from active review. Avoid reassurance that cannot be substantiated. | Employees use the FAQ and escalation route. |
| Operating model | How decisions will be made during the transition. | Name interim owners, decision dates, and exceptions. | Managers bring unresolved dependencies to the integration office. |
AUDIENCE MAP
Shared facts, tailored implications.
The center of the story stays stable. Each audience receives the detail, language, and action appropriate to its responsibilities.
Decide and model
Alignment on approved facts, decision gaps, tone, and the questions leaders should answer personally.
Interpret locally
Advance briefing, talk track, boundaries, escalation contacts, and a way to report recurring questions.
Protect delivery
Clear ownership, system or process changes, customer constraints, and where to resolve dependencies.
Understand and act
What changed, what did not, what comes next, and where the latest confirmed answer lives.
03 / WORKING SAMPLES
A coordinated set, not a series of disconnected announcements.
These sample excerpts demonstrate voice, sequencing, and the discipline to say what is known without filling gaps with speculation.
Bringing our capabilities together
Today we begin the work of bringing two business units into one operating organization. The reason is straightforward: our customers increasingly need connected capabilities, and our employees need clearer paths to bring that expertise together.
Some decisions are complete. Our current customer commitments and points of contact remain in place, and the integration leadership team is accountable for resolving cross-business dependencies. Other decisions, including parts of the long-term organization design, are still under review.
We will not ask you to rely on rumor. You will receive a weekly integration update for the next eight weeks, managers will receive briefing materials before team conversations, and the employee hub will show the latest confirmed information and open questions.
Voice: direct, measured, specific about certainty and cadence.
What we can answer today
“You should expect us to distinguish between a decision, a working assumption, and an open question. Today I will explain why we are integrating, what remains stable, and which decisions come next. If we cannot answer something yet, we will say so and tell you how the answer will be made.”
Leader cue: do not convert uncertainty into premature reassurance.
Make space for the real question
- Restate the two confirmed changes.
- Name what remains under review.
- Ask: “What would make it harder for this team to deliver during the transition?”
- Log questions, do not improvise answers.
- Commit to the next response date.
Will my role or reporting line change?
Some reporting relationships may change as the operating model is finalized. No broad workforce decision is being announced with this update. If a confirmed decision affects your role, you will hear it directly from your leader before it appears in a general update.
Escalation: Submit a question through the integration hub. Questions about an individual employment situation go to HR, not the public queue.
Say / Support / Avoid
- Say
- “The integration is intended to make cross-business delivery easier.”
- Support
- Approved operating-model decisions and named integration owners.
- Avoid
- Guaranteed savings, schedule improvements, or customer outcomes without evidence.
04 / 90-DAY CADENCE
Move from stability to informed participation.
- DAYS
0–10STABILIZE
Establish one source of truth.
Align the executive narrative, brief managers before employee release, publish a living FAQ, and open a triaged question channel.
Outputs: CEO note · town hall · manager brief · employee hub - DAYS
11–45CLARIFY
Resolve the questions that affect work.
Publish weekly decisions, equip functional leaders, track recurring concerns, and correct process friction before it becomes a trust issue.
Outputs: weekly digest · leader notes · issue matrix · office hours - DAYS
46–90BUILD CONFIDENCE
Show progress without declaring victory.
Connect decisions to employee experience, report what changed because of feedback, and transition from launch cadence to operating rhythm.
Outputs: progress story · pulse review · manager retro · next-quarter plan
05 / RUMOR AND ISSUE RESPONSE
Treat repeated questions as operational data.
RUMOR“Customer programs are being reassigned immediately.”
Check: Program leadership and customer commitments.
Response: Correct through manager brief and FAQ if false. If under review, name the decision owner and next update.
RUMOR“The new structure means broad layoffs are already decided.”
Check: HR, legal, and executive decision status.
Response: Do not speculate or offer unsupported reassurance. State only confirmed scope and the employee notification process.
ISSUEManagers are hearing news at the same time as employees.
Check: Release workflow and distribution timing.
Response: Add a protected manager briefing window and require readiness confirmation before broad release.
ISSUEThe FAQ is not answering technical delivery questions.
Check: Search terms, unanswered queue, and functional-owner coverage.
Response: Create a technical appendix, assign named owners, and publish decision timestamps.
06 / LISTENING AND MEASUREMENT
Measure whether communication reduces uncertainty and improves action.
The dashboard begins with proposed definitions, then earns targets after a baseline. Opens show reach, not understanding.
Percent selecting “confident” or “very confident” when asked if they can explain the latest confirmed decisions and escalation path.
Recurring questions divided by all categorized questions. A rising rate can indicate a discoverability or clarity problem.
Median business days from question submission to a published answer or a named next-update date.
Email delivery, opens, town-hall attendance, and hub visits. Useful for distribution checks, not proof of trust or adoption.
DECISION RULES
Let the signal change the plan.
- If manager confidence is low, pause reminder volume and improve the briefing, examples, and escalation support.
- If repeat questions rise, revise the source content and channel path before blaming attention.
- If one function reports unique friction, add a targeted working session instead of another enterprise-wide announcement.
- If no answer is available, publish the decision owner and next-update trigger.
WHAT THIS CASE SHOWS
Communication as an operating system for change.
Executive counsel, employee communication, manager enablement, governance, writing, listening, and measurement are designed together so the organization can communicate with discipline as decisions evolve.