Learning vs. Shipping: John Cutler Questions Development Bottlenecks

In a recent LinkedIn post, John Cutler revisits a question posed nearly eight years ago by Tanner McGrath: “Are you shipping faster than you learn? Or learning faster than you ship?” Cutler uses this timeless query to analyze common perceptions of development bottlenecks, suggesting that the true constraint for many teams lies not in their ability to ship code, but in their capacity to learn.

Cutler reflects on his observations from years past, noting that while the concept of a “shipping bottleneck” is frequently discussed, his experience often pointed to a different primary constraint.

“I remember when Tanner McGrath posed this question almost eight years ago, before AI was capturing everyone’s attention.”

He elaborates on how, even at that time, a significant number of companies he encountered were characterized by a learning bottleneck rather than a shipping one. This observation, Cutler implies, remains relevant even amidst current discussions about development velocity and efficiency.

The Prevalence of Learning Bottlenecks

John Cutler highlights that the notion of a “shipping bottleneck” can be misleading. While teams might feel pressure to deliver features quickly, Cutler suggests that the underlying issue for many is a slower pace of learning and adaptation.

Re-evaluating Development Constraints

As Cutler points out, the focus on shipping speed might distract from more fundamental challenges within development processes. He implies that teams might be capable of producing output but struggle to integrate feedback, iterate effectively, or truly understand the impact of their work.

“This is what gives me pause when people talk about the bottleneck of shipping.”

According to Cutler, this perspective challenges the conventional wisdom that faster deployment cycles are the universal solution to development challenges. He argues that without an equivalent or faster pace of learning, simply shipping more code may not lead to better outcomes or more efficient product development.

“Even then, a majority of teams had a learning bottleneck….not a shipping bottleneck.”

Cutler’s analysis encourages a deeper examination of team dynamics and processes. By posing the question of whether teams are learning faster than they ship, he prompts leaders and teams to consider whether their efforts are focused on the right areas for improvement. The implication is that fostering a robust learning culture might be a more critical factor in achieving sustainable development success than merely optimizing the shipping process itself.