Most organizations are still treating margin pressure like a future risk. It isn’t. Tariffs since 2025 have already injected more than $175 billion in cost into the system, and shipping disruptions tied to conflict in the Middle East are compounding it. Pricing, supply chains, and labor models are all under pressure at once — and that pressure is quietly raising the likelihood of operational and compliance failures that won’t surface until they’re expensive.
The executive response to all of it still collapses to the same two moves: cut headcount and automate what’s left.
To be clear — neither is inherently wrong. In acute financial distress, both can be necessary for survival. The real issue is centered within sequencing. When organizations apply expensive tools and drastic cuts to unmapped workflows and processes, they aren’t solving the problem. They’re changing the shape of the dysfunction and often only in ways that are harder to see and easier to scale.
Before you eliminate a position, you need to know what that position is actually doing. Most organizations think they understand a role because they can point to a title on an org chart. Ask them to trace how that role actually moves work, and the answer gets vague fast.
The Limits of the Org Chart
Value stream mapping is borrowed from lean manufacturing. It traces every step a unit of work takes from input to output — where value is actually created and where it disappears into waiting, rework, redundant approvals, and unnecessary handoffs.
In a perfect world, you map the entire enterprise before touching a single headcount decision. In the real world of large, fragmented organizations under financial pressure, that can take months. By the time the map is complete, the market has moved.
You don’t need a perfect map. You need one good enough to avoid cutting the wrong arteries — or preserving the wrong ones. When work runs through four people that a well-designed process could handle with two, cutting one of the four doesn’t fix anything. The problem is how the handoffs flow.
I spent years partnering with municipal governments where zero-sum budgets were the baseline. I watched organizations survive genuine resource emergencies through redesign rather than shrinkage. Some positions are genuinely redundant — not because the people filling them are underperforming, but because the process was a product of accumulation rather than design. A reorg added an approval layer that never got removed. A handoff built to manage a risk that no longer exists is still running, still consuming time, still showing up on nobody’s priority list because it has always just been there.
Consider a municipal procurement process where a $5,000 purchase requires four signatures because of a scandal that happened a decade ago. A rapid flow analysis will find that. A round of layoffs guided by budget targets and org charts likely will not. Budget-driven cuts tend to preserve bureaucratic layers because the people with budget authority protect what surrounds them. They eliminate producers closest to the actual work.
The Automation Argument Deserves More Scrutiny
Replacing a human operator with an automated process does not redesign the process. It removes the human from it.
Automation can reduce cycle times and surface bottlenecks through data. Sometimes that’s useful diagnostically. But if the underlying workflow has redundant steps, unclear accountability, and unnecessary handoffs, automating it produces a faster version of the same problem — with less human judgment available to catch what the system misses.
In regulated environments — healthcare, municipal services, financial services — that isn’t a cost savings. It’s a compliance exposure waiting to surface.
Take an RPA bot patching data transfers across three legacy systems that were never meant to talk to each other. When the bot misreads a field — pulling a patient identifier from a mismatched format because the underlying process was never standardized — there’s no human safety net. The resulting HIPAA violation or clinical error isn’t a technology failure. It’s a design failure that automation made invisible.
Automation applied to a broken process locks in the break.
A Framework for Acting Under Pressure
You cannot map the entire company under margin pressure. You also cannot cut blindly. The practical middle is a triage approach:
- Identify the pressure points. Where is the business bleeding the most cash or failing customers most visibly? Map those areas first and only those areas.
- Map the reality, not the policy. The documented process will hide the risk. Trace the actual flow of work in critical areas. Don’t ask what the manual says — ask what happens when the primary admin is out sick.
- Redesign for flow before you cut. If you haven’t removed dead-end approvals and redundant handoffs, you have no real basis for headcount reduction. Once the work is streamlined, the necessary cuts usually become obvious.
- Automate what’s been standardized. Automation should follow clarity. Applied before it, automation scales ambiguity.
The Problem with Calling HR “Infrastructure”
Who owns this redesign work? In many organizations, operations or transformation teams lead it. But HR has to be a real partner — not a passenger.
The failure to redesign processes before cutting or automating is ultimately a failure of ownership.
HR gets called infrastructure, then goes right back to processing offer letters as if that’s the job. Admin work matters. But infrastructure means owning how work moves, not just managing the people moving through it. If HR doesn’t partner with operations on process design, it’s just relabeling the admin function and calling it strategic.
Organizations that come through this cycle in better shape than they entered will do it by building leaner systems — not by inventing them in the middle of a crisis.
Every organization is the accumulated result of past decisions that were never revisited. Every system is working exactly as designed, even the dysfunctional ones.
