In partnership with
Opening Salvo
You knew the reorg wasn't going to fix it before it was announced, and the people around you knew it too, but it got announced anyway because restructuring is the most defensible move available when the real problem is one nobody at the table wanted to name out loud. Now the org is out the time and money, the original problem is still there, and the question sitting underneath the next planning cycle is whether this time someone is going to say what everyone already knows.
The org chart is not the strategy, and treating it as one is how organizations end up in cycles of restructuring that produce transition costs, talent disruption, and coordination losses without ever addressing the execution or clarity failures that made the reorg feel necessary in the first place. The structure should follow the strategy, and when it doesn't the answer isn't a new structure, it's an honest conversation about whether the strategy is clear enough to be structured around, and that conversation is the one most senior leaders keep finding reasons to defer.
What's in your purview is naming what the reorg was actually avoiding, and most organizations find that question more uncomfortable than the reorg itself, which is precisely why the cycle keeps repeating.
Practical Personas (with a tinge of hyperbole)
The Reorg Reflex: When execution stalls, their instinct is to redraw the structure, and they've got a track record of bold restructurings that read as decisive leadership in the moment and as activity in retrospect. They're not avoiding the real problem in any conscious way, they've just learned that a reorg is something they can announce, control, and be seen leading, and the harder conversation about strategy clarity is one they don't have a clean mechanism to run, so the structure becomes the thing they move because it's the thing they can move.
The Structure Defender: They sat through the last reorg knowing it wouldn't address the actual problem, said as much in a few private conversations, and went along with it publicly because the political cost of being the person blocking the leadership team's solution was higher than the cost of watching it fail. They'd tell you they raised concerns, and they did, in the rooms where raising them was safe, and the org absorbed the consequences of a restructuring that a number of people at the table already knew was treating the wrong thing.
The Clarity Holder: They ask the right question before every reorg, the one about whether the strategy is defined clearly enough to design a structure around, and they ask it sincerely, and it rarely changes what gets decided because asking the question from their seat without the authority or willingness to force the answer is its own form of participating in the cycle. They've raised the concern, they're on record, and the org restructures anyway, and the distinction between surfacing the problem and owning the resolution is one they haven't fully reckoned with yet.
Ask Yourself
Think about the last reorg your organization executed. Name the problem it was announced to solve and whether that problem is more or less present today than it was before the structure changed.
If the strategy your current org chart is designed to serve was written down and put next to the structure, how much of the structure would be recognizable as a response to that strategy and how much of it would be recognizable as a response to the last reorg?
When the org chart keeps changing and the execution keeps struggling, the organization doesn't have a structure problem. It has a strategy clarity problem that's been expensive enough to restructure around and not uncomfortable enough to actually solve.
The docs platform Anthropic, HubSpot, and Coinbase trust
Your documentation is a product decision. The companies building the most-used developer tools in the world chose Mintlify because great docs reduce support load, accelerate adoption, and convert evaluators into customers. Backed by a16z and Salesforce Ventures, Mintlify powers 20,000+ companies with AI-native documentation that keeps pace with your product — without pulling engineers off the roadmap to maintain it.
Did You See This?
AI Pilot Purgatory Has a Cause and It's Not the Tech
Stop spending more time double-checking your books than growing your business. BELAY provides the financial clarity and "peace of mind" you need to lead with confidence. Get your time back today. Get the Free Guide
Talent Management 101 (TM101)
Structure Follows Strategy: Why Reorgs Without Clarity Produce Costs Without Progress
Alfred Chandler established in 1962 that structure should follow strategy, meaning the way an organization is designed should be a direct response to what the organization is trying to accomplish. The principle is simple enough that most senior leaders would agree with it in the abstract and violate it in practice, because the conditions that produce a reorg are rarely conditions of strategic clarity. They're conditions of execution pressure, political tension, or leadership transition, and restructuring is the response that looks like action without requiring the organization to first answer what the structure is supposed to serve. The result is a structure that reflects the last crisis more than the current strategy, and an organization that keeps paying the cost of transition without ever closing the gap between how it's designed and what it's trying to do.
Why It Happens
Restructuring is visible, strategy clarification is not: A reorg produces announcements, new reporting lines, and the appearance of decisive leadership. The conversation required to define a strategy clearly enough to design around it produces discomfort, disagreement, and the exposure of gaps in alignment that the organization would rather not have surfaced. The reorg gets chosen because it can be managed and presented, and the harder conversation gets deferred because it can't.
The org chart inherits the last reorg's logic: Most structures aren't designed from scratch against a current strategy, they're modified from the previous structure in response to the most recent pressure, which means every reorg carries the accumulated logic of the reorgs that preceded it, and the distance between the structure and the strategy grows with each cycle.
Transition costs get absorbed, root causes don't: Every restructuring produces real costs in talent disruption, coordination losses, and productivity drag that the organization absorbs as the price of change. What doesn't get absorbed is accountability for whether the change addressed the right problem, because by the time the transition costs are visible the leadership attention has moved to managing the new structure rather than interrogating the old diagnosis.
The Question Organizations Avoid
If your organization has restructured more than once in the last three years and the execution challenges that preceded each reorg are still present in some form, the question isn't whether the structures were designed well. It's whether the strategy they were designed to serve was ever defined clearly enough to design around.
The Plug
This newsletter is brought to you by AstutEdge, a performance improvement consultancy. We help organizations close the gap between what leadership intends and what actually gets executed by fixing the misalignment in people, systems, and structure that stalls results.
We work through consulting engagements and coaching. If your organization is producing effort without outcomes, let's talk.
Visit astutedge.com or share this with a leader who feels the drag.