Team Motivation - CDK Local
summary
Claims that teams need autonomy, mastery and purpose and then gives concrete practices: run short feedback loops (daily joins, unit tests) to be "wrong fast", apply marginal gains via continuous refactoring and small cleanups, and probe missing data (candle problem and WWII bomber example) instead of trusting visible damage. Cites a 2005 MIT Lego study showing groups who kept visible work persist 40% longer, and describes CDK’s focus on unit tests, incremental refactor, customer feedback and aligning stories to product purpose.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:50Autonomy in motivation
- 3:37Intrinsic vs extrinsic motivation
- 6:11Barriers to autonomous teams
- 10:22Building team trust
- 13:16Shortening feedback loops
- 16:05Marginal gains in code
- 18:32Beyond visible data
- 20:18Purpose drives teams
- 21:44Organizational purpose
- 23:27Task-based purpose
- 25:53Personal purpose alignment
- 26:34Balancing autonomy mastery purpose
- 27:39Q&A
related talks
26mUpdate your team to be more extreme
54mMob Mentality Collaborative Coding and Problem Solving
52mEmpowerment in the Software Delivery Lifecycle
34mBuilding a Culture For Developer Productivity
33mFinding Motivation in Maintenance
46mTowards Joyful Development
45mDeveloper Joy – How great teams get s%*t done
41mTurn Up the Good