Which jobs does AI actually take first?

It takes the coordination layer first, not the front line. The roles thinning out fastest are not the people writing the code, closing the sale, or running the machine, but the managers whose day was assigning, monitoring, summarizing, and reporting on that work. Gartner predicted that through 2026, 20 percent of organizations will use AI to flatten their structure and eliminate more than half of current middle management positions. The reason is plain: scheduling, status reports, performance dashboards, and approval routing are exactly what a model does well, and they were most of what a coordination layer did all day.

Is this already happening at real companies?

Yes, and it started at the top of the market before the AI wave was obvious. In a September 2024 memo, Amazon CEO Andy Jassy set a target to increase the ratio of individual contributors to managers by 15 percent by the first quarter of 2025, explicitly to strip out management layers. Reported AI-linked workforce reductions ran past 150,000 roles in 2026. Across 2025 and 2026, companies including Intel and Google cut management headcount specifically: Intel set out to eliminate management layers, and Google reduced its manager, director, and VP roles. The pattern is consistent: the builders stay, the people who used to route information between them do not.

Why should an owner or family office care about this distinction?

Because the coordination layer was not only overhead; it was also where institutional knowledge, judgment under ambiguity, and quiet relationship management lived. A dashboard can reproduce the reporting. It cannot reproduce the manager who knew which client was about to leave and why. If you flatten the structure without naming where that judgment now sits, you have not saved cost. You have moved an unowned risk one level up, into your own calendar.

What should a leader do about it?

Decide deliberately which parts of the middle layer were overhead and which were judgment, before a vendor or a quarterly cost target decides it for you. Keep and elevate the judgment, automate the routing. Most organizations are doing the reverse by accident: they cut on cost and discover the judgment is gone only when something breaks. Treat the org chart as an attack surface of its own, and decide where accountable judgment lives once the routing is automated. Servola advises on AI risk and governance for owners weighing exactly this.