Flatten Your Org Without Breaking Execution: Uber's 3,300-Role Cut

If you are deciding whether to cut management layers before a downturn or an AI-driven productivity shift, Uber's restructuring is a useful test. The company announced the layoffs on September 2, 2026, and CEO Dara Khosrowshahi told employees it had become increasingly complex. Uber is eliminating about 3,300 positions, roughly 10% of its global workforce, in its largest layoff round since the pandemic. The plan is not just a headcount cut. Uber intends to cut manager headcount by about 20%, with some managers shifting to individual contributor roles. The company will trim by 20% the number of workers at least seven levels below the CEO. The plan also nearly halves the number of small teams that have only one or two direct reports. Uber will cap fully remote roles at about 1% of its workforce and keep requiring most employees to be in the office three days a week.

Complexity is the price of added layers

Before you remove a layer, test whether the layer is doing work or just absorbing it. The checklist below turns Uber's plan into a practical audit for founders and operators. Each item should be easy to run, not a long project to justify.

• Map layers from the CEO to every employee, then mark any path that crosses seven or more levels.
• Count managers with one or two direct reports and flag them for review.
• Set a written minimum manager span target for every manager.
• Identify micro-teams that share a product, customer, or deadline and can merge under fewer leaders.
• Cap fully remote roles to the smallest defensible share and require in-office collaboration for the rest.

Depth obscures handoffs, so the map comes first. Thin teams multiply meetings, and remote work can replace the office conversations that flattening needs. The order matters because each step exposes the next.

A wide span needs more than a longer list of meetings. The manager should be able to say what each report owns, what they no longer own, and where the handoff happens. If the answer is fuzzy, the cut will create confusion. Write that answer down before you announce the change.

Micro-teams are easy to create and hard to notice. They often form around a project, a tool, or a concern that the team is too small to matter. When you merge them, keep the merge visible: same goal, same owner, same review cadence. Otherwise you have just changed the name.

Remote exceptions should be rare enough to be meaningful. If every role can stay home, the office becomes optional. When only a few roles can stay home, in-person days become the place where cross-team problems get solved. The cap is a design choice that keeps cross-team work in the office.

Flattening fails when it only cuts people

The previous larger workforce reduction occurred in May 2020, when Uber eliminated about 6,700 jobs. This time, the aim is simplifying the management structure. Founders often wait until revenue pressure forces a cut. It is the wrong time to learn which layers were essential. A quieter moment is better: you can test the new structure, reassign work, and let managers take on a wider span before the next downturn. AI-driven productivity changes make the same argument. If output per person rises, the old number of managers may no longer match the work.

Run the audit before the memo, in the order above. Start with the map. Managers who cannot name the work that disappears when their layer is removed are probably costing more than the role returns. Teams too small to own a result should be merged. Remote work as the default needs an explicit exception. Then test the new chart against the checks before you announce anything.