Write a change story that gives people a usable explanation

A change story is a concise, connected explanation of why a change is happening, what it means for people and what they can do next. It should also distinguish decisions from proposals and known consequences from uncertainties. A reader should leave able to locate their own work in the explanation and recognise where questions remain open.

The story is one part of a change communication plan. The plan organises audiences, channels, timing and feedback; the story connects the essential facts. A compelling paragraph cannot resolve an unclear decision, supply missing resources or make an unfair arrangement acceptable.

There is no single standardised change-story formula used here. This guide offers an original drafting and checking process. Its aim is a credible explanation that can survive practical questions, rather than a motivational script that depends on everybody sharing the same feelings about the change.

Decide what the explanation must help someone do

Begin with the reader’s next situation. A coordinator might need to explain a changed booking rule. A manager might need to discuss workload with a team. A colleague might need to decide whether to volunteer for a trial. These require different detail, even when the underlying decision is the same.

The government OASIS planning framework starts with objectives and audience insight and links communications to evaluation. Adapt that principle by writing a modest objective: “colleagues can explain why reservations will be handled differently and which choices remain open.” Avoid treating approval of the message as the objective.

Define the boundary of the communication. Is the organisation announcing a decision, consulting about options or asking people to help design implementation? If the core decision has already been made, do not use “help shape the future” to imply that it is still open. State which implementation choices can change.

A story needs enough evidence to explain the reason. If the reason is a leadership preference or a budget decision, name it accurately. Do not invent an external crisis to make an optional choice appear inevitable. Questions about necessity belong in the decision discussion, not in the editing margin.

Gather the facts and consequences first

Consider a hypothetical public library introducing a common process for book reservations across three branches. Today, each branch keeps its own collection list. Staff sometimes have to contact another branch to find out whether a reserved book is ready. The proposed trial changes how a reservation is recorded and who confirms collection.

Before drafting, verify the decision, the reason, the trial boundary, the responsible roles and the review date. Ask whether extra work has been assigned, which existing routine will end and what happens when a colleague is absent. The writer should not fill these gaps with imagined answers.

Talk with desk staff, collection staff and the colleague coordinating transfers between branches. Use stakeholder mapping to find affected groups, then check their actual concerns. A job title alone does not reveal whether someone works evenings, uses a shared terminal or supports visitors who need another format.

In the invented library, desk staff ask whether they will have to update two lists. Collection staff ask who marks a book ready after it arrives late. Volunteers ask how they will find a current instruction between weekly shifts. Those are consequences the story must acknowledge, even if some answers are pending.

Check operational questions through change readiness. If there is no agreed owner for a late-arriving reservation, the explanation can identify that uncertainty, but an operational decision is still required. A polished story should never hide a missing arrangement.

Build a short common core

Draft the common explanation in five connected parts. Start with the concrete issue; describe the decision and its intended outcome; explain the work that changes; acknowledge costs and unresolved questions; finish with the next action and update. This sequence is a writing aid, not a validated persuasion technique.

Use the following worksheet before writing the paragraph:

Part	Question to answer	Library example
Reason	What problem or decision explains the change?	Branch lists do not provide a shared reservation status
Direction	What has been decided, and what is intended?	Trial one common reservation record at two branches
Consequence	What will this audience do differently?	Record readiness once and use the agreed transfer handoff
Uncertainty	What is unresolved, and who will resolve it?	Collection owner for late arrivals; service manager to confirm
Next step	What should people do now, and when will they hear more?	Rehearse a case; return questions before the trial review

Be careful with tense. “The process will reduce waiting” presents an uncertain benefit as a prediction. “The trial will examine whether a shared status reduces avoidable enquiries” states the purpose. If the team has measured the current problem, describe the measure and its boundary accurately. Otherwise, use the verified qualitative evidence.

Keep the story short enough to retell, with a longer reference for precise instructions. A colleague should not have to memorise a speech to answer an ordinary question. The story should point to the current decision and support records when detail matters.

A hypothetical library change story

For the invented library, a first usable draft might read:

“Our separate branch lists make it difficult to confirm whether a reserved book is ready at another location. We will trial a shared reservation record in two branches for three weeks. During the trial, desk and collection staff will use one agreed status and handoff, with supported practice before the first shift. We are still deciding who covers late arrivals and how volunteers will access the current instruction. The service manager will confirm those arrangements before the trial begins. Bring a reservation case to the rehearsal, and tell us where the proposed handoff would create extra work. We will publish the review and the decision about expansion afterwards.”

This is a fictional draft, not a message from a real library. It avoids promising that every shift will become easier. It also exposes two prerequisites that must be resolved before the described trial is credible.

Suppose a volunteer asks whether “one agreed status” means they now have authority to release a book without the usual checks. That is a useful misunderstanding to discover during preparation. The team should add the relevant role boundary to the reference, and clarify it in the version used for volunteers.

If the change is being developed through Lean Change experiments, name the experiment as an experiment. People need to know whether they are rehearsing a proposal, testing an approved variation or adopting a settled rule. Keeping those states visible helps the story remain accurate as the work changes.

Adapt the consequences while keeping the facts consistent

Use one fact base and several audience-specific explanations. Desk staff need the collection conversation and exception route. Collection staff need the physical transfer and responsibility for updates. Managers need to understand what the status record can support and what it cannot establish about performance.

Avoid altering the reason to suit what a group wants to hear. Telling managers that the purpose is tighter performance control while telling employees that the purpose is solely to reduce administration creates contradictory accounts. If a change has several purposes, name the relevant ones and the tensions between them.

The government inclusive communications template recommends planning for different audience needs and involving those audiences early. In this workplace adaptation, test whether people can access the explanation during their ordinary work. A recording needs captions; a reference needs readable structure; a briefing needs a route for a colleague who cannot attend.

For the hypothetical library, the common story appears in a short written reference. A shift conversation adds two actual role scenarios. A colleague returning after leave receives the current version and a practice opportunity. These are delivery choices, not assumptions that everyone learns best in a particular medium.

Check understanding without demanding agreement

Read the draft with a small mix of affected colleagues. Ask them to explain the intended change in their own words and identify what they would do next. Invite the difficult question: “What does this explanation leave you unsure about?” Use systemic questions when different groups interpret the same consequence differently.

Check four things separately: factual accuracy, understandable meaning, practical usefulness and credibility. A clear message can still describe an arrangement someone reasonably opposes. Do not rewrite disagreement as a comprehension problem or count a polite response as support.

CIPD’s employee-voice factsheet connects voice with expressing views and influencing matters affecting work. A useful story therefore includes a response route with an owner. Tell people what can change following their input and how they will hear the result. A generic invitation to “share feedback” is too vague if nobody can respond.

Discuss especially sensitive consequences through an appropriate confidential channel. A group briefing should not pressure a colleague to reveal a personal concern. When trust or interpersonal risk affects participation, consider the conditions described in the psychological-safety guide, rather than assuming an inviting tone makes the conversation safe.

Keep uncertainties, corrections and commitments visible

Give the explanation a date, an owner and a location for the current version. Record unresolved questions with a next update. If an answer changes, correct it where the earlier answer circulated; quietly replacing a document leaves people with conflicting memories and copies.

In the library example, the manager might commit to reviewing the late-arrival handoff by Thursday. That is a commitment to an answer or a documented status, not a guarantee that the preferred solution will be available. The story should state what happened when the commitment is reviewed.

Use change contracting to make consequential promises reviewable. “We will support you” becomes useful when someone names the support, the available time and the owner. If a promise depends on budget approval, describe that dependency rather than presenting it as secured.

Monitor reach, understanding and subsequent use separately. The government Evaluation Cycle distinguishes communications outputs, audience perceptions, behaviour and wider impact. Here, an email opening is evidence of neither a correct handoff nor acceptance of the decision. Observe the relevant task and ask about remaining uncertainty.

If a new software rollout reveals that access or workflow is still wrong, amend the operational plan and the story together. Sending the same explanation more frequently will not resolve a mismatch between the message and the available work arrangements.

Evidence and limits of a change story

The institutional sources support communications planning, audience inclusion, voice and evaluation. They do not validate this five-part worksheet as a distinct model or establish that a particular story causes successful organisational change. The library example, testing prompts and drafting sequence are original practical guidance.

A story can make reasoning and consequences easier to examine. It cannot remove a real loss, supply decision authority or substitute for consultation that is needed. If the underlying choice is uncertain, expose that uncertainty and take it to the responsible decision process.

Avoid a heroic narrative in which leadership understands the future and everyone else merely needs to catch up. Include what the organisation has learned, what remains contested and what affected colleagues can influence. A useful explanation remains open to correction because it is tied to the work, its evidence and actual commitments.