Engineering Effectiveness: Achieving your goals with less
summary
Claims that only 30–40% value‑add of development time is real and Stripe’s cited ~$300B GDP loss grab attention; evidence centers on measuring and eliminating waste (not individual productivity) using value‑stream mapping, tracking late‑stage defect rates and strategic‑aligned capacity, and surveying engineers. Finding information consumes 30% of a week for many teams, platform engineering and operating‑model fixes show biggest leverage, DORA is useful but lagging, and generative AI helps findability and spec prep more than end‑to‑end throughput today.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:35Global Economic Crisis
- 1:30Engineering Effectiveness
- 3:14Measuring and eliminating waste
- 4:43The talent question
- 5:28Developer experience friction
- 7:47Dora metrics
- 8:26Culture
- 12:50Engineering Effectiveness Framework
- 17:05Metrics
- 20:20Strategic Intent
- 21:35How much does coding really matter
- 23:30Summary
related talks
31mImproving engineering effectiveness: A journey for the entire organization
46mThe journey to building effective engineering teams
27mOptimizing the engineering value stream
10mAchieving engineering velocity by optimising developer experience
13mDeveloper Satisfaction = Better Code | Here's Why
55mAgile Engineering
06mWin with AI through Engineering Effectiveness: Insights from...
44m.tune - Eliminate Waste in SW Development