A serious organizational realignment changes more than an org chart. It changes how decisions are made, how work moves, and how people feel the impact of leadership every day. This article explains what the process is really trying to fix, which workplace skills matter most, how to handle the change in a UK setting, and what I would check before calling the new structure ready.
What matters most before you change the structure
- The best restructures solve a concrete business problem, not a vague desire to “simplify”.
- Managers need communication, coaching, and stakeholder skills before they need a new chart.
- A clear process usually beats a fast process, especially when roles and reporting lines are changing.
- In the UK, consultation rules can apply well before any dismissal letters are issued.
- Public-sector teams need extra discipline around transparency, continuity, and fairness.
What this restructure is really trying to fix
I treat any restructure as a response to a specific problem, not a design exercise. The cleanest version of it removes friction: duplicated approvals, unclear ownership, slow decisions, or a team structure that no longer matches the work.
In practice, most organisations start one because something has shifted. It may be budget pressure, a merger, a new digital system, changing demand from service users, or simply a management layer that has become too heavy for the work underneath it. A good redesign should make the organisation easier to run, not just cheaper to maintain.
The easiest mistake is to assume this is only about efficiency. Sometimes that is part of the story, but if you stop there, you usually miss the real issue. The better question is: what must change in the way work is done so the organisation can perform better without creating new bottlenecks?
- Too many handovers often signal that roles are split too finely.
- Slow decisions usually point to weak decision rights, not lazy people.
- Repeated errors can mean accountability is unclear.
- Low morale may be a symptom of constant change without enough explanation.
Once the problem is framed that clearly, the next step is to ask whether leaders have the skills to carry the change through without confusing people or damaging trust.
The workplace skills that decide whether the change works
I rarely see a restructure fail because the new boxes on the page were impossible. More often, it fails because leaders were not equipped to communicate the change, manage resistance, or translate strategy into daily work. That is why workplace skills matter so much here.
| Skill | What it looks like in practice | Why it matters |
|---|---|---|
| Strategic clarity | Explaining the reason for change in plain English | Stops rumours and keeps the team focused on the real objective |
| Communication | Sharing what is fixed, what is still under review, and when updates will come | Builds trust during uncertainty |
| Stakeholder management | Keeping staff, unions, finance, and service leads aligned | Reduces friction and prevents surprises |
| Coaching | Helping line managers answer difficult questions without improvising | Middle managers carry most of the emotional load |
| Data literacy | Using workload, demand, and span-of-control data instead of guesswork | Prevents changes based on politics or habit |
| Emotional intelligence | Noticing anxiety, fatigue, and the drop in confidence that follows change | Helps keep performance stable while the organisation adjusts |
One term I use often in this context is span of control, which simply means how many direct reports a manager has. Too wide, and managers become overloaded; too narrow, and the organisation can become slow and expensive. The right number depends on the work, not a fashionable benchmark.
I also pay close attention to decision rights, which is just a practical way of saying who decides what. If that is vague, the new structure will look tidy but still feel chaotic. Good structure is always tied to clear behaviour.
Those skills matter even more when the change moves from theory into a live transition plan, which is where most organisations either build momentum or lose it.
How I would run the process step by step
When I am thinking about a reorganisation, I do not start with the org chart. I start with the work. If the process is built around how the organisation actually operates, the structure usually follows in a more sensible way.
- Define the problem in one sentence. If you cannot say why the change is happening without jargon, the rest of the plan will wobble.
- Map the work before you redraw roles. Look at handoffs, decision points, service peaks, and the tasks that always fall between teams.
- Build the communication plan early. Staff should know what is changing, what is not changing, and when they will hear the next update.
- Design the transition, not just the destination. Interim cover, training, handover notes, and temporary reporting lines all matter.
- Review after launch. I like a 30, 60, and 90-day rhythm because issues often appear in waves, not all at once.
That kind of discipline keeps the change from becoming a one-day announcement followed by weeks of confusion. It also helps managers answer a very normal question: what do we do on Monday morning?
Once the change goes live, the real test is how it feels to the people doing the work, because a restructure is experienced through workload, meetings, approvals, and stress levels, not through a neat diagram.
What changes for people on the ground
People usually do not resist change because they love the old structure. They resist it because they can see the risks before leaders do: unclear priorities, duplicated tasks, and new managers who do not yet understand the history of the work. That is why the human side needs just as much attention as the design side.
| What you may notice | What it usually means | What to do about it |
|---|---|---|
| People keep asking who approves what | Decision rights are still unclear | Publish a simple decision map or RACI matrix |
| Managers are still doing old tasks | The role changed, but the workload did not | Remove legacy duties or add temporary cover |
| Teams duplicate work | Hand-offs were not redesigned end to end | Map the workflow and remove repeated steps |
| Morale drops after the announcement | People fear hidden cuts or loss of status | Keep briefings regular and specific |
| Service delays increase | Informal shortcuts disappeared with the old structure | Rebuild the operating process, not just the hierarchy |
A RACI matrix is simply a tool for showing who is responsible, accountable, consulted, and informed for each task. It sounds dry, but in a restructure it can save a lot of confusion.
I have seen teams become less effective not because the talent disappeared, but because nobody translated the new reporting line into practical behaviour. If people do not know where decisions live, they will keep asking around, and the organisation starts to feel slower than it was before the change.
That is one reason the legal and consultation side matters so much: if people feel shut out of the process, trust falls quickly and recovery takes longer.
The UK consultation rules you cannot treat as optional
Acas is clear that consultation should be genuine and meaningful, not a box-ticking exercise. In other words, if the decision has already been treated as final in practice, the process is already damaged.
GOV.UK says collective consultation is required when 20 or more redundancies are proposed at a single establishment within any 90-day period, and the Redundancy Payments Service must be notified at least 30 days before the first dismissal for 20 to 99 redundancies or 45 days before the first dismissal for 100 or more.
That threshold matters, but it is not the whole story. Even where collective consultation is not legally required, consultation is still a good test of whether the restructure has been thought through properly.
- Explain the rationale. People should understand why the change is being proposed.
- Consult on alternatives. That includes ways to avoid, reduce, or soften redundancies.
- Keep individual conversations going. Collective consultation does not replace one-to-one consultation.
- Document the process. Good records help show that the organisation acted fairly and consistently.
If consultation is mishandled, the risk is not only reputational. In 2026, the protective award for non-compliance can be up to 180 days' pay per affected employee, which is a serious cost for any employer and a particularly poor outcome when the change could have been managed better from the start.
For public-sector employers, this legal floor is only the beginning, because the wider expectations around transparency, fairness, and continuity are often even higher.
Why public sector teams need an extra layer of discipline
In public services, a restructure is judged against more than efficiency. People want to know whether residents, patients, students, or service users will still get a dependable service while the organisation changes. That makes the process more demanding, not less.
I would be especially careful about five things in a public-sector setting:
- Public value. Explain what improves for the people the service exists to support.
- Transparency. If updates are vague, staff will fill the gap with their own interpretation.
- Equality impact. A change can look neutral on paper and still land unevenly in practice.
- Continuity. The present still has to work while the future is being built.
- Middle-management capacity. These are the people who translate policy into day-to-day delivery, and they usually feel the strain first.
I think public-sector leaders sometimes over-focus on structure and under-focus on service flow. A cleaner chart does not automatically improve casework, response times, or collaboration. If the new model makes it harder for people to solve problems quickly, the organisation may look more modern while performing less well.
That is why I would always test the design before I sign it off.
Before you sign off the new structure, test these five things
Before any launch, I want the answers to be painfully clear. If they are not, the organisation is probably not ready yet, no matter how polished the presentation looks.
- Can every manager explain the new model in plain English? If they cannot, staff will not trust it either.
- Do people know who decides what? Ambiguous authority creates delay faster than almost anything else.
- Has the work been redesigned, not just relabelled? If the old process is still in place, the restructure is mostly cosmetic.
- Have you planned the first 90 days after launch? That is where hidden workload, confusion, and morale problems usually appear.
- Can you defend the change to staff and service users? If the rationale is weak, the structure will be hard to sustain.
If any of those answers are shaky, I would slow the rollout rather than force momentum. The best reorganisations are not the ones that look clever in a slide deck; they are the ones people can actually work inside without friction, fear, or constant clarification. That is the standard I would use every time.
