Looking for Flow in All the Wrong Places
summary
Defines flow as both an individual state and an organizational ability to deliver value faster, argues most teams misplace focus on visible metrics and feature churn, and gives concrete numbers and fixes: 90% of software costs are maintenance, 70% of coding effort is understanding code, and companies must sometimes pause feature work for 6–36 months to reverse a debt spiral that killed firms like Nokia. Recommends measure value, sequence work for fastest value first, signal and remove unplanned work, and track dependencies to protect seams.
AI-written summary · about
chapters (12)
- 0:00Introduction to Flow
- 0:29Defining Flow
- 2:21The Importance of Flow
- 4:46Historical Perspectives on Flow
- 7:40Modern Challenges in Achieving Flow
- 10:42Common Misconceptions About Flow
- 13:50Strategies for Improving Flow
- 14:52The Debt Spiral and Feature Work
- 17:25The Role of Productivity and Agency
- 19:49The Importance of Collaboration
- 25:36Practical Tips for Enhancing Flow
- 28:02Conclusion
related talks
39mMob Programming and the Power of Flow
32mThe F word; What it takes to do great work
22mHappiness & Performance: How to Trigger Flow at Work
43mSoftware Architecture, Design Thinking & Knowledge Flow
05mThe Road to DevOps Success: It’s Human
01h 02mPeople and Patterns
51mCommon pitfalls in engineering teams and how to avoid them
01h 01mLies Developers Tell Themselves