Organisational Redesign Process: 7 Steps
Most organisational redesigns are restructures with a better name. The boxes move, the reporting lines are redrawn, a consultation runs its course, and six months later the same work is being done in the same way by fewer or differently titled people. The board paid for a new organisation and received a new org chart.
What is an organisational redesign process? An organisational redesign process is the structured sequence of steps an organisation follows to change how its work, decisions and roles are organised, from agreeing why change is needed to embedding the new structure after go-live.
Done properly, it is different from a restructure. It starts with what the organisation has to be able to do, uses the principles of organisational design to decide how work and decisions should flow, and only then draws the structure. It also treats the parts most programmes rush, consultation, transition and the first ninety days, as design work rather than administration. This guide sets out the seven steps we use to take a redesign from board mandate to a stable organisation that works differently, and the points where most redesigns go wrong.
Redesign or restructure: is structure really the problem?
The first question is whether structure is the problem at all. Boards reach for a restructure because the org chart is the most visible part of the organisation and the easiest to change. But slow decisions, duplicated effort and rising cost are more often caused by unclear decision rights, failure demand created upstream, or processes that were never designed end to end. Moving the boxes leaves all three in place.
That is why a redesign should follow diagnosis, not replace it. Our Five Lens Function Review sets out how to read purpose, demand, work, capability and cost before anyone draws a structure. If you are changing process, technology and governance at the same time, the organisation is one layer of a wider target operating model, and it should be designed as part of it.
This guide picks up from the point where the evidence says the structure itself has to change.
The seven-step organisational redesign process
1. Mandate and case for change
Every redesign needs a written mandate before any design work starts. It should state the two or three outcomes the new organisation must deliver, what is in and out of scope, what has already been decided, and how success will be measured twelve months after go-live. It should also name the sponsor who will own the decisions when they become contested, because they will.
The business case belongs here too. It should set the cost of the current organisation against the expected cost and benefit of the new one, including the one-off costs most cases leave out: consultation time, redundancy and relocation costs, backfill, lost productivity during transition, and the management attention the exercise will consume. A case that only works without those costs is not a case.
2. Design principles
Design principles are the rules the new organisation must follow. They are agreed by the executive before any options are drawn, and every option is tested against them. Good organisation design principles are specific enough to rule options out. "Customer focused" rules nothing out. "Decisions on pricing below £50,000 are taken within the business unit" does.
| Principle | What it tests |
|---|---|
| Organise around the customer or value stream, not the function | Does work cross fewer handoffs than today? |
| Decisions are taken as close to the work as the risk allows | How many decisions still escalate to the executive? |
| One accountable owner for every outcome | Can every KPI be traced to a single named role? |
| Spans and layers set by the work, not by grade | Are there layers that exist only to manage the layer below? |
| Standardise by default, vary by exception | Is every local variation justified by a genuine customer or regulatory need? |
| Design for the capability needed in three years | Does the design depend on skills the organisation does not have and has no plan to build? |
| Affordable within the agreed cost envelope | Does the fully costed structure sit within the business case? |
Seven principles is usually enough. Beyond ten, they start to contradict each other and stop doing their job.
3. Shape: spans, layers and decision rights
The shape of an organisation is its spans of control (how many people report to each manager) and its layers (how many levels sit between the chief executive and the front line). A spans and layers baseline is one of the most revealing pieces of analysis in any redesign. It routinely finds managers with one or two direct reports, layers that exist to relay information rather than add judgement, and pockets of the business where a manager has twenty reports and no time to lead any of them.
There is no universally correct span. Highly standardised work can support wide spans; complex, specialist or high-risk work needs narrower ones. The point of the analysis is not to hit a benchmark but to ask of every layer what decision it exists to take.
That is why decision rights come before the lines on the chart. Agree who decides what, at what threshold, before drawing the structure. If decision rights do not move, the new organisation will reproduce the old one's behaviour, whatever the chart says.
4. Detailed design: roles, role mapping and cost
Detailed design turns the shape into roles. Each role needs a clear purpose, its accountabilities, its decision rights, the capabilities it requires, and where it sits in the grading structure. Then comes role mapping: setting every current role against the new structure and deciding whether it is unchanged, changed, new or removed. Role mapping is where the human impact becomes visible, and it should be done carefully and confidentially, because it drives both the consultation and the selection process that follow.
The final part of detailed design is the fully costed structure, set against the baseline and the business case. This is also the moment to test the design against the principles from step two. If the structure only works because of who currently holds certain roles, it has been designed around people rather than work, and it will fail when those people move on.
5. Consultation and the legal process
In the UK, a redesign that affects jobs is also a legal process, and the timetable has to be built around it rather than squeezed into it. Where an employer proposes 20 or more redundancies at one establishment within 90 days, collective consultation with employee representatives is required: at least 30 days before the first dismissal for 20 to 99 proposed redundancies, and 45 days for 100 or more. The Secretary of State must be notified on Form HR1.
The Employment Rights Act 2025 raises the stakes. From 6 April 2026, the maximum protective award for failing to consult properly doubled from 90 to 180 days' pay per affected employee. The Act also adds a second, organisation-wide trigger for collective consultation, based on proposed redundancies across all sites, and the government has consulted on where to set it. Boards should take specific employment law advice on the current position before fixing any timetable.
Consultation also has a design purpose. It must be genuine, which means the proposals must still be open to change, and it is often where the people who do the work point out the flaw the design team missed. Organisations that treat consultation as a formality lose that insight and usually end up paying for it after go-live.
6. Selection and transition
Once the structure is confirmed, people are appointed to it through a fair, documented selection process: ring-fenced pools, clear criteria tied to the role design, and an appeals route. This is also where the organisation either keeps or loses the people it most needs. Strong performers with options leave during uncertainty, so the time between announcement and appointment should be as short as a fair process allows.
Transition is the step most redesigns under-plan. Work does not move with a letter of appointment. For every changed or removed role, someone needs to know which activities are moving, to whom, with what knowledge and by when. Service levels should be protected by a clear cut-over plan, with named owners for any work at risk of falling between the old structure and the new one.
7. Stabilise, measure and embed
Go-live is the start of the new organisation, not the end of the redesign. Plan a stabilisation period of around ninety days, with a short weekly review of what is working, what is stuck and which decisions are still escalating out of habit. Measure against the success measures in the mandate, not against the delivery plan. The most telling indicator is usually decision speed: whether decisions that used to take weeks now take days.
This is where the Embedded Change Model™ earns its place. A redesign that the organisation has helped shape, and whose managers can explain the reasoning behind it, holds after the advisers leave. One that has been done to the organisation tends to drift back towards the old shape within a year, one exception at a time.
Where AI changes the redesign conversation
AI is now one of the most common reasons boards give for an organisational redesign, and one of the most common reasons redesigns go wrong. The mistake is to start with headcount: to estimate the roles AI might replace and draw a smaller structure around the estimate.
The better sequence is to redesign the work first. Look at tasks, not roles: which tasks AI can take on reliably, which it can support, and which still need human judgement. Only then ask what that means for roles, spans and layers. Most roles change shape rather than disappear, and the capability the new organisation needs, people who can supervise, question and improve AI-assisted work, rarely exists in the current structure. Our view on why AI pilots succeed and rollouts stall applies here: the organisation has to be ready for the change, not just the technology.
Five ways organisational redesigns fail
- Structure first. The org chart is drawn before the principles and decision rights are agreed, so the exercise becomes a reorganisation of the existing problems.
- Sized to a savings number. A target is set, a structure is drawn to meet it, and the rationale is written afterwards. Staff recognise the pattern and resist it, and the savings rarely hold.
- Designed around current post-holders. Roles are shaped to fit individuals rather than work, and the design breaks as soon as those individuals leave.
- Consultation underestimated. The timetable assumes consultation is a formality, then slips when it is not, and the organisation sits in uncertainty for months.
- Success declared at go-live. Nobody owns the first ninety days, old decision paths quietly return, and within a year the new organisation behaves like the old one.
When to bring in an independent organisation design consultant
Many organisations can run a redesign with their own HR and leadership teams. Independent support adds most value in three situations: when the executive team is too close to the current structure to challenge it, when the redesign has to be defended to a board or investor, and when the organisation wants a method it can reuse rather than a one-off report.
Independence matters here more than in most consulting work. An adviser with a technology platform to sell or an implementation practice to fill has a stake in the answer. Intology has neither, so our challenge is about whether the design will work, not what follows it. We bring the method, the evidence and the independent challenge, and we hand over the tools so your team can run the next redesign itself. More on that approach in team augmentation versus embedded change, and on our operating model redesign service.
Frequently asked questions
What are the steps in an organisational redesign process?
Seven steps: agree the mandate and case for change; set design principles; define the shape through spans, layers and decision rights; complete the detailed design of roles, role mapping and cost; run consultation and the legal process; select people and manage the transition; then stabilise, measure and embed the new organisation.
What is the difference between organisational redesign and restructuring?
Restructuring changes reporting lines and roles. Organisational redesign changes how work and decisions flow, and then sets the structure to support that. A restructure can be part of a redesign, but a restructure on its own usually moves existing problems into new boxes.
How long does an organisational redesign take?
For a single function or a mid-sized business, design typically takes eight to twelve weeks, followed by consultation, selection and transition, which can take another three to six months depending on the number of people affected and the consultation required. Allow a further ninety days after go-live for stabilisation.
Do we have to consult staff on an organisational redesign in the UK?
If the redesign could lead to redundancies, yes. Individual consultation is expected for any fair redundancy process, and collective consultation applies where 20 or more redundancies are proposed at one establishment within 90 days, with a new organisation-wide trigger introduced by the Employment Rights Act 2025. Take employment law advice before setting a timetable.
How do you build the business case for an organisational restructure?
Set the fully costed current organisation against the fully costed new one, then add the one-off costs of change: consultation, redundancy and relocation, backfill, lost productivity during transition and management time. Tie the benefits to the outcomes in the mandate, not to headcount alone, and name who will be accountable for delivering them.
Talk to us
If you are planning an organisational redesign and want it to change how the business works rather than just how the chart looks, arrange a confidential conversation with a senior Intology consultant.