Show Notes
In this episode of Engineering Enablement, host Laura Tacho talks with Fabien Deshayes, who leads multiple platform engineering teams at Monzo Bank. Fabien explains how Monzo is adopting AI responsibly within a highly regulated industry, balancing innovation with structure, control, and data-driven decision-making.
They discuss how Monzo runs structured AI trials, measures adoption and satisfaction, and uses metrics to guide investment and training. Fabien shares why the company moved from broad rollouts to small, focused cohorts, how they are addressing existing PR review bottlenecks that AI has intensified, and what they have learned from empowering product managers and designers to use AI tools directly.
He also offers insights into budgeting and experimentation, the results Monzo is seeing from AI-assisted engineering, and his outlook on what comes next, from agent orchestration to more seamless collaboration across roles. Where to find Fabien Deshayes: • LinkedIn: https://www.linkedin.com/in/fabiendeshayes
Where to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/ • X: https://x.com/rhein_wein • Website: https://lauratacho.com/ • Laura’s course (Measuring Engineering Performance and AI Impact): https://lauratacho.com/developer-productivity-metrics-course
In this episode, we cover: (00:00) Intro (01:01) An overview of Monzo bank and Fabien’s role (02:05) Monzo’s careful, structured approach to AI experimentation (05:30) How Monzo’s AI journey began (06:26) Why Monzo chose a structured approach to experimentation and what criteria they used (09:21) How Monzo selected AI tools for experimentation (11:51) Why individual tool stipends don’t work for large, regulated organizations (15:32) How Monzo measures the impact of AI tools and uses the data (18:10) Why Monzo limits AI tool trials to small, focused cohorts (20:54) The phases of Monzo’s AI rollout and how learnings are shared across the organization (22:43) What Monzo’s data reveals about AI usage and spending (24:30) How Monzo balances AI budgeting with innovation (26:45) Results from DX’s spending poll and general advice on AI budgeting (28:03) What Monzo’s data shows about AI’s impact on engineering performance (29:50) The growing bottleneck in PR reviews and how Monzo is solving it with tenancies (33:54) How product managers and designers are using AI at Monzo (36:36) Fabien’s advice for moving the needle with AI adoption (38:42) The biggest changes coming next in AI engineering
Referenced: Monzo The Go Programming Language Swift.org Kotlin GitHub Copilot in VS Code Cursor Windsurf Claude Code Planning your 2026 AI tooling budget: guidance for engineering leaders
More from Engineering Enablement by DX
As AI agents become more capable, context quality is increasingly the limiting factor in their performance. In this episode of Engineering Enablement, DX researcher Brian Houck by his CAFE(S) is joined by co-authors Max Kanat-Alexander (Capital One), Eirini Kalliamvakou (DX), and Margaret-Anne Storey (University of Victoria) to discuss CAFE(S), a new framework for improving context quality. The panelists introduce the five dimensions of CAFE(S): Clarity, Actionability, Fidelity, Efficiency, and Security. They walk through common context failures, how poor context accrues technical and cognitive debt, what it costs in developer productivity and operating spend, how AI is changing the skills engineers need, and why context review could become as important as code review.
Meta researcher Moritz Beller joins Brian Houck to discuss how Meta measures developer productivity. Moritz explains diff authoring time and how Meta uses it to evaluate tools and guide engineering decisions. They explore how AI is changing engineers’ work and revealing gaps in traditional metrics. They also revisit Moritz’s “Mind the Gap” study and discuss the promise and risks of AI agents for testing.
In this episode of Engineering Enablement, Robert Lucero, Chief Architect at Okta, joins host Brian Houck to discuss how agentic AI is changing identity and access management. They explore how organizations should define agent identities, why authentication and authorization remain foundational, and how sandboxing, fine-grained permissions, and just-in-time access can enable agents to operate autonomously without creating unacceptable risk. Robert shares what Okta has learned from driving AI adoption among security-minded engineers, what makes a repository ready for AI agents, and why strong testing, CI, and review processes matter even more as AI generates more code. They also discuss AI’s role in software validation, the need for human judgment, and whether AI will ultimately give the advantage to security teams or attackers.
Max Kanat-Alexander is an Executive Distinguished Engineer at Capital One, where he helps lead developer experience and AI-assisted software development. In this episode of Engineering Enablement, Max joins Brian Houck to discuss how AI is changing software development and why strong engineering fundamentals matter more than ever. They explore how engineering skills are evolving, why AI can amplify weaknesses in the development lifecycle, and how teams should rethink code review, quality, and testing. Max also shares how leaders can assess whether their organizations are ready for more advanced AI workflows and why developing the next generation of senior engineers remains one of the biggest open questions in software engineering.
AI adoption among software developers is approaching 100%, AI-authored code now makes up more than half of merged code, and developers report saving more time with AI every quarter. But those gains aren’t translating evenly into better outcomes. In this episode of Engineering Enablement, host Brian Houck, Distinguished Scientist at DX, sits down with Justin Reock, Deputy CTO at DX, to unpack findings from DX’s latest AI Impact Report. They explore where AI is improving engineering velocity and developer experience, where concerns are emerging around PR size, change confidence, and failure rates, and why rising AI spend has yet to produce a comparable increase in innovation. They also discuss how AI is changing the meaning of code maintainability and where developers’ AI-driven time savings may actually be going.