Effecting Change—The Art of Leading Teams
summary
Convincing others starts with rigor: verify the problem before selling a fix, generate three solutions and list tradeoffs, and test changes on a small team while diagnosing why they work. A consultant uncovers three non-testing blockers and the project finishes two weeks early; a company with 7,000 programmers and a 50-member architecture committee shifts practice after an unbiased review of options. Use targeted support like pair programming with an expert, surface progress with display metrics, and remove energy-draining busywork.
AI-written summary · about
chapters (16)
- 0:00Leading teams as programmers
- 3:34Changing minds vs writing code
- 8:10Pushing solutions vs understanding problems
- 13:53Why teams resist mandates
- 16:22Paradox of choice in decisions
- 20:40Guide change without dictating
- 24:56Testing ideas and success
- 28:52Fighting corporate politics
- 31:22Innovative approaches to problems
- 34:54Mental fatigue and productivity
- 38:08Boring tasks kill decisions
- 41:19Environments for focus and creativity
- 42:43Timing and breaks impact decisions
- 44:57Overcoming confirmation bias
- 45:37Support for successful change
- 48:06Key takeaways
related talks
54mEffecting Change—The Art Of Leading Teams
01h 00mImproving Your Team(work)
55m14 Identifying And Removing Impediments
25mHow to Drive Cross Team Techincal Changes
46mEssentials for Building and Leading Highly Effective Development Teams
49mAll Aboard: Tools and Tactics for Building Team Consensus.
41mWant to make a change? Stop talking and start listening
47mHow to Lead Change as the Newbie