Flattening the org is not a strategy. It is a budget decision wearing a strategy’s clothes.
I have seen this play out more than once. A leadership team builds a clean cost case. The model holds up in the room. The board approves the restructure in a single meeting. Execution problems last three years.
What the Model Did Not Capture
At one company, the leadership team projected a 15% reduction in overhead costs. The numbers were accurate. The assumptions behind them were not.
What the model did not include was the cost of delayed decisions, missed project milestones and increased attrition over the following 18 months. When we added it up, that drag exceeded the savings the restructure was supposed to deliver. The analysis looked complete. It was not complete, because the people who understood how decisions actually moved through the organization were not part of building it. The analysts modeled the layers. No one modeled the work those layers were doing.
That is the root cause I see most often. Not malicious intent. Not bad math. Wrong people in the room.
The Work That Disappears
Middle managers do work that does not appear on any org chart. They translate strategy into daily action. They absorb conflict before it reaches senior leadership. They carry context across teams so every decision does not have to start from scratch.
When that layer is removed, the work does not disappear. It moves up.
I have seen senior leaders inherit flattened teams and spend more time managing up than executing. The leadership overhead transfers quietly. It does not show up in any budget line. But it shows up in response times, in missed windows and in leaders who are too stretched to make good decisions about what comes next.
The cost is real. It is just invisible until you are already inside it.
The First 60 Days Nobody Plans For
I once joined a company that had just eliminated its entire middle management layer. No one knew who approved new hires. Decisions that had taken three days were taking three weeks. I spent my first 60 days rebuilding the decision-making structure we had just dismantled, while also trying to scale the business.
That is the part that never makes it into the business case. You remove the layer. You capture the short-term savings. Then someone has to perform that work again, usually under worse conditions and without the institutional knowledge the previous layer carried.
The restructure made sense on paper. In practice, it created a 60-day execution hole at the exact moment the business needed to accelerate.
Three Things That Actually Hold
Not every restructure fails. The ones that hold tend to share three characteristics.
- Map the invisible work before anything is cut. Before any layer is removed, document what that layer actually does. Not the job description. The real work. Who is coordinating across teams? Who absorbs escalations? Who translates board-level priorities into team-level decisions? If you cannot answer those questions with names and specific handoffs, the organization is not ready to restructure.
- Assign a single owner to every critical handoff. When a management layer is removed, the handoffs it managed do not disappear. They become ambiguous. The organizations that recover fastest assign explicit ownership to every critical decision path before the restructure is announced, not after.
- Run a 90-day decision audit. Commit to a structural review 90 days post-change. Not a survey. A decision audit. Where did decisions stall? Which milestones slipped? Which escalations reached senior leadership that should have been resolved below? Those answers tell you what the original model missed and where to reinforce before the next quarter amplifies the problem.
The Trade-Off Is Real. So Is the Risk.
Flatter organizations can move faster. That part is true. But speed requires clarity, and clarity requires structure. Not layers for the sake of layers. Structure that makes it obvious who decides, who coordinates and who absorbs the noise so the rest of the organization can execute.
The companies that handle this well treat the restructure as an operating design problem, not a headcount problem. They start with what the organization needs to produce, then design the structure to support that output. The savings are real. The risks are also real. The difference is whether both numbers are in the analysis before the board votes.
A PE board approved the restructure in a single meeting. Execution problems lasted three years.
That sentence belongs in every business case before it is submitted.
If you are navigating this right now, let’s compare notes. I am currently opening conversations for my next fractional or full-time leadership role.
Review checklist before you approve:
- Does the 15% overhead example read the way you intended in the What the Model Did Not Capture section?
- Does the “wrong people in the room” closing line of that section land the way you want it?
- Any wording, tone or structural changes before I lock and produce the final package?
Once you approve, I will deliver the final formatted article with the full SEO/CMS output and CSV, ready to paste into WordPress.