The middle management crisis nobody's preparing for

The Switchboard Is Empty

In 1950, there were roughly 350,000 switchboard operators in the United States. Their job was simple and essential: you picked up the phone, told them who you wanted to talk to, and they physically connected your wire to the right socket. Every call in the country passed through a human being sitting at a board, making the connection by hand.

By 1980, the job was nearly gone.

Not because the operators were bad at it. Not because a machine did it cheaper. But because direct dialing made the connection automatic. The call still happened. The conversation still happened. The complexity that required a human in the middle simply evaporated.

Nobody replaced the switchboard operator. The world just stopped needing one.

I think about this a lot when I look at how product teams are structured today.

The coordination layer had a reason to exist. That reason is shrinking.

For the last fifteen years, the standard product team has worked like this: a PM talks to stakeholders and translates business needs into requirements. A designer translates requirements into interfaces. An engineer translates interfaces into code. And somewhere in between, a layer of people exists whose primary job is making sure all that translation doesn't break down.

Project managers. Scrum masters. Team leads. Program managers. People whose calendars are a mosaic of alignment meetings, status syncs, dependency check-ins, and "quick chats" that are never quick.

I've been that person. I've also managed that person. And I want to be honest about something: most of the complexity that justified these roles was artificial. It existed because the gaps between disciplines were wide enough that someone had to stand in them and direct traffic.

The PM couldn't see what the designer was building in real time. The designer couldn't understand why engineering estimated eight weeks for something that "looked simple." The engineer couldn't talk to the customer without three layers of context. So we hired people to carry context across these gaps. Meeting by meeting. Slide by slide. Jira ticket by Jira ticket.

That was a reasonable solution to a real problem.

But AI is closing the gaps.

This isn't about AI replacing managers. It's quieter than that.

Here's where the conversation usually goes sideways. Someone says "AI will replace middle managers" and the entire room gets defensive. That framing is wrong, and it lets people dismiss the real shift.

AI isn't replacing managers. It's removing the friction that made management necessary at the scale we built it.

When a PM can prototype a working concept in an afternoon, they don't need a two-week design cycle to see whether the idea has legs. That's one alignment meeting gone. When a designer can ship a functional feature without waiting for an engineering sprint, that's one project manager's dependency map that just got simpler. When an engineer can synthesize customer feedback using AI tools instead of waiting for the research team's quarterly report, that's one status sync that doesn't need to happen.

None of these changes "replace" a manager. Each one just removes a tiny piece of the complexity that the manager was hired to coordinate. Remove enough pieces and you're left with someone whose calendar is still full but whose impact has quietly hollowed out.

I worked with a team once where the project manager was genuinely talented. Organized. Respected. Good with people. But as the team adopted better tools and the PM started prototyping directly with engineering, the project manager's role slowly shifted from "the person who makes things happen" to "the person who documents that things happened." Nobody said anything. The standups continued. The sprint reports still landed in inboxes. But everyone in the room could feel the change.

The switchboard was still staffed. The calls just weren't coming through it anymore.

The identity crisis is the real crisis.

Here's what makes this different from other "AI and jobs" conversations. When AI automates a task, like writing a first draft or generating test cases, the person can learn a new task. That's adaptation. It's uncomfortable but manageable.

But when AI removes the complexity that justified your role's existence, that's not a task problem. That's an identity problem.

A lot of middle managers I've known, including past versions of myself, built their professional identity around being indispensable connectors. The person who "knows where all the bodies are buried." The person who can get the VP on the phone. The person who translates between engineering and design so that neither side has to learn the other's language.

That identity felt earned. And it was. The problem is that "earned" and "still necessary" are not the same thing.

The switchboard operators of the 1950s were skilled. They memorized hundreds of local numbers. They could connect a call faster than any machine of that era. They were genuinely good at their jobs.

Their skill was never the question. The question was whether the world still needed a human in that particular seat.

What actually survives.

I want to be clear about what I'm not saying. I'm not saying management doesn't matter. I'm not saying leadership is obsolete. I'm not saying you should fire your project manager on Monday.

What I am saying is that the version of middle management that exists primarily to coordinate information between specialized silos is running on borrowed time. The silos are collapsing. The information is flowing faster and more directly. The gaps are narrowing.

The managers who will thrive are the ones who were never really coordinators in the first place. They were decision-makers. Mentors. People who could look at a messy situation and say "here's what we're actually doing and here's why." People whose value was judgment, not logistics.

But if your primary contribution to a team is making sure information gets from Point A to Point B, and AI is making that transfer automatic, the honest conversation to have with yourself isn't "how do I protect my role." It's "what else am I capable of?"

That's not a comfortable question. But it's a more useful one than pretending the switchboard still needs you.

The calls are still happening. The connections are still being made. The work is still getting done.

It's just routing itself now.