Engineering Enablement by DX

Research briefing with Brian Houck: Measuring AI agents and revisiting the Core 4

· Summarized

Share this episode
Anyone with this link can open it.
Share Link
Start at 0:00

Key takeaways

  • Agent experience is an extension of developer experience, focusing on how AI agents are integrated and supported within engineering workflows.
  • Improving agent experience involves platform-level guardrails, clear context, accurate data, shared prompts, and fostering a culture of psychological safety.
  • Traditional metrics like PR throughput and token counts need reinterpretation in the AI era, emphasizing outcome-based measures such as the DX Core 4 and 'idea to customer'.
  • Measuring and supporting organizational readiness requires attention to tooling, culture, infrastructure, and context quality. Leadership advocacy and social proof are vital for AI adoption.
  • Avoid reliance on single metrics; instead, triangulate multiple measures to understand technology impact, system health, and value creation.
  • Documentation quality remains critical. Automating and maintaining up-to-date docs can significantly enhance AI and developer efficiency.
  • Psychological safety is crucial to mitigate burnout and AI-washing fears, ensuring sustainable long-term AI adoption and developer well-being.
  • Ongoing research will continue to refine how we measure and optimize both developer and agent experiences in the evolving AI landscape.

Summary

Introduction and Context of the Discussion

Justin Riyak introduces the podcast episode and highlights the evolution of the conversation around developer experience over nearly five years. He emphasizes how recent advancements, particularly in AI, have shifted the focus towards agent experience and the need to measure this emerging domain effectively. The episode sets the stage for a deep dive into the intersection of developer productivity, AI fluency, and the tools that support these efforts.

Understanding Agent Experience as a New Research Area

Brian Houck explains the concept of agent experience as an extension of developer experience, focusing on whether AI agents have the optimal environment to perform their tasks. He discusses how agent experience encompasses clarity of requirements, data accuracy, and the ability for humans and agents to collaborate effectively. The importance for engineering leaders to care about this area lies in the fact that poor agent setup can hinder human productivity, making it crucial to measure and improve the collaboration and conditions around AI agents.

Improving Agent Experience at the Platform Level and Its Interplay with Developer Experience

The speakers explore ways to enhance agent experience by applying principles similar to those used in traditional developer experience—defining it, measuring it, and iterating improvements. They highlight key factors such as clear and unambiguous context, data validation, shared prompts, and the importance of platform guardrails. There is also a discussion about how improvements in agent experience benefit human developers and the significance of platform-level protections to ensure effective and predictable AI behavior.

Relationship Between Developer and Agent Experience; Impact on Long-term Outcomes

The discussion delves into the complex relationship between developer experience and agent experience, emphasizing how they are interconnected and increasingly inseparable. They consider research findings indicating a paradox where AI makes developers feel more productive but also leads to a decline in overall developer experience. This highlights the need to measure and optimize both, as improvements in agent experience can positively influence overall productivity while avoiding negative impacts like burnout or decreased code quality.

Preparing Engineering Teams for AI-Driven Work and Measuring Success

Attention shifts to organizational readiness for AI and agents, emphasizing three layers: tooling, culture, and infrastructure. Cultural readiness, including leadership advocacy, training, and social proof, is identified as the most impactful for adoption. Infrastructure involves measurement and feedback loops to gauge progress. The conversation underscores the importance of managing expectations and fostering psychological safety, along with developing metrics such as documentation quality, PR size, token usage, and the innovative 'idea to customer' measure, to evaluate AI's impact effectively.

Reinterpreting Metrics in the Age of AI and the Core Four Framework

Brian Houck discusses how traditional metrics like PR throughput remain relevant but need reinterpretation in the AI context. He advocates for a focus on outcome-oriented outcomes—like the DX Core 4 (speed, effectiveness, quality, business impact)—and stresses that diagnostic metrics should adapt to new patterns of work and AI involvement. He warns against relying solely on input metrics like token counts, emphasizing triangulation with broader outcome and system health metrics.

Evaluation of Token Usage and Proposed New Metrics for AI Impact

The podcast explores the limitations of token usage as a metric, deeming it primarily a cost indicator rather than a reflection of productivity or quality. They propose focusing on higher-level metrics like 'idea to customer' to assess the true flow of value, advocating for cross-referencing cost metrics with outcome data. The conversation also emphasizes avoiding gaming of metrics like PR size and underscores the importance of holistic, multiple-metric approaches.

Audience Questions and Final Thoughts on Documentation, Psychological Safety, and Future Research

The hosts respond to questions about keeping documentation up to date, noting its crucial role in onboarding and efficiency, especially for AI. They highlight ongoing research to automate and improve documentation practices. The topic of psychological safety is discussed in relation to AI-induced layoffs and burnout, emphasizing the importance of transparency and leadership support to foster a healthy work environment. Brian shares upcoming research plans on agent experience, further exploring how organizations can optimize human-AI collaboration.

Sponsors

  • GetTheX.com · Learn more about the AI measurement framework, a research-based set of metrics designed to help you understand the impact AI is having on engineering productivity. To learn more and how to apply it, head over to GetTheX.com/AI-Framework.

Show notes

AI coding agents are changing how software gets built, but they're also forcing organizations to rethink how engineering effectiveness is measured. Traditional developer experience metrics were designed for humans, not AI agents, so how should engineering leaders adapt?

In this webinar, Justin Reock, Deputy CTO at DX, is joined by Brian Houck, Distinguished Scientist at DX and co-author of the SPACE framework, to explore the emerging field of agent experience and how it builds on developer experience rather than replacing it. They discuss how organizations can prepare for AI-assisted software development, how the DX Core 4 applies in the age of AI, why metrics like token usage and PR throughput don't tell the whole story, and the growing importance of documentation. They also examine the impact AI-driven pressure is having on burnout and cognitive overload.

Throughout the conversation, they share practical guidance for building engineering organizations where both developers and AI agents can do their best work.


Where to find Brian Houck: 

• LinkedIn: https://www.linkedin.com/in/brianhouck


Where to find Justin Reock:

• LinkedIn: ⁠https://www.linkedin.com/in/justinreock⁠


In this episode, we cover:

(00:00) Intro

(01:26) Justin’s new role at DX

(03:53) What agent experience is and why engineering leaders should care

(08:55) How to improve agent experience at the platform level

(11:25) How agent experience and developer experience influence each other

(14:41) Preparing engineering teams for agentic work

(21:38) Why the DX Core 4 still matters in the age of AI

(27:23) What PR throughput actually measures 

(32:47) The limits of token metrics

(37:10) What the data shows about documentation and developer experience

(39:32) Improving documentation for AI agents

(40:43) AI-washing, burnout, and cognitive overload

(45:35) Brian's upcoming research on agent experience


Referenced:

• DX Core 4 Productivity Framework

• The SPACE of AI | Queue

• Sara Chizari on LinkedIn

• The Middle Loop - Annie Vella

• gastownhall/gastown: Gas Town - multi-agent workspace manager · GitHub

• DORA, SPACE, and DevEx: Which framework should you use?

• AI Impact Report: Q1 2026

• AI-authored code has nearly doubled, but so has PR size 

• EngThrive: Make It Fast and Easy to Do Great Work: Building a durable model for outcome-oriented engineering measurement

• Google's Project Aristotle - Psychological Safety 

• Zapier

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account

Couldn't load the audio. A blocker may be stopping the show's tracking links. Open the file