Better software faster
summary
A concrete checklist: adopt the Core 4 (speed, effectiveness, quality, impact) with the provided survey template and benchmarks, measure developer friction with the DXI (14 drivers) and expect DXI increases save 13 minutes/week per developer, track AI under three lenses—utilization, impact, cost—and report developers save 3.75 hours/week on average; cite customers who used Core 4 (Dropbox, Block, Booking.com), the saved-hours claims (Block 500,000 hours, Booking.com 150k hours) and show which investments actually moved those numbers.
AI-written summary · about
chapters (14)
- 0:00AI and disappointment gap
- 1:05AI hype misleading leaders
- 3:58Antidote to AI hype is data
- 6:49Developer time savings with AI
- 7:52Leaders must educate stakeholders
- 11:03AI accelerates fundamentals
- 12:25DX Core 4 framework
- 14:09Developer experience and friction
- 16:37Deploy Core 4 framework quickly
- 18:23Measuring AI impact with framework
- 20:55Booking.com’s AI metrics success
- 21:59Leading with data in change
- 22:41Next steps to avoid gap
- 23:44Key leadership questions
related talks
47mTransforming Developer Experience: A Tale of Recovery & Innovation
43mMeasuring Developer Productivity: The Good, the Bad and the Data
13mDeveloper Satisfaction = Better Code | Here's Why
10mAchieving engineering velocity by optimising developer experience
38mHow to Build Better Developer Platforms
27mDevelopers Expose What's Breaking Productivity in Their Companies
34mBuilding a Culture For Developer Productivity
58mDeveloper Joy – How Great Teams Get S%*t Done