The Reorg Reflex That Breaks Execution
A new strategy gets announced, and within weeks someone is redrawing the org chart.
That reflex creates more execution problems than it solves.
The disruption that follows consumes the attention and time you need to deliver results.
Changing structure changes how work flows through the company, whether you intend it to or not. People have to relearn who to go to, where decisions sit, and how things actually get done. During that adjustment period, execution almost always takes a hit.
You start to see it almost immediately. Decisions that used to happen quickly now require another conversation. Questions that would have been answered in the room get taken offline. Work pauses because someone isn't sure whether they still own the call.
It shows up in the calendar, too. More alignment meetings. More pre-reads. More time spent making sure everyone is comfortable before a decision moves forward.
None of this is irrational.
When roles shift and decision rights aren't clear, people naturally become more cautious. The risk of stepping outside your lane suddenly feels higher than the risk of waiting. So momentum drops.
The real problem is timing.
If priorities and guiding principles aren't already clear, reorganizing just adds friction. Teams spend energy figuring out who owns what instead of delivering outcomes, and leaders burn attention resolving confusion that didn't exist before.
That's why it should never be the automatic response to a new strategy.
When a new strategy is developed, the first move shouldn’t be to redraw the org chart. It should be getting clear on how work actually gets done — who owns which decisions, how those decisions get made, and where the real friction points are. Structure should be the last thing you touch, not the first.
That means working through a specific sequence before you consider changing anything organizational:
Start with decisions. Where do they need to be faster or simpler? Who should own them, and what principles should guide them when there's no clear answer?
Then clarify roles and hand-offs. What does each team actually deliver, and where do things fall through the cracks between them? Friction points that feel structural are often just ambiguity in disguise.
Then consider the human element. Every boundary you draw on an org chart creates an in-group as well as an out-group. People grouped together develop shared identity, shared language, and a way of working that builds over time. That's a real asset. But every boundary also creates a potential us-versus-them dynamic with whoever sits on the other side of it. You can't eliminate that tension, but you can be deliberate about where it shows up. The question isn't whether your structure will create both cohesion and friction — it will — but whether you've drawn the lines in places where the cohesion benefits the work most, and the friction lands somewhere you can manage it.
Only after that work is done does the structural question become meaningful. At that point you can evaluate whether the current structure supports the work. And even then, you change it only if you can point to a specific constraint the new structure will remove.
Otherwise you've traded one set of problems for another, except now people are also trying to figure out where they fit.
