Improving engineering effectiveness: A journey for the entire organization
summary
Argues that improving engineering effectiveness requires systems thinking across the whole value stream, not just more engineers or tools, citing the Accelerate 2018 finding that low performers spend up to 70% waste. Recommends concrete practices: value stream mapping, team reshaping into autonomous product teams (staggered rollout to reduce change fatigue), dedicating ~20% time to tech debt, using GitHub Copilot / AWS CodeWhisperer / ChatGPT to speed scripting, and measuring delivery + user outcomes to prioritize fixes.
AI-written summary · about
chapters (12)
- 0:00Engineering effectiveness matters
- 4:24Effectiveness beyond engineering
- 7:41Systems thinking for improvement
- 15:01Identifying improvement opportunities
- 17:29Roles driving change
- 22:31Engineers reducing manual work
- 24:41Product owners: features vs quality
- 25:47Tech leads: continuous improvement
- 27:14Management’s role in culture
- 28:16Non-engineering teams contribute
- 29:02Executives driving change
- 30:50Continuous journey in effectiveness
related talks
46mThe journey to building effective engineering teams
31mEngineering Effectiveness: Achieving your goals with less
38mEngineering Engineering: More than the sum of our parts
32mPanel discussion: The journey to building effective engineering teams
44mEnhancing the Performance of Engineering Teams
06mWin with AI through Engineering Effectiveness: Insights from...
10mAchieving engineering velocity by optimising developer experience
15mOptimizing the engineering value stream