GitLab Restructuring

 

In May 2026, GitLab announced a major reorganization that will create roughly 60 smaller R&D teams with greater autonomy and end-to-end ownership, while eliminating as many as three layers of management. This episode illustrates a basic tradeoff in organizational design. Larger functional or divisional groups make communication within a specialty relatively easy, but they can create weak incentives and costly communication across organizational boundaries. A programmer might finish her assigned code, for example, while responsibility for whether the overall product actually works belongs somewhere else. GitLab explicitly identifies layers of management and “handoffs that dilute accountability” as problems it wants to eliminate. Putting the people needed to deliver a product into a smaller team gives them greater authority, and responsibility, over the decisions affecting that product.

But organizing around small product teams creates a different communication problem. Engineers working on similar technologies may now sit in different teams, so knowledge that once flowed naturally within a large engineering group must travel across product groups. Teams can also duplicate solutions to common problems or make decisions that work for their product but impose costs elsewhere in the company. GitLab is betting that this tradeoff has changed: it plans to use AI agents to automate some reviews, approvals, and handoffs, while its current development model emphasizes small, cross-functional teams with end-to-end accountability. Organization form depends on which communication problem is more costly. Divisions facilitate coordination among specialists but weaken incentives for the final outcome; product teams strengthen ownership of outcomes but make sharing knowledge and coordinating across products more difficult. GitLab’s restructuring suggests that it now believes the first problem has become more important than the second.