Reorganizations

Idea one

The question is Monday morning

An organization can become so poorly arranged that ordinary work requires too many handovers, decisions sit with people too far from the facts, managers carry more people than they can support, and functions protect their own measures while customers experience the gaps between them. In those circumstances, changing the structure may be necessary.

But a reorganization is also one of the most tempting responses to organizational frustration because it is visible. A leader can announce new reporting lines. Teams can be moved. Titles can change. A new role can be created to "own" a problem that previously belonged to everyone and no one. The published org chart can be redrawn in a few weeks, even when the deeper problems took years to develop.

That creates a powerful impression of action. Employees see that senior leaders recognise the problem. Managers receive new responsibilities. The business can describe a clearer model to customers, investors or a board. For a period, people often feel renewed energy. The organization appears to be changing because its boxes have changed.

But the real question is not whether the chart is different. It is whether authority, decisions, information, and work will move differently on Monday morning.

A reorganization should be a response to a diagnosed structural problem, not a general expression of dissatisfaction.

Idea two

Four real triggers, each incomplete

Growth. A structure that worked with a small group of managers strains as customers, products, employees and geography increase. Informal access that once felt efficient becomes a source of inconsistency. People who know the right senior person get help quickly. People who do not know the route wait. But growth does not automatically require a reorganization. Sometimes the problem is not that teams report to the wrong leader — it is that nobody has defined who owns a decision, created an exception route, or given managers enough authority to act. The chart may change while the decision remains stuck in the same place.

Performance. Retention falls, repairs are delayed, debt rises, manual work grows. Leaders read the measures and conclude that one function is failing. Sometimes a function genuinely does have a capability problem. Yet poor performance does not prove that reporting lines are the cause. The urgent repair journey crosses Operations, the warehouse, Finance and Sales; the delay may be incomplete requests, unclear thresholds, unavailable decision-makers or missing stock information. Moving the warehouse into Operations might change who attends which meeting. It would not necessarily remove the handover that creates the waiting.

Strategy. A real change of direction can create a legitimate need to reconsider structure. But strategy is often used as a broad justification for a change that has not been made specific. Leaders say "we need to become more customer-focused," then move people into a new customer division. Customer focus does not come from placing the word "customer" on a box in the chart. It comes from deciding who owns the customer outcome, how conflicts between service speed and financial control will be resolved, what information moves across teams, and who can act when a need is urgent. If the authority and handovers are not designed carefully, the customer-facing team gains responsibility for the relationship while still depending on central functions for every important decision. The organization has then widened the authority-responsibility gap rather than closed it.

A new leader. They can see assumptions long-serving employees no longer notice. But new leaders can also mistake unfamiliarity for dysfunction. A relationship they do not yet understand may look like duplication. An informal route that appears inefficient may be compensating for a missing formal process. A role that seems unnecessary on the chart may be carrying essential coordination work. A reorganization based only on the published structure risks removing the bridges while leaving the rivers in place.

And there are less admirable triggers. A reorganization can be used to signal decisiveness after poor results, to settle political conflict by moving a contested team, to create roles for senior people, or to avoid addressing a performance issue directly. Employees usually recognize these motives quickly. They notice when the stated purpose is "faster decisions" and the design adds a management layer, when it promises empowerment but removes authority from managers closest to customers, and when leadership speaks about collaboration while creating separate targets and budgets that make collaboration harder.

Idea three

Trace the work first

Before reorganizing, leaders should trace the work.

Where does the delay begin? What decision is waiting? Who has authority to make it? What information is missing? What measure is encouraging one team to protect its local target? What workaround are experienced people using to get around the formal route?

These questions may reveal a structural issue. They may also reveal a process, policy, capacity, or leadership issue that can be repaired without moving large numbers of people.

The portal case shows why the distinction matters. Moving Customer Support from one executive to another will not solve it if Support still lacks a clear route to make manual workload visible, Product still owns priorities without agreed customer-impact thresholds, and Technology still receives incomplete information about the defect.

And a leader who has just joined should be especially careful. The published chart tells them who is supposed to report to whom. It does not tell them who actually resolves urgent credit issues after normal hours, who translates customer complaints into Product decisions, or who quietly ensures that Sales promises are understood by Operations. Follow a few decisions from notice to action before redrawing anything.

Idea four

Four myths

That changing reporting lines changes behavior. It can influence behavior — reporting lines affect priorities, escalation routes, performance conversations and the authority a manager is believed to hold. But they do not automatically change habits, incentives, systems, policies, or relationships. If account executives have learned to make commitments before checking operational capacity, moving Sales into a customer division will not change that habit unless decision rights, measures, and expectations also change.

That fewer layers always mean faster decisions. Sometimes they do. But removing layers can also create managers with spans too wide to support their teams, make decisions, or notice emerging problems. A manager responsible for too many people may become a forwarding point rather than a source of judgment. Employees gain a shorter route on paper and lose access to coaching, context and timely decisions in practice. The relevant question is not how many layers there are. It is whether each layer adds necessary authority, coordination, capability, or control.

That putting related teams together solves coordination. It may help. But coordination is still needed wherever work crosses expertise, systems, or decisions. Putting Support, Sales and Operations under one executive does not remove the need to coordinate with Finance on credit risk or Technology on portal reliability. It may simply move the most difficult boundary somewhere else. Every structure creates boundaries. The task is not to eliminate them all. It is to make the necessary boundaries workable.

And that the reorganization is the change. It is not. The announcement is the beginning of a period in which people must learn new responsibilities, relationships, decision routes, measures and ways of handling exceptions. If those things are not made explicit, employees will continue to use the old informal organization because it is the only route they trust.

A reorganization can be necessary. But it should never be confused with a solution in itself. The chart can be redrawn quickly. The real organization changes only when work begins to move differently.

Idea five

Which difficulties you would rather carry

Every reorganization contains a trade. A structure is changed because the current arrangement made one problem too difficult to manage. The new structure is designed to correct it — but correcting it changes the balance of authority, information, control and coordination. The problem that was most visible may improve. Another problem, previously less important or less visible, becomes more significant.

This does not mean reorganizations always fail. It means they should be judged honestly. A reorganization is not a move from a bad structure to a perfect one. It is a decision about which difficulties the organization is better equipped to carry.

Create a customer division and the divisional leader can finally see the service failure, the customer risk and the commercial consequence together. But Finance, Technology and company-wide standards have not gone anywhere. The division wants freedom to approve urgent exceptions because it is judged on retention; Finance worries that local pressure will produce inconsistent decisions and growing exposure. The reorganization solved one problem and created another: the company now needs stronger mechanisms for common controls, shared resources and comparing performance across divisions.

And if those mechanisms are not designed deliberately, central functions pull authority back. Finance requires more approvals. Technology insists everything returns to a central roadmap. The organization then drifts toward the arrangement it was trying to escape, but with added frustration on both sides. Divisional leaders say "we have accountability without authority." Central leaders say "the divisions want freedom without discipline." Both may be partly right.

Centralizing runs the same course in reverse. Consistency, common training, shared standards and finally seeing the true volume of manual work — all real gains. But centralization also creates distance. A customer who previously spoke to someone familiar with their equipment, contract and recent repair now enters a standard queue and repeats information the company already holds. The central team may meet its call-response target while customers experience a less informed and less personal service. Again, the new problem is not evidence that centralizing was wrong. It is the cost of the improvement that was chosen.

Every structure asks an organization to choose what it will make easier and what it will need to manage more carefully.