I've been on the receiving end of a restructure. The reasons were the usual ones: profits too low, cost of sales too high, not enough left over to cover the overheads. At the start, I understood. I even agreed. It's business, and sometimes the numbers force hard decisions.
That understanding didn't survive the process. Not because the decisions got worse, but because the communication did. Reasons grew vague. Updates stopped. Rumours did what rumours do in a vacuum. The only substantial written communication anyone remembers from that period was a short email noting that pay reviews were off the table for the foreseeable future. People with young families, mortgages and cost-of-living pressure were left to fill the silence with their worst guesses.
Here's what that experience taught me, talking afterwards with people both directly and indirectly affected: almost nobody was angry about the restructure itself. They were angry about not being told things, clearly, in writing, when it mattered.
Why writing, specifically
Restructure announcements are usually delivered in meetings, and meetings are the right place for the human moment: faces, questions, acknowledgement. But meetings evaporate. People in shock retain very little, and the ones not in the room get the story second-hand. Within a day, five people have five versions.
Written communication does what the meeting can't:
- It gives people something to re-read at 11pm when the anxiety hits, instead of their imagination.
- It keeps every team working from the same facts.
- It creates a record of what was actually said, which protects staff and leadership alike.
- It forces precision on the leadership team. Vague intentions survive in a meeting. They collapse on a page, which is exactly why writing them down early is so valuable.
The trust deficit you're working against is real: Gallup finds only 13% of employees strongly agree their leadership communicates effectively with the rest of the organisation, and that's in ordinary times. A restructure is the worst possible moment to discover your organisation has no habit of writing clearly to its people.
The evidence: communication determines what survives the restructure
The people who stay are watching how the people who leave are treated. A study of 4,172 workers across 318 companies that had recently made layoffs found 74% of surviving employees said their own productivity had declined, and 87% were less likely to recommend their organisation as a place to work.
But the same research contains the finding that should be pinned to every executive's wall: survivors who rated their managers as visible, approachable and candid were 72% less likely to report a productivity drop. The restructure didn't decide the outcome. The communication did.
What New Zealand law already expects
In New Zealand this isn't only good practice. The duty of good faith makes genuine consultation a legal requirement. Employment New Zealand's guidance sets out the shape: explain the proposed change and the reasons for it, give employees a reasonable time to consider the proposal and seek advice, genuinely consider their feedback, and tell them what was accepted or rejected and why, all before the decision is final.
Read that list again and notice what it actually is: a writing brief. A proposal document, a feedback process, a decisions document with reasons. Organisations that treat consultation as a legal hoop produce murky documents that inflame exactly the anxieties they're meant to settle. Organisations that treat it as communication produce documents people can actually use to make decisions about their own lives.
What to put in writing, at each stage
At announcement. A written summary of the proposal in plain language: what is changing, what is not changing, the genuine reasons, the timeline, and what happens next. Name the hard parts plainly. "Some roles are proposed to be disestablished" buried in paragraph six fools nobody and insults everybody. Include where to go with questions, and what support is available: EAP, union contacts, someone whose actual job is to answer.
During consultation. Regular written updates on a stated rhythm, even when the update is "no decisions yet, and here's where the process is." A promised fortnightly update that arrives is worth more to trust than any wording inside it. Silence is never neutral: people read it as bad news being hidden, and they are sometimes right.
At decision. The outcome, the reasons, and an honest account of what the feedback changed. If feedback changed nothing, say so and say why. Pretending consultation shaped a pre-made decision is the fastest way to poison the next one.
Afterwards. This is the forgotten stage. The people who remain need written clarity about new structures, new reporting lines, and what their own roles now look like. The "survivors" are deciding whether to stay. Write to them like it matters, because it does.
The standard to hold every document to
One test covers it all: could an anxious person, reading this at home, answer the three questions they actually have? What is happening? Why? What does it mean for me? If a document doesn't answer those, it isn't communication. It's administration.
Empathy, in restructure writing, isn't a soft tone. It's precision: telling people what you know, when you know it, in language that doesn't require a second read at the worst moment of their working year.
It's a hard thing to write well, and leadership teams are usually at their busiest and most depleted exactly when it's needed. If you're heading into a workplace change and want the communication to be something your people respect you for afterwards, we can help you get it right.