How to restructure a department

Start with the problem, not the chart

Write down what is not working and what should be true after the change. In a worked example, a Gurugram e-commerce company has one team onboarding new sellers and another supporting them afterwards. Every handoff loses information, and onboarding takes ten days. The goal: one seller team per region, owning each seller from signup to first order, with onboarding in five days. A clear problem statement stops the restructure from becoming a reshuffle of boxes around people's preferences.

Map the current state

Before designing anything, capture how the department works today: the org chart, headcount by team, spans of control, roles and what each actually does, workload, cost, open vacancies and key-person risks. Talk to a few people at each level; the real flow of work often differs from the chart. This baseline also lets you measure, three months later, whether the change worked.

Design and test options

Draft two or three options rather than one, and test each against the same questions. Choosing between options in writing makes the decision easier to explain to the people affected. It also shows leadership that the chosen design beat real alternatives, rather than being the first idea anyone had.

• Organize by function, region, customer segment or process?
• Does the option fix the problem in the statement?
• Are spans of control reasonable at every level?
• What does it cost compared with today?
• Which people or skills become a single point of failure?
• How long and how disruptive is the transition?

Handle people changes fairly

Map every person to a role in the new structure. Where duties change, explain them and offer training. Fill new roles through a fair selection among eligible people. Try redeployment first when a role disappears. If roles are cut and a worker with at least one year of continuous service is retrenched, the Industrial Relations Code requires one month's written notice with reasons, or wages in lieu, and compensation of 15 days' average pay for each completed year. See the notice and termination rules and follow your standing orders.

Communicate and put it in place

Tell people in the right order: those whose roles change or end, individually and in person; then the department; then the wider company. Share the reasons, the new structure, the timeline and whom to ask. On the effective date, update every record the same day, including departments, designations and reporting managers, and issue letters where terms change. Review after ninety days against the problem statement.

Step by step

1. Write the problem statement. Describe what is not working, the evidence, and what should be true after the change, in half a page.
2. Map the current structure. Capture headcount, roles, spans and workload. ZeniaHR's org chart shows each manager's direct and total team size, which gives a quick picture of spans.
3. Design two or three options. Draft alternatives and test each against the problem, spans, cost, key-person risk and transition effort.
4. Choose and detail the new structure. Pick one option and define every role, its reporting line, its grade and its main responsibilities.
5. Map people to roles. Assign each person to a role, plan training for changed duties, and run fair selection where several people fit one role.
6. Plan legal and pay steps. Check notice, compensation and standing orders for any role that ends, and get approvals for grade or pay changes.
7. Communicate in the right order. Meet affected people first, then the department. In ZeniaHR, post the announcement on the Company Wall to the chosen departments, with acknowledgement required.
8. Update records on the effective date. In ZeniaHR, update each person's department, designation and reporting manager on their record, then check the org chart for broken reporting lines.
9. Review after 90 days. Compare results with the problem statement, fix what is not working and close open questions from employees.

Frequently asked questions