Developers and operators have long debated how to move code from commit to customer. A new podcast episode from Heavybit’s James Governor, Heidi Waterhouse and Adam Zimman argues that the missing piece is a Third Loop—the feedback that comes from actual users. Naming this loop gives teams a concrete target.

The hosts trace the idea back to Microsoft’s progressive rollouts, where feature flags, canary releases and dark launches kept blast radius small. They call this collection Progressive Delivery, a name that signals a mature CI/CD practice built on feature toggles, observability and staged exposure.

The podcast’s title, *The Third Loop*, signals a shift beyond deployment. The hosts argue that the final barrier lies between developers and end users. By capturing usage data and listening to feedback, teams can close the gap and deliver software that actually satisfies real needs.

Heavybit’s episode underscores that naming practices matters because it unites teams around a shared vocabulary. As software permeates every domain, designers and operators must coordinate with non‑technical users to iterate quickly. The discussion concludes that without a third loop, releases risk becoming silent, unvalidated changes that never reach their intended audience.