Delayering Changes Who Carries the Coordination Work

On September 2, 2026, Uber told employees it was changing the structure of the company. The plan would reduce the team by about 10 percent, reduce roles focused primarily on coordination, broaden manager scopes, cut the number of employees seven or more layers from the CEO by 20 percent, and reduce one- or two-report teams by nearly half. Uber said the changes were intended to produce clearer ownership and faster decisions (Uber employee memo).

The announcement described a specific structural intervention. It also raised a question that an org chart cannot answer.

Who carries the translation, escalation, policy interpretation, and cross-functional judgment that used to sit inside the removed roles?

A company can delete a reporting line on a set date. The decisions embedded in that line continue to enter planning cycles, customer commitments, resource choices, and delivery disputes. Delayering changes who carries that work. The operating consequence depends on where the work goes and whether authority moves with it.

A reporting line can disappear before its decisions are reassigned

Management roles contain more than direct reports and approval steps. They often hold the context that connects one function's decision to another function's consequence.

A manager may know why a customer promise was structured a certain way. They may translate a regional constraint for a central team, decide when standard policy fits the situation, or settle a tradeoff between cash protection and delivery timing. Much of this work is visible only when the answer is missing.

That creates a design problem during delayering. The organization can reassign tasks and still leave consequential decisions without a durable route. Finance retains control of spending. Operations retains control of delivery. Sales retains the customer relationship. The removed role may have been the place where those interests became one company decision.

The chart becomes simpler as soon as the box is removed. The operating system changes only when each consequential decision has a new carrier, sufficient authority, and backup coverage.

Coordination changes carrier

Coordination work usually moves into one or more of four places after a structural change.

An explicit role. A person receives the responsibility and the authority to resolve the decision.
A rule or system. Written criteria, workflow logic, or a shared record handles work that previously required interpretation.
A recurring forum. The decision moves into a meeting or review process where several roles contribute and one role closes it.
An informal broker or delay. A well-connected operator reconstructs the answer, or the work waits until someone with enough history intervenes.

All four can appear inside the same reorganization. Routine approvals may move into a system while unusual requests move to a senior operator. A weekly meeting may settle priorities while customer commitments still depend on private messages. The redesign succeeds in one part of the work and remains incomplete in another.

This is why headcount, span of control, and layer count are incomplete measures of operating change. They show where positions moved. They do not show where judgment, access, escalation, and final authority now reside.

Fewer routes can feel faster

A structure with fewer approval steps can move quickly during ordinary work. Fewer people touch the decision. Questions converge on someone who understands the dependencies. The team spends less time circulating the issue.

That speed may come from a durable route. It may also come from concentration.

The distinction matters because concentration can look efficient while the key operator is available. Colleagues know whom to contact. The operator remembers the history, has the system permissions, and can persuade several functions to move. Repeated access to that person becomes the process.

The same pattern can appear in a smaller company after staff reductions. Recurring tasks are redistributed. People extend hours and learn adjacent work. Status reports, scheduling, and standard customer communication continue. One experienced operator still holds the reasoning behind earlier commitments and the authority to change them.

Task coverage expands. Decision coverage narrows.

This smaller-company pattern is separate from the Uber record. It illustrates the general mechanism: work can continue while the structure becomes more dependent on one person's context and judgment.

Strong performance leaves the structural question open

Uber announced the changes after reporting second-quarter revenue of $14.2 billion, up 12 percent year over year, and GAAP income from operations of $1.9 billion, up 30 percent (Uber Q2 2026 results).

That context matters. The restructuring was presented as a deliberate operating choice inside a growing, profitable company, rather than an announcement explained only by immediate financial distress.

Strong results still cannot establish where the removed coordination functions went. Financial performance can coexist with several structural realities. Uber may have reassigned decisions to broader managers, encoded work into systems, merged authority under single owners, or concentrated more judgment in fewer senior roles. The public documents do not provide enough evidence to choose among those outcomes.

The appropriate conclusion is bounded. Uber announced a significant reduction in layers, small teams, and coordination-focused roles. It stated the intended result. The internal distribution of context, authority, and continuity remains outside the public record.

Speed and continuity answer different operating questions

Operating speed asks how quickly the organization can reach and execute a decision today.

Continuity asks whether the organization can reach the same decision when a particular person is absent, a customer request falls outside the usual route, or two functions hold competing priorities.

A redesign can improve the first measure and weaken the second. That happens when fewer people participate in the decision but more of the required history, access, and judgment sits with one person.

The difference becomes visible under a change in conditions. A standard request follows the workflow. An unusual request requires interpretation. A routine commitment moves on schedule. A contested commitment requires someone who can choose which consequence the company will accept.

Those moments reveal whether coordination became part of the new architecture or remained attached to an individual.

The public record leaves the outcome open

Uber's memo offers unusually specific evidence about the structural changes themselves. It identifies reductions in overall staffing, deep reporting chains, small teams, and roles centered on coordination. It also identifies the intended operating result.

The record stops before the decision inventory behind the removed roles. It leaves permissions, broader authority, encoded processes, and remaining dependence on informal judgment unobserved.

Those unanswered questions are the substance of the operating redesign.

Delayering is structurally complete when consequential decisions have a durable carrier, the carrier has enough authority to resolve them, and another person or system can preserve the route during an absence. Without those conditions, the org chart records fewer layers while the company depends more heavily on whoever remembers how the pieces fit.