Why Chinese Big Tech Is Flattening Management Layers

Flattening is appearing in several forms

Recent public reporting and internal-channel signals describe fewer numeric levels, removed manager nodes, broader reporting spans, functional teams moving into business units, and senior specialists returning to individual-contributor roles. These actions share a goal: shorten the route from a customer or technical problem to a decision.

They should not all be called layoffs. Some remove titles without removing jobs; some redistribute management work; others accompany real contraction. A useful analysis asks which decision rights, staffing responsibilities, and support functions changed.

AI changes the economics of coordination

AI tools reduce the cost of drafting, analysis, coding, testing, and documentation. That makes smaller teams more capable and weakens the case for some coordination-only layers. Public commentary on AI-native organizations and company engineering cases both emphasize higher individual leverage.

But coordination does not disappear. Decisions about architecture, priorities, conflicts, hiring, performance, and incidents still require accountable owners. If a company removes a layer without redesigning those decisions, the work moves invisibly to senior leaders or individual contributors.

Wider spans are not automatically more efficient

A manager with more direct reports can receive information faster, but has less time for each employee. The model works best when teams have clear goals, strong operating data, standardized tools, and experienced contributors who need little day-to-day coordination.

It works poorly when the work is ambiguous, junior-heavy, or dependent on negotiation across functions. In those environments, removing middle management can lengthen queues because every exception rises to the same senior person.

Business-unit embedding trades speed for consistency

Moving frontend, testing, algorithms, or platform specialists into business units can improve local priorities and end-to-end ownership. The trade-off is that each unit may reinvent standards, procurement, data definitions, and career ladders.

The more durable design keeps shared technical standards and communities of practice while assigning product outcomes locally. This is a matrix even when the organization chart pretends to be simple.

How to tell redesign from cost cutting

The announcement language is rarely enough. Readers should watch the next quarter: whether decision time falls, whether senior leaders become accessible, whether engineering quality holds, and whether managers who lose teams receive meaningful specialist paths.

A successful flattening makes ownership more legible. A weak one merely reduces formal nodes while leaving approvals, meetings, and uncertainty intact.

• Count decisions and handoffs, not just hierarchy levels.
• Track manager span and employee access to coaching.
• Check whether shared standards survive business-unit embedding.
• Compare cycle time with defects and employee turnover.