Results stalled. The board met. The first move was the org chart.
New reporting lines. New titles. A few lateral hires. Everyone updates LinkedIn. The operating partner presents the restructuring to the board as a decisive intervention. The management team absorbs the disruption and goes back to work.
Six months later the same problems report to different people.
The reorg moved the boxes. The boxes were never the problem.
Why the reorg is always the first instinct
When a portfolio company is not hitting its targets, the board needs to act. Doing nothing is not an option. The value creation plan has milestones. The operating partner has a timeline. LPs have expectations. Something visible has to happen.
The reorg is the most visible action available. It is immediate. It is decisional. It demonstrates that leadership recognizes the problem and is responding. It changes names on org charts, which creates the appearance of change without requiring the organization to understand what actually broke.
This is not cynical. The people making these decisions are usually acting in good faith. The theory behind a restructuring is sound in many cases. If the problem is a leadership gap, replace the leader. If the problem is a coordination failure, change the reporting structure. If the problem is accountability, create clearer ownership.
The issue is that in most portfolio companies where the value creation plan is stalling, the problem is not the people or the structure. The problem is the infrastructure underneath them.
The infrastructure problem that looks like an org chart problem
Here is what the pattern typically looks like.
The value creation plan calls for pricing optimization. The pricing initiative stalls. The board asks why. The management team explains that the data needed to support segment-level pricing is unreliable. Cost data lives in three systems that do not agree. Customer profitability cannot be calculated accurately. The pricing team cannot model the impact of changes because the baseline is not trustworthy.
The board hears “the pricing initiative stalled” and concludes the pricing leader needs to be replaced or the reporting structure needs to change.
The actual issue is that the data infrastructure does not support the initiative. The pricing leader knows this. Their team knows this. But explaining that the failure is an infrastructure problem, not a competence problem, requires a level of organizational candor that most board environments do not support.
So the reorg happens. A new pricing leader arrives. They spend 60 days learning the business. They arrive at the same conclusion the previous leader reached. The data cannot support the initiative. But they are less likely to say so because they were hired to deliver results, not to explain why results are structurally blocked.
The initiative stalls again. The next board meeting reviews the same gap. And the cycle continues.
The CDO as a shield
The most common data-specific version of this pattern is the CDO hire.
The board recognizes that data is a problem. The solution is to hire a Chief Data Officer. The mandate is clear. “Fix the data.”
But “fix the data” is not a mandate. It is a wish. The CDO arrives without agreement on what “fixed” means. Without budget authority over the source systems that generate the data. Without executive alignment on which metrics are canonical. Without a decision about whether the goal is operational reporting, buyer-ready analytics, or AI enablement.
The CDO does what any competent leader would do. They assess the landscape. They build a small team. They pick a tool. They start a roadmap. They present quarterly updates to the board.
Twelve months later, there is activity but no progress. The CDO has a team, a strategy deck, and a roadmap. The source systems still do not agree with each other. The board deck is still assembled from spreadsheets. The finance team still reconciles manually every month.
The CDO did not fail. The organization failed to make the decision that had to precede the hire.
You do not hire a leader to figure out the strategy. You figure out the strategy and then hire a leader to execute it. The CDO was handed a mandate without a decision. They inherited the ambiguity the board was trying to outsource.
Diagnosing before reorganizing
The firms that avoid the reorg trap share a discipline. They diagnose before they reorganize.
The diagnostic is straightforward. It asks three questions.
Is this a people problem or an infrastructure problem? If the pricing initiative stalled because the pricing leader lacks competence, that is a people problem and a reorg may be appropriate. If the pricing initiative stalled because the data cannot support segment-level pricing, that is an infrastructure problem and a reorg will not fix it.
What would this person need to succeed? Before replacing a leader or changing a reporting line, ask what conditions would enable the current leader to deliver. If the answer is “reliable data, consistent definitions, and a source of truth for customer profitability,” then the intervention is not a new leader. The intervention is the infrastructure.
What decision has not been made? In most stalled initiatives, there is a decision hiding underneath the problem. Which system is authoritative for revenue? How do we define customer count? Who owns the EBITDA bridge? These decisions were never made because they are uncomfortable. They require someone to be accountable for a number. The reorg avoids the decision by moving the accountability around. The decision remains unmade.
What infrastructure-first looks like
The alternative to the reorg is not inaction. It is a different kind of intervention.
Fund the data infrastructure. If the pricing initiative needs reliable cost data by customer segment, fund the work to reconcile the cost data. This is not a multi-year transformation. It is a quarter of focused work to establish a canonical source of truth for the specific data the initiative requires.
Make the decisions. Before building anything, decide which system is authoritative for each key metric. Document the decisions. Get executive agreement. If the board cannot agree on which system produces the authoritative revenue number, no amount of technology will resolve the discrepancy.
Give the existing team what they need. The pricing leader who stalled may be the right person for the job if they have the right data. The CDO who has not produced results may be effective if they have clear mandate, budget authority, and executive alignment. Before replacing people, consider whether you gave them the conditions to succeed.
Measure differently. If the value creation plan has milestones that depend on data infrastructure that does not exist yet, adjust the plan. Add data readiness milestones. Track the infrastructure work as a precondition for the operating initiatives. Make the dependency explicit rather than letting the operating initiative fail and blaming the leader.
The cost of the wrong intervention
Every reorg has a cost that extends beyond the visible disruption.
Lost institutional knowledge. The leader who is replaced understood the systems, the relationships, and the history. Their replacement starts from zero. The 60 to 90 day ramp-up is time the company does not have on a five-year hold.
Organizational fatigue. The management team absorbs each restructuring. Morale declines. Good people leave. The remaining team becomes risk-averse because they have seen what happens when initiatives do not deliver.
Delayed root cause resolution. The reorg addresses the symptom (stalled initiative) without addressing the cause (insufficient infrastructure). The next leader encounters the same cause. The cycle burns another six months.
On a five-year hold, two rounds of this cycle consume two years. On a seven-year hold with an average exit at year seven, two years of misdiagnosed interventions is 28% of the hold spent reorganizing around a problem that was never structural in the first place.
The structural principle
There is a principle that applies to every organizational problem in PE-backed companies.
Structure follows clarity. Not the other way around.
You cannot solve an infrastructure problem by moving the boxes around. You can only delay the moment when someone has to look underneath them.
The right sequence is to make the decision first. Which metrics matter. Who owns them. Which system is authoritative. What “fixed” actually means. Then hire the person. Then fund the infrastructure. Then hold people accountable.
The wrong sequence, which is the one most organizations follow, is to hire the person and hope they figure out the decision, the infrastructure, and the accountability simultaneously. They cannot. Because those are different problems that require different interventions.
The reorg feels like action. Diagnosis feels like delay. But the reorg that addresses the wrong problem costs more than the diagnosis ever could. In time. In talent. In the EBITDA that was sitting right there, waiting to be captured, if someone had looked underneath the boxes instead of rearranging them.