Improving Your Team(work)
summary
Practical, example-rich guidance on how individual contributors change team dynamics: concrete tactics for proposing technical change (talk to build/test owners, show costs/benefits, offer a bite-sized trial), handling urgent solo fixes while keeping the team informed, and practical fixes for poor communication (retros, standups, Git cheat sheets, rethink Google Test or C++20 upgrades). Emphasis on measurable outcomes — fewer handoffs, fewer missed integrations — with behavioral moves like lead by example and praise publicly but low-key to nudge culture.
AI-written summary · about
chapters (7)
- 0:00Introduction to teamwork
- 5:55Negative behaviors in teams
- 16:16Positive team dynamics
- 27:17Communicating effectively
- 39:58Taking initiative
- 49:15Healthy team discussions
- 55:44Q&A session
related talks
51mEffecting Change—The Art of Leading Teams
41mWant to make a change? Stop talking and start listening
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
46mEssentials for Building and Leading Highly Effective Development Teams
17mSo You Think You Can Lead a Software Team?
34mCongressive Management Techniques: Gardening Your Team
39mUsing Agile Techniques to Build a More Inclusive Team
51mCommon pitfalls in technical teams and how to avoid them