
Sign up to save your podcasts
Or


Brian Houck from Microsoft returns to discuss effective strategies for driving AI adoption among software development teams. Brian shares his insights into why the immense hype around AI often serves as a barrier rather than a facilitator for adoption, citing skepticism and inflated expectations among developers. He highlights the most effective approaches, including leadership advocacy, structured training, and cultivating local champions within teams to demonstrate practical use cases.
Brian emphasizes the importance of honest communication about AI's capabilities, avoiding over-promises, and ensuring that teams clearly understand what AI tools are best suited for. Additionally, he discusses common pitfalls, such as placing excessive pressure on individuals through leaderboards and unrealistic mandates, and stresses the importance of framing AI as an assistant rather than a replacement for developer skills. Finally, Brian explores the role of data and metrics in adoption efforts, offering practical advice on how to measure usage effectively and sustainably.
Where to find Brian Houck:
• LinkedIn: https://www.linkedin.com/in/brianhouck/
• Website: https://www.microsoft.com/en-us/research/people/bhouck/
Where to find Abi Noda:
• LinkedIn: https://www.linkedin.com/in/abinoda
In this episode, we cover:
(00:00) Intro: Why AI hype can hinder adoption among teams
(01:47) Key strategies companies use to successfully implement AI
(04:47) Understanding why adopting AI tools is uniquely challenging
(07:09) How clear and consistent leadership communication boosts AI adoption
(10:46) The value of team leaders ("local champions") demonstrating practical AI use
(14:26) Practical advice for identifying and empowering team champions
(16:31) Common mistakes companies make when encouraging AI adoption
(19:21) Simple technical reminders and nudges that encourage AI use
(20:24) Effective ways to track and measure AI usage through dashboards
(23:18) Working with team leaders and infrastructure teams to promote AI tools
(24:20) Understanding when to shift from adoption efforts to sustained use
(25:59) Insights into the real-world productivity impact of AI
(27:52) Discussing how AI affects long-term code maintenance
(29:02) Updates on ongoing research linking sleep quality to productivity
Referenced:
In this episode, we’re joined by author and researcher Gene Kim for a wide-ranging conversation on the evolution of DevOps, developer experience, and the systems thinking behind organizational performance. Gene shares insights from his latest work on socio-technical systems, the role of developer platforms, and how AI is reshaping the shape of engineering teams. We also explore the coordination challenges facing modern organizations, the limits of tooling, and the deeper principles that unite DevOps, lean, and platform engineering.
Mentions and links:
Discussion points:
In this episode, Airbnb Developer Productivity leader Anna Sulkina shares the story of how her team transformed itself and became more impactful within the organization. She starts by describing how the team previously operated, where teams were delivering but felt they needed more clarity and alignment across teams. Then, the conversation digs into the key changes they made, including reorganizing the team, clarifying team roles, defining strategy, and improving their measurement systems.
Mentions and links
Discussion points:
Many teams struggle to use developer productivity data effectively because they don’t know how to use it to decide what to do next. We know that data is here to help us improve, but how do you know where to look? And even then, what do you actually do to put the wheels of change in motion? Listen to this conversation with Abi Noda and Laura Tacho (CEO and CTO at DX) about data-driven management and how to take a structured, analytical approach to using data for improvement.
Mentions and Links:
Discussion points:
In this episode, David Betts, leader of Twilio’s developer platform team, shares how Twilio leverages developer sentiment data to drive platform engineering initiatives, optimize Kubernetes adoption, and demonstrate ROI for leadership. David details Twilio’s journey from traditional metrics to sentiment-driven insights, the innovative tools his teams have built to streamline CI/CD workflows, and the strategies they use to align platform investments with organizational goals.
Mentions and links:
Discussion points:
Chris Chandler is a Senior Member of the Technical Staff for Developer Productivity at T-Mobile. Chris has led several major initiatives to improve developer experience including their internal developer portal, Starter Kits (a patented developer platform that predates Backstage), and Workforce Transformation Bootcamps for onboarding developers faster.
Mentions and links:
Discussion points:
In this episode, Abi and Laura dive into the 2024 DX Core 4 benchmarks, sharing insights across data from 500+ companies. They discuss what these benchmarks mean for engineering leaders, how to interpret key metrics like the Developer Experience Index, and offer advice on how to best use benchmarking data in your organization.
Mentions and Links:
Discussion points:
In this episode, Abi and Laura introduce the DX Core 4, a new framework designed to simplify how organizations measure developer productivity. They discuss the evolution of productivity metrics, comparing Core 4 with frameworks like DORA, SPACE, and DevEx, and emphasize its focus on speed, effectiveness, quality, and impact. They explore why each metric was chosen, the importance of balancing productivity measures with developer experience, and how Core 4 can help engineering leaders align productivity goals with broader business objectives.
Mentions and Links:
Discussion Points:
In this episode, Brian Houck, Applied Scientist, Developer Productivity at Microsoft, covers SPACE, DORA, and some specific metrics the developer productivity research team is finding useful. The conversation starts by comparing DORA and SPACE. Brian explains why activity metrics were included in the SPACE framework, then dives into one metric in particular: pull request throughput. Brian also describes another metric Microsoft is finding useful, and gives a preview into where his research is heading.
Mentions and links
Discussion points
Click here to view the episode transcript.
Mentions and links
Discussion Points
From the publisher's feed

30,689 Listeners

43 Listeners

56,424 Listeners

179 Listeners

34 Listeners

567 Listeners