Reorganization · Organizational Redesign
Reorganization
What is reorganization?
- Reorganization in three phases: design, announcement, settling in
- Draw decision rights before department boxes
- Tell those affected one-on-one, before the company-wide announcement
If you think of reorganization as moving boxes on an org chart, the work looks finished on announcement day. For employees, though, the reorganization starts that day, because the boss they report to, the colleagues they work with, and the criteria they are evaluated on all change. In practice, a reorganization should be viewed as three phases: design, announcement, and settling in, and most problems arise not in design but in the last two phases.
Design starts with one sentence: what problem is this reorganization meant to solve? Describe the problem concretely, such as slow decisions or customer contact points that are split across teams, then work out whether the cause is structure, people, or process. If it really is structure, map who decides what before you draw the department layout. The right span of control depends on the type of work, but once a manager has more than about 7 to 10 direct reports, one-on-ones and evaluations tend to become a formality. Concurrent roles and dual reporting lines cause the most confusion after a reorganization, so put their duration and authority in writing.
Order and speed matter in the announcement. Tell anyone whose position changes or who is giving up a title one-on-one, before the company-wide announcement. The announcement itself should cover why the reorganization is happening, what changes, what doesn't, and where people can take their questions. In the settling-in phase, use a checklist to confirm work handovers, approval lines and system permissions, and the transfer of in-progress goals and evaluation criteria, then review again at 30 and 90 days.
Reorganizations tend to go wrong when they try to solve a people problem with structure. If one leader’s capability or a conflict between two department heads is papered over with an org chart change, the problem simply moves to the new department. Frequent reorganizations are costly too. If you change the structure again before it has settled, employees stop moving, thinking “it’ll just change again anyway.” Also, transfers, job changes, or changes in working conditions that come with a reorganization can raise legal issues, so check your work rules, collective agreement, and relevant laws with your HR and labor staff in advance.
Anna ChoExpert in organizational culture, coaching, emotion management, and CS consulting
John KimInstructor John Kim, CEO of Nanum Consulting and author of B2B Marketing DesignThe idea that an organization's structure must be redrawn to fit its strategy and environment has long been a theme in organization design in management studies. The term reorganization itself has no particular originator. It became a working term through companies' regular personnel cycles and business planning.
Consider a hypothetical case. Company A, an industrial equipment maker with 520 employees, plans to replace its 3 product-based business units with 2 divisions organized by customer industry. In its reorganization two years ago, 6 team leaders learned about their moves only on the day of the company-wide announcement, and rejected approvals tripled for three months.
- The head of business administration writes the purpose of the reorganization in one sentence: "Eliminate the problem of three sales reps visiting the same customer." The team draws the decision-rights chart before the org chart.
- The HR manager calculates how many people each manager will lead in the new structure. Two teams would grow to 14 people, so they are split into sub-teams, and each of the three dual-role assignments gets a written 6-month term.
- Starting three days before the announcement, division heads meet one by one with the 11 people whose roles are changing. One team leader asks, "Who will evaluate me?" and the division head hands over the transfer criteria in writing.
- The company-wide announcement is organized as '5 things that change, 4 things that don't'. Once a question channel opens, 73 questions come in the first week, and HR posts answers within 24 hours.
- On day one of implementation, 38 approval lines and system permissions are checked against a checklist. The 126 goals in progress are handed to the new team leaders along with handover meetings.
- At the 30-day check, rejected approvals are only 1.2 times the usual level, and at the 90-day check, customers visited by more than one rep drop from 41 to 6. Two of the three concurrent roles are resolved on schedule.