The AI Jobs Debate is Not Asking the Right Question

In May, Meta laid off roughly 8,000 people, about ten percent of the company, in a restructuring built around AI. The memo called the cuts the price of leading the most consequential technology shift of our lifetimes. Six weeks later, at an internal town hall on July 2, Mark Zuckerberg told employees that AI agent development “hasn’t really accelerated in the way that we expected.” The reorganization had been messier than planned, he said, and the benefits should arrive in three to six months.

Be precise about what he conceded. He did not say the layoffs were a mistake. His chief AI officer quickly clarified that he meant the whole industry’s progress on agents, not Meta’s alone. Take that at face value. It makes the admission bigger, not smaller. A whole industry restructured its workforce around an acceleration that one of its most aggressive adopters now says is running late. Meta may just be the first to say so out loud.

Every story like this feeds the same debate, and two chief executives sit at its poles. In May, Matthew Prince of Cloudflare wrote in the Wall Street Journal about how he decides which employees to replace with AI. He had just cut more than a fifth of his workforce. Days later, in the New York Times, Goldman Sachs chief David Solomon took the optimist’s side. Yes, AI will disrupt the labor market, he wrote, but America absorbed electrification and the digital revolution before it, and new work will emerge as it always has. One CEO sees replacement beginning. The other sees the economy adapting, as it always has. Both may be right. Both are missing the bigger problem.

AI is not just a labor story

The debate treats AI as a labor substitute. But what AI is really collapsing is the cost of execution, the cost of doing things. Build a workflow, analyze a dataset, draft a document, run a process. Each of these once took real expertise and real time. Now each one takes a goal and an instruction.

When execution gets cheap, the constraint moves. What becomes scarce is not the ability to do things. It is the ability to do them coherently. A company now runs on hundreds of autonomous systems. Keeping them pointed at compatible goals is the hard part. So is making sure the people who answer for the results still understand what they have built well enough to govern it.

That is the inversion neither side of the jobs debate has named. AI is not primarily a labor story. It is a coordination story.

And the people living it already feel the difference. In a 2026 survey of 1,200 executives, more than half, 54 percent, said adopting AI was tearing their company apart. In the same survey, 79 percent said AI applications were being built in silos, and more than a third admitted they could not immediately shut down a misbehaving agent. Those are not complaints about weak models. They are the sound of an organization losing its coordination, not its labor.

Prince’s own reasoning shows why. He built the Cloudflare cuts on a framework from Peter Drucker: every company has builders, sellers, and measurers. AI can now measure cheaply and continuously, work that used to take a lot of people. So the measuring layer can shrink, and the savings can move to the roles that create value. The logic is clean. That is what makes it worth examining, because it rests on one quiet assumption. It assumes the people labeled measurers were only measuring.

In most companies they were not. The person who tracks a process is often the one who notices when it breaks. She knows why it was built that way. She catches the exception the dashboard misses. Cut her as redundant measurement, and you may find you also cut a layer of coordination you never had a name for. Did Cloudflare make that mistake? I cannot say from outside. The point is that the framework cannot even see the question. Neither can the jobs debate it belongs to.

Anticipation, not implementation

The labor story is mostly theater anyway, and the evidence says so. In a survey of more than a thousand executives, 21 percent had made big cuts in anticipation of AI. Only 2 percent tied cuts to AI they had actually deployed. That is a tenfold gap between the future they were cutting for and the present they were living in. New York State added a box to its mass-layoff filings asking whether automation drove the cuts. In the first full year, almost no employer checked it.

The research points the same way. AI’s real effect on jobs shows up in slower hiring, not firing. And that is the quiet danger. According to Accenture’s last Pulse of Change survey, 59% believe young professionals are having a harder time finding jobs due to automation and AI. Juniors who never get hired are the seniors an organization will lack in ten years. The pipeline gets cut without anyone announcing it.

The layoffs are running ahead of the plans that would justify them. In that same 2026 survey, 69 percent of companies were planning AI-related layoffs, yet 39 percent had no formal strategy to earn revenue from the AI they were adopting. Cutting first and figuring out the value later is not a strategy. It is a bet on an acceleration that has not shown up.

Read Meta’s year through that lens. The company cut in anticipation of an acceleration. The acceleration is the very thing its CEO now says has not arrived on schedule.

The oldest instinct in the room

I have seen the underlying mistake before, long before agents existed. Early in the data science era, I sat down with a business unit head to discuss where machine learning could help. Her opening move was to hand me an enormous dataset and ask me to figure out something useful from it. I was the data geek. That was my job.

Capability first, purpose later, is analysis unmoored from the business, and it goes nowhere.

It took several more conversations before the team came around to a different starting point: begin with a business outcome, then work backward to the analysis. Capability first, purpose later, is analysis unmoored from the business, and it goes nowhere.

That instinct never went away. What changed is the friction that used to hold it back. Back then, a capability-first project cost a quarter of work and a real budget. When it produced nothing, it died quietly in a slide deck. Today the same instinct ships an autonomous system into production in an afternoon.

And those systems do not sit still. An agent built for escalations spins up sub-agents to handle edge cases, each with its own logic and even less context than the first. A finance agent reaches for new data sources and builds a picture of the company no human has checked. Every step is reasonable on its own. Nobody approved the whole. The organization did not design this. It just failed to prevent it.

This is how the burden I wrote about last week, complexity debt, actually accumulates: not through failure, but through hundreds of local successes that nobody is coordinating. The old friction was never just cost. It was an accidental governance system. AI removed it without replacing it.

Why the reorganization wasn’t clean

There is also a well-documented reason Zuckerberg’s three-to-six-month promise should be read skeptically, and it has nothing to do with model quality.

Economists Erik Brynjolfsson, Daniel Rock, and Chad Syverson found that big general-purpose technologies follow a productivity J-curve. Early on, measured productivity actually dips. The technology demands a lot of hidden investment first: new processes, new roles, new organizational wiring. That work is real, but it does not show up on the books. The gains come later, once the work is done. It happened with electricity. It happened with computing.

A plan that waits for the models to improve, instead of doing the coherence work, is a plan to sit at the bottom of the J.

For agentic AI, that hidden investment is coherence. It means shared context across systems, wiring the organization can still read, and a clear human owner for every autonomous system. This is organizational work. No model release does it for you. A plan that waits for the models to improve, instead of doing the work, is a plan to sit at the bottom of the J.

This makes the shape of Meta’s cuts worth a pause. Reporting at the time said the layoffs fell hardest on integrity, cybersecurity, and content design, while AI infrastructure and monetization teams were spared. I do not know Meta from the inside, and I will not pretend to. But the pattern raises the question every executive should ask before this trade: how much of what looks like overhead is actually the coordination layer? Cut the people who do the quiet coordinating work, then multiply the systems that need coordinating, and the J-curve does not get shorter. It gets deeper.

What actually closes the gap

History suggests where this leads. Industrialization created coordination problems, and operations management grew up to solve them. Software created questions no engineer or salesperson owned, and product management, data science, and UX design each emerged to answer one. The pattern repeats every time. The new function is dismissed as redundant, then treated as essential, then made table stakes once the companies that built it start winning. The doubters never look wrong until the results come in.

Even the optimists can see the first outline of it. Solomon, arguing that new jobs will emerge, names one. Companies are already hiring people to manage agentic AI, he writes, across implementation, workflows, compliance, and validation, and all of it takes human judgment. He is right. The role is real and growing. Some in the industry are calling it the agent manager, the person who runs a fleet of agents inside one function. Tellingly, the good ones tend to come from the business being automated, not from tech. Forward deployed engineers, brought in to install and tune the systems, are the other half of the early response.

Both are real. Both are also operators, and this is where Solomon stops one step short. An agent manager’s view ends at the edge of the fleet. The support agent manager watches the support agents. The procurement agent manager watches the procurement agents. Each starts and ends the day inside their own dashboard. Nobody is accountable for whether those fleets are working from the same assumptions about the same customer.

An enterprise can staff every function with an excellent agent manager and still have no one whose job is the coherence among them.

That cross-cutting question is invisible from inside any single fleet, and it is the one that goes unowned. An enterprise can staff every function with an excellent agent manager and still have no one whose job is the coherence among them. This is already biting. In a 2026 survey of 621 enterprise leaders, 42 percent said the lack of a clear internal owner had directly delayed an agentic project in the past year. The gap is not theoretical. It is on the calendar, slowing things down right now.

The obvious response is to add a governance layer: a committee that reviews what the machines produce, a stack of approvals, more people whose job is to sign off. That instinct is backward.

Be careful here, because the obvious response is the wrong one. The obvious response is to add a governance layer: a committee that reviews what the machines produce, a stack of approvals, more people whose job is to sign off. That instinct is backward. It is the old apparatus of permission applied to a problem it was never built for, and it cannot keep pace with systems that deploy in an afternoon.

The goal is to build coherence into how the organization is wired, not to post humans at every intersection to hold it together by hand.

The book argues the real work is structural, and it comes first. Before any new role, an organization has to build the infrastructure to see its own systems, to contain them so trouble in one place stays in one place, and to set in advance how much any system is allowed to decide. Most of that is design work, done once and maintained, not review repeated forever. Increasingly the systems do the watching themselves. The goal is to build coherence into how the organization is wired, not to post humans at every intersection to hold it together by hand. An organization that stays coherent through sheer vigilance is coherent only for now, at a cost that does not scale, one lapse of attention from a mess.

Only on top of that structural work does a human role make sense, and it is a smaller thing than a new bureaucracy. It resolves into a handful of capabilities, each one rhyming with a profession we already know. Someone has to decide how the organization’s own systems should fit together, which ones may depend on which, and where the lines between them run. That is product management, turned to face inward. Someone has to establish which systems can be trusted, for what, on your actual work, based on real, measured data. That is what an analytics team does, applied to AI. Someone has to design the moments where a person hands a decision to a system and takes it back. That is akin to UX, pointed at the inside of the company, designing the interfaces between human and machine. And someone has to own all of this close to where the systems are built, while still answering to a view of the whole. That is the embedded finance officer, in a new setting.

In each of these the machines do more of the work every year. What does not pass to them is the judgment about what the organization should permit, and who answers when it goes wrong.

That is the real shift. The job is not to build AI, and it is not to approve it. It is to build the structure that lets an organization gain from what AI does for it, and hold together while it does.

The question that matters

The jobs debate will continue, and it should. Displacement is a genuine human and economic concern. But the debate is incomplete. It asks what AI replaces. The more urgent question is how to manage the complexity AI creates, and whether organizations will recognize that need before the debt comes due.

Zuckerberg has put a clock on Meta’s answer: three to six months. I read that clock differently. It is not set by the next model release. It is set by how fast a company can do the unglamorous work of staying coherent while it automates. That work is what my book, Coherence, is about, and I will keep working through it here in the open. The one-page tool I use to start is the first thing I send when you join the list at coherise.com.