Tech leadership for everyone
summary
A senior developer steps into an unofficial tech lead role by running two weeks of pairing with everyone, mapping personalities, running a retrospective canvas workshop, and co-running an estimation workshop that produces a confluence estimation guide with examples for 1–8 story points. The team enforces TDD, refactors the front-end repo, reduces merge conflicts, gains visibility into bug fixes, wins autonomy over the backlog and becomes the first product team in the company — concrete practices that measurably improve estimates and delivery.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:10Leadership
- 3:02Authentic leadership
- 4:28Team culture
- 6:20Pairing
- 10:55Changing mindsets
- 12:38Intrinsic personality
- 14:21Review
- 17:41Tech parties
- 21:22Conclusion
related talks
50mMaking the Leap to Tech Lead
36mBecoming a tech lead - Lessons learned
47m"Talking with Tech Leads"
18mAgile leadership and technical mastery, a harmonious alliance
32mCongrats! You're the tech lead - now what?
30mWhat I wish I knew as a first time Tech Lead
17mSo You Think You Can Lead a Software Team?
51mSo You’ve Just Become a Tech Lead - Great! Now What?