
Sign up to save your podcasts
Or


In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub wrestle with one of the industry's toughest questions: How do you measure engineering productivity?
The conversation explores the hypothesis that deploy frequency per person can serve as a practical proxy for velocity, and the cultural tradeoffs this metric may introduce. Scott and Brad dig into why smaller, more frequent deploys can drive quality, momentum, and stakeholder confidence, while also acknowledging the risks of discouraging big, bold initiatives.
Other highlights include:
A step-by-step playbook for turning around engineering teams
The dangers of vanity metrics (like lines of code)
Why demos beat burn-down charts every time for stakeholder trust
The reality (and rarity) of the 10x engineer
Balancing incremental progress with audacious projects
Selling productivity metrics to non-technical stakeholders
Along the way, Scott shares his favorite demo stories (including an on-demand dog-walking product launch at Rover), while Brad offers candid reflections on how teams can avoid paralysis when faced with large projects.
If you've ever struggled to explain "velocity" to your CEO or wondered whether deploy counts can really measure productivity, this is the episode for you.
Resources:
#TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCtos #Podcast #Ctos #CtoPodcast #Technology #Engineering #SoftwareDevelopment #TechLeadership #EngineeringLeadership #DevOps #Velocity #10xEngineer #EngineeringProductivity #DeployFrequency #CTOlife #DevCulture #AgileLeadership #ProductivityMetrics #TeamVelocity
By Brad Hefta-Gaub & Scott PoradIn this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub wrestle with one of the industry's toughest questions: How do you measure engineering productivity?
The conversation explores the hypothesis that deploy frequency per person can serve as a practical proxy for velocity, and the cultural tradeoffs this metric may introduce. Scott and Brad dig into why smaller, more frequent deploys can drive quality, momentum, and stakeholder confidence, while also acknowledging the risks of discouraging big, bold initiatives.
Other highlights include:
A step-by-step playbook for turning around engineering teams
The dangers of vanity metrics (like lines of code)
Why demos beat burn-down charts every time for stakeholder trust
The reality (and rarity) of the 10x engineer
Balancing incremental progress with audacious projects
Selling productivity metrics to non-technical stakeholders
Along the way, Scott shares his favorite demo stories (including an on-demand dog-walking product launch at Rover), while Brad offers candid reflections on how teams can avoid paralysis when faced with large projects.
If you've ever struggled to explain "velocity" to your CEO or wondered whether deploy counts can really measure productivity, this is the episode for you.
Resources:
#TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCtos #Podcast #Ctos #CtoPodcast #Technology #Engineering #SoftwareDevelopment #TechLeadership #EngineeringLeadership #DevOps #Velocity #10xEngineer #EngineeringProductivity #DeployFrequency #CTOlife #DevCulture #AgileLeadership #ProductivityMetrics #TeamVelocity