14 Identifying And Removing Impediments
summary
Shows concrete fixes and measured practices: a $3 tether solved a recurring projector-remote problem; use ask why five times to reach root causes; prefer alignment over agreement so teams commit to a direction; add fitness functions/checklists and dashboards showing bug counts and code coverage as information radiators. Hire a coach and appoint a sponsor per initiative. Example: pairing with leadership and coaching leads to a full automated-test release in six months.
AI-written summary · about
chapters (12)
- 0:00Introduction to impediments
- 2:31Types of impediments
- 5:41Comfort zone as an impediment
- 11:15Course correction in progress
- 19:52Root cause analysis with why
- 24:13Realistic goals and team capabilities
- 30:13Checking team vitals continuously
- 36:18Data-driven decision making
- 43:07Information radiators for transparency
- 47:21Focus on outcome over blame
- 51:39Bringing help and coaches
- 54:30Sponsors and champions for change
related talks
51mEffecting Change—The Art of Leading Teams
44mEnhancing the Performance of Engineering Teams
55mReignite your desire to improve
51mCommon pitfalls in engineering teams and how to avoid them
26mTake a step back
51mHacking Your Processes
48mThe 10 vicious circles at work: detecting and breaking them up
01h 01mHabits of a Highly Effective Technical Manager