Becoming a tech lead - Lessons learned
summary
Describes moving from individual contributor to tech lead by building onboarding and mentorship programs, instituting frequent code reviews, ticket templates and sprint review meetings, and measuring sprint metrics to find blockers. Implements feature toggles for risky launches and pushes back on product tradeoffs to reserve refactor time. Metrics show surprising swings — sprint accuracy rising to 150% while consistency remains below 50% — prompting root-cause fixes (auth bugs, missing specs) that reduce QA/code-review bottlenecks.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:59Individual Contributor
- 3:45Learning From Tech Leads
- 5:34Goals
- 7:52Communication Bridge
- 10:40Working Together to Improve the Productivity
- 12:57Sprint Planning
- 18:25Code Reviews
- 20:17Retro Sessions
- 27:18estimating?
- 30:44Sprint Metrics
- 32:32Summary
related talks
50mMaking the Leap to Tech Lead
30mWhat I wish I knew as a first time Tech Lead
23mTech leadership for everyone
47m"Talking with Tech Leads"
51mSo You’ve Just Become a Tech Lead - Great! Now What?
32mCongrats! You're the tech lead - now what?
43mHow to Lead? Testimonial of a Lead Android Engineer
50mSupporting your peers' growth as a tech lead