Skip to main content
Steady at the Top
← All articles

How to explain company change so people know what to do

Explain company change by stating the problem, the evidence behind the decision, and what employees must do differently. Distinguish decisions already made from choices still open. Give each affected group a usable next action and a named route for questions you cannot yet answer.

A work-implication change story is a practical explanation that connects a business problem and leadership decision to changes in everyday work. It is a working term grounded in Daft and Lengel’s (1986) distinction between missing information and unclear interpretation in organizational information processing. The framework is a management method, not a validated measure of communication effectiveness.

A change story explains why a decision makes sense and what follows from it. An implementation plan assigns work, dates, and resources. One cannot substitute for the other. A persuasive account without an operating plan leaves employees informed about ambition but uncertain about action.

Begin with the employee’s practical question

Employees in different roles may hear the same announcement and need different answers. A manager needs to know what to tell the team. A customer-facing employee needs to know which commitments remain valid. A specialist needs to know whether priorities or decision authority changed.

Start with those work questions before choosing a slogan or presentation design. Ask which task, promise, or decision becomes different after the announcement. If no one can name the change, the story may be too abstract or the decision may not be ready to announce as an implementation.

Industrial/organizational psychology is the psychology of work and organizations. Its research can inform how leaders understand employee reactions, while the company’s own evidence must establish the case for this change. Do not use psychology language to make an uncertain business choice sound inevitable.

Use How CEOs can build motivation that survives hard quarters for the broader motivation context. Employees need more than a reason to agree. They need a workable role in the decision’s implementation, with appropriate support and a way to raise problems.

The work-implication change story method

1. State the problem in verifiable terms

Describe the condition leadership is trying to change. Use current customer evidence, operating constraints, or strategic facts that you can support. Avoid vague claims that the company must become more agile or innovative without explaining the business consequence.

Separate observation from interpretation. “Customers wait across several handoffs” is an observation when the workflow record supports it. “Our structure is the main cause” is an interpretation that requires further reasoning. State the connection rather than blending the two.

Tell employees why the problem matters now. The timing may reflect a commitment, new evidence, or a decision point. Do not invent urgency merely to discourage questions. A real deadline should have a source and a clear relationship to the work.

Keep sensitive information within appropriate boundaries. You can explain the operating problem without revealing private personnel details or restricted commercial information. Use the relevant specialists to determine what can be shared accurately with each audience.

2. Explain the decision and the alternatives considered

State what leadership chose in direct language. Explain the main tradeoff and why the selected option fits the current evidence. You do not need to reproduce every meeting, but employees should understand the reasoning that links problem and action.

Name the meaningful alternative you rejected where useful. Explain its cost or limitation without caricaturing it. Employees may have supported that alternative, and an accurate account helps them understand why leadership reached a different conclusion.

Avoid rewriting prior decisions as obviously foolish. The earlier plan may have been reasonable under earlier information. If leadership made an error, own the specific error rather than turning it into a story about unnamed people resisting progress.

State the uncertainty that remains. A decision can be necessary without guaranteeing the outcome. Explain what evidence would lead leadership to adjust implementation or reconsider an assumption. That boundary gives employees a more accurate account of the commitment.

3. Translate the decision by audience

For each affected group, identify what starts, what stops, and who owns the next decision. Use the actual work. A finance team may change approval thresholds while an account team changes how it confirms delivery commitments.

State what remains in force where confusion would otherwise create risk. If current customer agreements still apply, say so after verification. If reporting arrangements remain temporary, name the interim owner and the point when the next decision will be communicated.

Do not ask every manager to invent the implications independently. Give managers the common facts and decision boundaries, then help them translate those facts for their teams. Differences in examples are useful. Contradictions in the underlying decision are not.

Where an implication is unresolved, label it and assign an owner. “We have not decided this part” can be a useful answer when followed by the process and next update. A vague promise of more details soon leaves employees unable to plan.

4. Create a route for useful challenge

Ask what the story may have missed about implementation. Invite evidence about conflicting commitments, missing access, or unintended effects. Do not define every objection as resistance before hearing the work problem it may identify.

Morrison’s 2014 review examines employees choosing to share or withhold upward input. Make the route clear: where to raise an issue, who reviews it, and how the response returns to employees.

Use Why employees resist change that leaders think is obvious to distinguish different sources of resistance. A person who doubts the evidence needs a different response from someone who lacks the capacity to implement. The story should help clarify the issue, not become a script for dismissing it.

Explain what feedback can change. The strategic decision may be fixed while sequencing, tools, and work allocation remain open. Employees should not spend time debating a closed choice under the impression that leadership requested their input on it.

5. Return with evidence from implementation

Choose the next update around an operating event, not only a communication calendar. Explain what happened, what leadership learned, and what changes follow. Keep the original rationale available so the story does not drift as circumstances change.

Kramer’s 1999 review examines barriers to sustaining organizational trust. In this method, follow-through is inspectable. Employees should be able to see whether the announced authority, support, and review process exist in practice.

Correct inaccurate statements directly. Say what changed and why. Do not quietly replace the original wording while implying that employees misunderstood it. A clear correction preserves a usable record of the decision and its current implications.

Use What to say when employees ask questions you cannot answer for uncertainty that remains. The story does not need a confident answer to every future question. It needs an accurate account of what is known and a dependable process for resolving the rest.

A hypothetical change story

A company moves from separate regional service teams to a shared operating model. The evidence shows inconsistent exception decisions and duplicated reporting. Leadership chooses shared decision rules while keeping local customer ownership.

The story explains that the company rejected complete centralization because local account context still matters. It states which exceptions now use the shared approval route and which decisions remain with regional owners. Managers receive examples from current work.

An unresolved issue concerns support coverage across schedules. Leadership names an owner and a review point rather than claiming the design is finished. Employees can raise specific coverage problems through the implementation channel.

This hypothetical example illustrates the structure of the explanation. It does not establish that a shared model is appropriate for your company. The business evidence and operating consequences must justify your own choice.

The private-life composite

A founder rehearses a company-wide change message at home. The presentation explains the market and leadership’s ambition, but their partner asks what a manager should do differently the next morning. The founder cannot answer without opening another document.

This composite shows where the story needs work. The strategic rationale may be sound, yet the practical implication remains buried. Add the next action, decision owner, and unresolved question to the message before asking employees to carry it forward.

If stress symptoms persist or affect daily life, consult a licensed clinician. The communication task is to reduce avoidable ambiguity through accurate work guidance. It is not a treatment for the private pressure carried by the CEO or employees.

Test comprehension before calling the message complete

Ask a small set of affected employees to explain the change in their own words. They should be able to name the problem, the chosen action, and the practical difference in their role. Treat a mismatch as information about the message or the plan.

Avoid asking whether they liked the presentation as the main test. Agreement, comprehension, and ability to implement are separate. An employee can understand the decision and still disagree with its tradeoff. Another can agree while lacking the information needed to act.

Use How to address workplace rumors without spreading them when rumors reveal unanswered questions. Do not respond to every circulating claim through the main story. Address the consequential gap and keep the reliable source of current information easy to find.

Keep specialized announcements in their proper processes. Personnel decisions, legal notices, and customer commitments need the appropriate private or formal channels. The general change story should connect those processes without disclosing information that does not belong in a broad message.

The explanation is ready when the next action is clear enough to perform and the remaining uncertainty has an owner. Then let employees inspect the implementation. A credible story stays connected to the work it asks people to do.

Keep an accountable owner for the published explanation. When implementation changes, that person should update the current work guidance and tell affected managers what changed. The archive should preserve earlier decisions without leaving obsolete instructions looking current.

Sources

Steady at the Top