4 bad ideas about productivity... & what Agilists should do instead
summary
High interest rates drive fresh demands for productivity and the talk debunks four trendy but harmful claims and gives concrete alternatives: measure impact not output — connect effort to customer outcomes and financial value; treat developer experience ≠ productivity — track both separately and use DX as a leading indicator; make platform as product choices so teams would willingly adopt shared services; and treat AI as a tool, not magic, validating its work and guarding long term learning and release discipline.
AI-written summary · about
chapters (13)
- 0:00Productivity questions rising
- 3:20Four bad productivity ideas
- 10:21Can’t measure productivity
- 11:04Dev experience ≠ productivity
- 16:23Platforms ≠ productivity
- 21:35AI ≠ productivity
- 27:39Frame productivity correctly
- 30:28Q&A: Platforms & dev experience
- 34:21Q&A: Outcome-based models
- 37:16Q&A: Dev experience & motivation
- 41:56Q&A: Tech choices & volatility
- 44:20Q&A: AI reliance & skills
- 47:13Closing remarks
related talks
33mMeasuring Developer Productivity: the good, the bad and the data
51mDeveloper productivity is waste
43mMeasuring Developer Productivity: The Good, the Bad and the Data
34mBuilding a Culture For Developer Productivity
43mThe Past, Present and Future of Developer Productivity Theories and Metrics
47mCan We Measure Developer Productivity?
18mFrom developer productivity to engineering impact
34mFor effectiveness, Agile was never the answer