The Reorg Trap: Why You Want to Restructure, and Why It's Usually the Wrong Move

The number misses. Not catastrophically — just enough that the board will ask, and enough that you can feel the room change temperature. Somewhere in the second week, without deciding to, you start redrawing boxes. You do it on a whiteboard at home or in a notebook at the back of a meeting: who reports to whom, which function belongs under which roof, whether the product people should sit with engineering or with the commercial side. The sketch is pleasing. It has lines and it has a shape, and it gives the week's diffuse unease somewhere to go. By Friday you've begun telling yourself the organization has outgrown its current structure — a sentence that is technically true every year of every company's life, and therefore proves nothing.

Restructuring is the most seductive move available to a leader under pressure, and the seduction is worth understanding before you evaluate the move itself. A reorg is the only intervention in leadership that produces visible, legible action inside a week. Hiring takes months. Strategy takes a quarter to test. The conversation with the person who is actually the problem takes something harder than time. But you can move a box on Monday and everyone can see you have done something by Wednesday. So the chart ends up used as a container for anxieties it was never built to hold.

What a reorg actually buys you

To be fair to it: structure is not nothing. Reporting lines are real, and a bad one is a tax paid every day in escalations, duplicated work, and decisions nobody owns. If the chart is genuinely wrong, no amount of communication skill fixes it, and waiting a year to admit that costs you the year. Structure decides who has authority to decide, whose incentives point where, and what information has to cross a handoff to reach the person who needs it. When those are broken, the organization will feel broken, and the diagnosis will be correct.

The problem is that "the organization feels broken" has at least four causes and only one of them is the chart. The others are clarity, capability, and courage — and a reorg fixes none of them. It is very good at masquerading as a fix for all three, because it consumes the attention that would have gone to them and produces a plausible story about why everything is in flux.

• One person is holding two genuinely different jobs, and the conflict is now structural rather than seasonal.
• Two teams own one outcome, and neither can be held accountable for it.
• A recurring decision has no owner, and the reason it has no owner is visible in the reporting lines.
• Information that must reach someone weekly currently crosses three handoffs to get there.
• A span of control has grown past the point where one person can actually manage it.

Notice that every one of those is a specific, nameable claim about a decision or a flow. If you can't state yours that way — if your version is "the commercial side feels disconnected from product" — you don't have a structural diagnosis. You have a feeling with a diagram attached to it.

The test before you touch the chart

One question sorts most of these in under an hour: if you were not allowed to change a single reporting line, what would you have to do instead? Write the answer down. Whatever is in that list is the actual work — the clarity you haven't published, the decision you haven't made, the person you haven't talked to. The reorg is very often a way of not doing it, and it is a way that costs a quarter.

• Name the decision. Not the misalignment — the specific decision that cannot be made today, with a date attached. If you can't name one, the diagnosis isn't ready.
• Ask whether the reporting line is the obstacle or the clarity is. Most complaints that "our structure doesn't support speed" are really "nobody has written down who is allowed to decide this."
• Identify the two people this makes worse. Every reorg has losers — status, scope, or visibility removed. Those two people do most of the work in the quarter that follows, and they will know exactly what you did.
• Say out loud what would have to be true for this to be the last reorg. If you don't have an answer, you aren't solving a problem, you're relieving a feeling.

What the redraw really costs

A reorg is billed as free because nothing is invoiced. The real cost is attention and status, and both are expensive. Every person in the affected area spends six to twelve weeks quietly renegotiating their position: what they own now, whether they were demoted in the shuffle, whether their standing with you has changed, and whether they should be updating their résumé. That work happens under the surface and shows up as a slowdown in exactly the output you were trying to fix.

The deeper cost is invisible on the chart. Real coordination doesn't live in reporting lines; it lives in relationships — the director who knows to call one specific person before the customer meeting, the peer who will give you the unvarnished version. Years of accumulated trust are the actual operating system, and a redraw scatters it. Then, in the ambiguity, the people with the most options leave first — a pattern most leaders already know and still manage to walk into again.

Then there's the meta-lesson, and it's the one that compounds. When a team learns that discomfort produces a redraw, the organization acquires a habit: every hard stretch gets answered with a new diagram instead of a hard conversation, a hiring decision, or a standard being enforced. That habit is expensive to break and nearly impossible to see from inside, because each individual reorg has a reasonable justification. Two in eighteen months isn't two decisions. It's one symptom, observed twice.

Why the urge is physiological

The reason a leader reaches for the chart under stress isn't strategic. It's that unresolved uncertainty is genuinely uncomfortable for a nervous system. An open loop — a number you can't explain, a problem you can't yet name — keeps attention in a vigilance state, and vigilance is costly. The brain will trade a bad answer for no answer, and a fast false one for a slow true one, because closing the loop relieves the state even when the content is wrong. Redrawing boxes closes the loop. It converts a diffuse threat into a solvable diagram, and the relief you feel is real, which is why the move feels like insight.

Under pressure that pull strengthens while your capacity to resist it weakens. Stress narrows thinking toward fast, concrete, action-oriented options — which is exactly the category a reorg belongs to. The leader best equipped to resist the redraw is the one whose physiology isn't currently asking them for it.

The sequence that usually works better

None of this means never restructure. It means restructure last, and only after the cheaper options have had a real run. The order that resolves most of these situations without touching the chart:

• Publish the mandate. In plain language, write down who owns which decision and what they're allowed to decide without asking. Much of the friction you're feeling disappears under this alone.
• Give the stuck decision a real owner and a date, and say it out loud twice.
• Move a decision, not a person. Changing what someone is accountable for is cheap and reversible; changing who they report to is neither.
• Run ninety days with the structure unchanged and a written success criterion. If nothing improves, your structural hypothesis has gained evidence — and you'll know which part to change.
• Fix the smallest thing that could work. The version of a change that slightly embarrasses you is usually right; the version that looks like a transformation is usually the one that costs a quarter.

When restructuring is genuinely the right call

Be honest about the counterweight, because this argument can be misread as "never change the org," which is its own kind of failure. Restructure when the chart is measurably wrong in one of the specific ways named earlier; when you're crossing a real threshold — a second product line, a new geography, a company that has doubled and still runs on a chart drawn for half the headcount; or when the same escalation keeps landing on your desk and the reason it lands there is visible in the reporting lines.

Do it rarely, do it with the reason attached, and do it in writing. A reorg that arrives with a named problem and a stated test is a management decision. A reorg that arrives with a feeling and a fresh look is a tell — and everyone below you can read it.

"If you can't say which decision a reorg makes possible that can't be made today, you're not restructuring. You're relieving anxiety in a costume."

So before you move the boxes, put the sketch in a drawer for two weeks and publish a mandate instead. If the organization is genuinely wrong, the diagnosis will survive the fortnight — and you'll arrive at the change with evidence, a test, and the two people you're about to disadvantage already named and already handled. If it doesn't survive the fortnight, you'll have saved a quarter and told nobody why.