What Happens to the Coordinating Work When Middle Management Shrinks by 42%

We watched a reorg remove two layers of management last year. Within a quarter, the status-update chasing, the cross-team follow-up, the quiet "did anyone tell finance" pings that used to be spread across those two layers had all funneled into a single inbox. The org chart got simpler. Nobody's job got easier.

That's not a one-company story. Middle-management job postings are down 42% from their April 2022 peak, and most of the conversation about that decline stops at the org chart.

Middle-management job postings are down 42% from their April 2022 peak, per Revelio Labs' tracking of more than 100 million employment profiles, and manager headcount fell 6.1% between May 2022 and May 2025, per Live Data Technologies' analysis, reported by The Wall Street Journal. That coordination work didn't vanish with the layer — it landed on whoever sat structurally closest to the gap: a Chief of Staff, an ops lead, a founder's EA.

The Layer Is Gone. The Work It Did Isn't.

Every "flatter org" announcement gets read as an efficiency win, and on the headcount line, it is one. Fewer manager salaries, fewer approval hops, a cleaner chart to show the board. What that framing skips is that a management layer wasn't just a reporting line — it was a buffer. It absorbed status-checking, cross-team follow-up, and the small negotiations that keep four departments moving in the same direction without anyone above them noticing friction.

Revelio Labs has tracked the middle-management job-posting decline every month since the April 2022 peak, and it hasn't recovered. Live Data Technologies' data, reported by The Wall Street Journal, puts the actual headcount drop at 6.1% over three years. Neither number is a blip, and neither is close to done.

Remove the layer and the org chart looks better immediately. The coordination volume doesn't drop with it. It has to land somewhere, and it lands fast — usually within one quarter, based on what we've seen — on whoever is structurally closest to the gap the layer used to fill.

What 42% Fewer Middle Managers Actually Means on a Tuesday

Numbers like 42% and 6.1% read as abstractions until you watch them hit a specific week. In the two-layer version of the reorg we mentioned, the Tuesday status pull — checking in with four team leads before a leadership update — took two people about 45 minutes combined, split by department. Post-flattening, it's one person, and it now runs closer to two hours, not because the work got harder, but because there's no second person to divide the follow-ups with.

That's the part the 42% figure doesn't capture: the coordination didn't get 42% smaller. It got concentrated. One person is now doing what two were doing, on the same Tuesday, with the same number of Slack threads to close before the update goes out.

This is exactly the gap we built Rhythms' Playbooks to close — the recurring cadence that used to require a manager physically chasing four people now runs on its own schedule, pulling status instead of a person having to ask for it twice.

Where the Coordination Work Actually Lands (It's Not Random)

It doesn't scatter evenly across a team. It lands on whoever already sits at the intersection of the most workstreams — the person the org already routes ambiguous things to, because everyone assumes they'll know who to ask. That's usually a Chief of Staff, an operations lead, or a founder's EA: roles defined by proximity to everything, not authority over any one thing.

The uncomfortable part is that this person rarely gets the layer's old headcount, budget, or title. They get the layer's old job, informally, on top of the one they already had. It shows up as more meetings that "just need someone from your side," more forwarded emails with "can you own this," and a calendar that fills in from the edges first.

We built Rhythms' Reviews around this exact failure mode — instead of one person manually assembling what four former managers used to track separately, the data pulls from where the work already lives, so the person absorbing the coordination gap isn't also the one manually stitching four systems together every week.

The 60% Number Is the Symptom, Not the Root Cause

Asana's 2026 Anatomy of Work research puts "work about work" — status updates, chasing approvals, searching for information — at roughly 60% of the global workweek, with similar figures in the US, UK, and Singapore, each landing between 61% and 62%. That leaves about a quarter of the week for the actual skills-based work someone was hired to do, and roughly 13% for anything resembling strategic planning.

Most coverage treats that 60% as a personal productivity problem — as if the fix is a better calendar habit or a task-management app. It's worth separating the symptom from the cause. The 60% figure is what a labor market with 42% fewer management openings looks like from the inside, measured one person's week at a time. The coordination work didn't get more time-consuming. There are fewer people left to divide it among.

What to Do When You're the One Absorbing a Layer's Worth of Work

If this is landing on you specifically, the instinct is to work faster or get better at triage. Neither addresses the actual mechanism, which is a labor-market shift, not a personal productivity gap. Three things are worth doing instead.

First, name it as headcount math, not a personality trait. "I'm absorbing what used to be two managers' coordination load" is a different conversation with your CEO than "I'm behind." One is a staffing argument. The other sounds like an excuse, even when it isn't.

Second, give the work a visible home instead of letting it live in your head and your inbox. This is the same reasoning behind Rhythms' Radar — surfacing what's off track on day three instead of day thirty, so the gap gets caught by a system watching for it, not by whoever happens to notice first.

Third, make the case with the two numbers that actually explain your week: the 42% decline in management job postings, and the 6.1% drop in managerial headcount. Cited to Revelio Labs and Live Data Technologies, those numbers turn "we're too busy" into a structural argument a CEO can act on — and check.

We don't have a tidy ending for this one. Flatter orgs aren't going away, and the coordination work isn't going back to a management layer that no longer exists. What changes is whether the person absorbing it has a system watching the handoffs, or just a longer to-do list and a good memory. Most Tuesdays, that's the entire difference.

Try for free at rhythms.ai.

Frequently Asked Questions

Why is middle management shrinking in 2026?

Middle-management job postings are down 42% from their April 2022 peak, according to Revelio Labs' analysis of over 100 million employment profiles, and total managerial headcount fell 6.1% between May 2022 and May 2025, per Live Data Technologies' data as reported by The Wall Street Journal. It's a measured labor-market shift driven by flatter-org strategies and cost discipline, not a temporary hiring freeze.

Who absorbs the coordination work when a company removes a layer of management?

Whoever sits structurally closest to the gap the layer used to fill — in practice, usually a Chief of Staff, an operations lead, or a founder's EA. None of them typically inherit the layer's old headcount or budget along with its work.

What percentage of the workweek is spent on "work about work"?

Roughly 60% globally, according to Asana's 2026 Anatomy of Work research, with regional figures around 61% in the US and UK and 62% in Singapore. That leaves about a quarter of the week for skills-based work and roughly 13% for strategic planning.

Is a flatter org chart actually more efficient, or does it just hide the coordination cost?

Both can be true at once. The org chart gets simpler and cheaper on paper, while the coordination cost that used to be spread across a layer of managers concentrates onto fewer people — which feels like inefficiency at the individual level even as headcount costs look better company-wide.

How do you tell if your team is understaffed for the coordination work it's doing?

Look at who the org routes ambiguous requests to by default, and check whether that person's role or headcount changed the last time a management layer was removed. If the work moved and the resourcing didn't, that's the gap — not a productivity problem to solve with better habits.