John Cutler · 6 min read · Product Strategy
TBM 427: The Bottleneck Strike Again!
Read the original on cutlefish.substack.com →
The piece challenges the trendy claim that engineering is no longer the bottleneck, arguing that bottlenecks in product development are distributed, dynamic constraints rather than a single fixed point. It emphasizes that product work involves sensing, deciding, learning, and adapting, and that simple speed fixes rarely address the real, multi-layered friction in complex systems.
Key Takeaways
- Bottlenecks are constraints that shift and interact within a complex system, not a single visible logjam.
- Product work encompasses sensing, deciding, learning, aligning, and adapting—coding is only one part of the equation.
- Simple linear narratives (e.g., faster engineering) overlook systemic factors; theories from Meadows, Juarrero, and Goldratt advocate for distributed constraints and holistic optimization.
- AI can help in certain contexts but is not a universal fix and may introduce energy costs and new complexities; speed gains are not guaranteed by technology alone.
Excerpt
My goodness. If I see another slide with a 2005-era SDLC diagram sprinkled with little AI logos and a bunch of words suggesting “the bottleneck has moved” or that this has all been figured out, when in reality every week there’s something new like Loop Engineering, or _____________. I’m trying to understand why we are so quick to be seduced by the idea that “engineering is no longer the bottleneck.” At this point, it almost feels like the bottleneck has shifted to conversations about how the bottleneck has shifted. As if engineering was ever the bottleneck, or was always the…