Achieving engineering velocity by optimising developer experience
summary
Claims incremental improvements increase productivity by an order of magnitude and backs it with a LinearB benchmark over 2,000 organizations and 3.5 million PRs that finds the average org spends 15% of effort on developer experience. Recommends five indicators: top‑level investment, predictability, team bottlenecks, manager-level visibility and culture. Calls out concrete metrics — coding time / review time / deployment time — working agreements, WIP and burnout signals, surveys for quick qualitative checks, and self‑service tooling to let developers act.
AI-written summary · about
related talks
36mDeveloper Productivity Engineering: What's in it for me?
44mEnhancing the Performance of Engineering Teams
35m"DevOps Reframed: Embracing the Path to Developer Productivity Engineering"
43mMeasuring Developer Productivity: The Good, the Bad and the Data
31mHow Do You Measure Devel...
34mBuilding a Culture For Developer Productivity
27mWhat Makes a Great Developer Experience?
27mDeveloper Experience: It’s Time to Start Complaining