How to Reorganize Without Losing a Year

Reorganizations are among the most expensive things a leadership team can do and among the least well executed. The design usually receives months of attention. The transition receives a slide.

That imbalance is the problem. Most of the value destroyed in a restructure is destroyed in the eight weeks after the announcement, when accountability is ambiguous, informal networks are broken, and the best people are taking recruiter calls.

Be honest about the problem you are solving

Structure can fix a small number of problems: misaligned incentives, decisions made too far from the information, duplicated capability, unclear ownership. It cannot fix a weak strategy, an underperforming leader, or a culture issue. Reorganizations aimed at those problems reliably fail, and the organization can usually tell which kind it is watching.

Write the problem in one sentence before designing anything. If the sentence is vague, the structure will be too.

Design for the decisions, not the boxes

Start from the ten most important recurring decisions in the business and ask who should make each one, what information they need, and who must coordinate. Structure follows from that. Teams designed this way tend to have fewer escalations because the decision and the information sit in the same place.

• Which decisions are we trying to move, and to whom?
• What coordination will the new structure make harder? Every design makes something harder.
• What will we do about the seams? Name the two or three interfaces that will now require deliberate management.

Announce completely or not at all

The most damaging pattern is the partial announcement: structure now, leadership appointments in a few weeks, team assignments later. Every gap is filled with speculation, and productivity drops for the entire period.

Wait until you can tell people three things simultaneously: what the structure is, who leads what, and who they report to. If you cannot say all three, you are not ready to announce.

The half-announced reorganization costs more than the delayed one. Ambiguity is not a neutral state; it is an active tax.

Say what happens to people, first and plainly

Before the strategic rationale, before the diagrams, answer the questions everyone is actually holding: is my job at risk, does my manager change, does my work change, when will I know. Then explain the reasoning. Leaders routinely reverse this order and lose the room in the first ninety seconds.

If there are reductions, say so immediately and give the date certainty will arrive. Prolonged uncertainty produces more attrition among people you wanted to keep than the reduction itself.

Rebuild the informal network deliberately

Org charts do not carry institutional knowledge; relationships do, and restructures sever them. In the first month, deliberately recreate what was broken: pair people across new boundaries, hold joint sessions for teams that used to sit together, and document the handoffs that used to happen by proximity.

Measure the transition, not the design

Set three indicators for ninety days: decision latency on a few named decisions, voluntary attrition in the affected population, and one delivery metric that should not degrade. Review them monthly and be willing to adjust the design.

Structures are hypotheses. The organizations that reorganize well are the ones that treat them that way rather than defending the diagram for two years because it took six months to draw.