Jesse Jacoby
I have watched restructurings land exactly on plan. The headcount reduction comes in within a percent of target. Severance runs under the reserve. The run rate steps down on the promised date, and the finance team can trace every dollar back to a line in the case. On the metrics the program was built to satisfy, it worked.
Eighteen months later the same organization is paying contractors to do work it used to do internally. Approval cycles have quietly lengthened. Two of the people leadership most wanted to keep have left for competitors. Nobody connects those facts to the restructuring, because by then the savings case is closed, the tracking has stopped, and the executive who built it has moved into a different role.
This is not an argument that restructuring is always wrong. Sometimes an organization genuinely carries more cost than its revenue can support, and delaying the decision only makes the eventual cut deeper and less humane. The argument is narrower and more uncomfortable: the savings and the costs of a restructuring are recorded on entirely different timetables, in different currencies, and often against different P&Ls. That asymmetry is what makes the business case look so clean, and it is why a decision that is fully defensible on the day it is announced can still leave the organization weaker two years later.
The Evidence Has Been Consistent for Thirty Years
Wayne Cascio has spent much of his career on this question, and his findings have been inconvenient for a long time. Working with Arjun Chatrath and Rohan Christie-David, he examined restructuring events across firms listed on the New York Stock Exchange over a thirty-seven year period, from 1980 through 2016. The pattern that emerges across that body of work is not that downsizing destroys value in every case. It is that downsizing on its own does not reliably produce the performance improvement it is sold as delivering.1
Earlier work in the same vein compared firms that cut deeply against industry peers that did not, and found no durable profitability or shareholder return advantage for the cutters. Cascio’s conclusion, restated across decades of research, is that employment downsizing should be used sparingly and as a last resort rather than as a default lever.2
That finding is easy to dismiss as academic, because inside any single company the savings are demonstrably real. Payroll is genuinely lower. The mistake is treating a verified reduction in one cost line as evidence that total cost fell. Those are different claims, and only one of them gets measured.
What Actually Leaves the Building
An org chart shows roles, levels, and reporting lines. It does not show who knows why the exception process for the Midwest distributor exists, who to call at the vendor when the integration breaks at two in the morning, or which customer will escalate straight to the board if a shipment slips. That knowledge is real, it is load-bearing, and it lives in people rather than in documentation.
It also lives in a network that no one has mapped. Every organization runs on an informal structure of trust and reciprocity that determines how fast information moves and how quickly problems get solved. Some people are hubs in that network. Most are not. When selection criteria are built around cost per head, span of control, tenure bands, or performance ratings, the selection is essentially orthogonal to the network. You are as likely to remove a hub as a leaf, and the org chart cannot tell you which one you did.
There is a further complication. The person holding the most institutional value is frequently mid-level and modestly compensated, which makes them cheap to retain and invisible to protect. Nobody builds a retention case around the operations manager in her fourteenth year. She is, however, the reason four processes work.
Removing People Removes Capacity, Not Demand
This is the structural flaw in most savings cases, and it is almost never stated explicitly. A restructuring reduces the supply of labor. It does nothing on its own to the demand for work. Unless somebody deliberately retires activity, the work does not disappear. It redistributes to whoever remained.
That redistribution has no line item, so it is invisible in the case. It shows up later in forms that are hard to attribute: approvals that used to take a day now take four, quality checks skipped under load, a contractor invoice landing in a cost center that was never part of the program, a manager doing individual contributor work at nine at night instead of coaching a team. Each of those is a real cost. None of them is booked against the restructuring.
There is a simple discipline that catches most of this, and very few programs run it. For every role removed, name the work that role performed, and place it in one of four buckets: eliminated, automated, absorbed with a redesigned process, or absorbed with no process change. The first three are legitimate. The fourth is where savings quietly erode, and in most restructurings I review, the fourth bucket is by far the largest and the least examined.
The Survivors Are the Asset You Just Bought
The people who remain are the entire operating capability going forward, and their state after the announcement determines whether any of the savings survive contact with reality. The research here is blunt. In one widely cited study of layoff survivors, seventy-four percent said their own productivity had declined since the reduction, and sixty-nine percent said the quality of their company’s product or service had declined.3
Read that carefully. These are not the people who left. These are the people the organization chose to keep, reporting on their own output. If productivity among the retained population falls meaningfully, a fifteen percent headcount reduction does not deliver a fifteen percent capacity reduction. It delivers something worse, at least for a while, and how long that period lasts is a leadership variable rather than a fixed constant.
What drives the duration is not the memo. It is what people infer from how the decision was executed: whether the criteria were explained or left ambiguous, whether leaders were visible in the weeks afterward or unavailable, whether the people who left were treated well on the way out, and whether anyone in authority acknowledged that the remaining team is now carrying more. People can absorb a hard decision. What they cannot absorb is a hard decision that appears to have no plan behind it.
The Recovery Phase Is the Restructuring
Most restructuring programs are funded, governed, and staffed through the announcement, and then they stop. The steering committee dissolves. The program manager rolls off. The tracking reverts to a monthly finance report on run rate.
That is precisely backward. The announcement is the easiest part to execute and the least determinative of the outcome. The recovery is where the organization either rebuilds capability around a smaller footprint or slowly discovers it cannot do what it used to do. Three things belong in a funded recovery phase with the same governance rigor the announcement received.
Explicit work triage in the first sixty days, using the four-bucket test above, with a named executive empowered to kill activity rather than redistribute it. If nobody has authority to stop work, the redistribution happens by default and by exhaustion.
Deliberate knowledge and relationship transfer. Map where critical institutional knowledge now sits, who holds each external relationship, and where single points of failure were created. This takes weeks, not months, and it is the highest-return work available in the period immediately after a reduction.
A forward narrative with real substance. Not reassurance, which nobody believes, but a specific account of what the organization is building toward, what it has deliberately chosen to stop doing, and what the remaining team is expected to be world-class at. Ambiguity after a restructuring gets filled by the most pessimistic available interpretation.
A Different Ledger
Before approving the next case, put three questions to it. What capability are we deliberately choosing to give up, stated in plain language rather than implied by a number? Which specific work are we eliminating rather than redistributing, and who has the authority to enforce that? What does the recovery phase cost, who owns it, and how long are we tracking it?
A case that cannot answer those is not a business case. It is a subtraction exercise with a cover page and a finance sign-off.
The savings will look right. They almost always do, because they are measured with precision against a baseline that was chosen to make them measurable. The harder question, and the one that determines whether the decision was actually a good one, is whether the organization on the other side of those numbers can still do the thing you are counting on it to do.
References
- Analysis of employee and asset restructuring events among firms listed on the New York Stock Exchange across a 37-year period (1980 to 2016), examining both the antecedents of downsizing and upsizing and their performance consequences relative to prior firm performance. Wayne F. Cascio, Arjun Chatrath, and Rohan Christie-David, “Antecedents and Consequences of Employee and Asset Restructuring,” Academy of Management Journal, Vol. 64, pp. 587 to 613.
- Cascio’s longitudinal comparisons of firms that undertook significant workforce reductions against industry peers that did not found no durable profitability or shareholder return advantage for the downsizers, leading to the conclusion that employment downsizing should be used sparingly and as a last resort. Wayne F. Cascio, “Strategies for Responsible Restructuring,” Academy of Management Executive.
- Survey of layoff survivors in which 74 percent reported that their own productivity had declined since the layoff and 69 percent reported that the quality of their company’s product or service had declined. Leadership IQ, “Don’t Expect Layoff Survivors to Be Grateful.”
