Planning an Organisational Restructure: A Step-by-Step Guide

Step 1: Define the problem, not the solution

Restructures often start with a picture of the answer: fewer layers, a new division, a merged team. Start instead with a clear statement of what is not working. Slow decisions, unclear ownership of a product, duplicated work, managers with too many or too few reports and rising costs are all legitimate reasons, but each points to a different fix.

Write the problem down in two or three sentences and agree it with the leadership team. Every later design option should be tested against that statement.

Step 2: Map the current structure accurately

You cannot redesign what you cannot see. Build an up-to-date chart of the current organisation, including vacancies, contractors and people who informally report to more than one manager. HR records are a starting point, but line managers usually know about changes that have not reached the system yet.

Importing your staff list from a spreadsheet is the quickest way to start. Once the current chart is complete, look for warning signs such as very wide or very narrow spans of control, single points of failure, unclear reporting lines and teams that sit in the wrong part of the business.

Step 3: Set design principles

Before drawing anything new, agree a short list of principles that the new structure must respect. They give you an objective way to compare options and make it easier to explain decisions later.

• Each outcome or product has one accountable owner.
• Managers have a workable span of control for the type of work.
• Decision rights sit as close to the customer as is safe.
• Specialist skills are shared where duplication would be wasteful.
• The structure can absorb planned growth without another redesign.

Step 4: Develop and compare options

Draft two or three realistic alternatives rather than a single preferred design. For each option, produce an org chart and a short note covering cost, risk, the roles affected and how well it scores against the design principles. Seeing options side by side helps leaders discuss trade-offs rather than defend a single plan.

Keep early drafts confidential. Org charts that circulate before decisions are made can cause anxiety and rumours, so limit access to the people doing the design work.

Step 5: Check legal and consultation requirements

If the restructure changes roles, terms or headcount, employment law in your country may require formal consultation with affected staff or their representatives, fair selection criteria and specific notice periods. The rules vary by jurisdiction and by the number of people affected, so take advice from HR and qualified employment lawyers before announcing anything.

Build the required consultation time into your timeline from the start. Rushing this stage is one of the most common and costly mistakes.

Step 6: Plan the communication

People hear about a restructure first through the way it is announced. Plan who hears what, in what order and from whom. Affected individuals should hear directly from their manager or a senior leader, privately, before any general announcement.

• Explain the problem being solved, not only the new boxes.
• Show the new org chart so people can see where they fit.
• Give clear dates for each stage and what happens next.
• Provide a named contact for questions and support.
• Brief managers in advance so they can answer their teams consistently.

Step 7: Implement and review

Once decisions are final, publish the new org chart and keep it current. Update systems, approval limits, job descriptions and team meetings to match the new structure; a chart that does not match how work really flows quickly loses credibility.

Schedule a review three to six months later. Revisit the original problem statement and ask whether it has been solved. Small adjustments at that point are normal and much cheaper than another full restructure.

Common mistakes to avoid

Most restructures that fail do so for predictable reasons: designing around current personalities instead of future needs, changing structure when the real issue is process or leadership, underestimating the time needed for consultation, and announcing changes before the details are ready.

The dial369 designer helps you avoid several of these. You can keep the current chart and each proposed option as separate saved versions, compare them in portrait or landscape, and export polished PDFs or PowerPoint slides for leadership meetings. Because the work happens in your browser rather than on a shared server, sensitive drafts stay private until you are ready to share them.