Episode
BONUS Your Developers Got 20x Faster — Now Watch Your Product Managers' Heads Explode With Clarke Ching
- Published
- May 16, 2026
- Duration seconds
- 2340
- Processing state
not_requested- Canonical source
- https://scrummastertoolbox.libsyn.com/bonus-your-developers-got-20x-faster-now-watch-your-product-managers-heads-explode-with-clarke-ching
Actions
POST https://stenobird.com/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/bonus-your-developers-got-20x-faster-now-watch-your-product-managers-heads-explode-with-clarke-ching/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/bonus-your-developers-got-20x-faster-now-watch-your-product-managers-heads-explode-with-clarke-ching.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
BONUS: Your Developers Got 20x Faster — Now Watch Your Product Managers' Heads Explode Clarke Ching is "The Bottleneck Guy" — and he just spotted the bottleneck that AI is about to create in every software organization. It's not in the code. It's inside the heads of the people who decide what gets built. In this conversation, Vasco and Clarke unpack why speeding up developers with AI tools pushes the real constraint upstream — onto product managers, designers, and leaders — and what to do before cognitive overload crushes the people your organization depends on most. Every Business Has a Bottleneck — Most Are in the Wrong Place "Every single client I have is a detective puzzle. We're looking for this quiet killer sitting inside their business, siphoning off money. And if you look at them without the idea of going 'where's the bottleneck?' — you mistake the busyness for productivity." Clarke approaches Theory of Constraints like a detective story, not a physics lecture. Every business has a bottleneck — the narrowest point that chokes throughput. The question isn't whether you have one, it's whether it's in the right place. In software development, Clarke argues, the bottleneck should almost always be the developers. Not because they're slow, but because they're the pacing resource — like the aircraft carrier in a naval fleet that sets the speed for everything else. When developers are the bottleneck, the people upstream (product managers, designers, architects) have time to curate high-quality, high-value inputs. The people downstream (testers, ops) can deliver fast feedback. Everything flows. But when the bottleneck drifts somewhere else — and nobody notices — everyone gets busy, nothing flows, and the organization mistakes that busyness for productivity. Clarke's lat…