Congrats! You're the tech lead - now what?
summary
Defines the tech lead as owner of the technological vision and gives tactical practices: use burndowns and hours and tickets to make scope arguments, write meeting recaps and requirements to stop Groundhog Day, teach team members instead of doing everything, force demos and whiteboard walkthroughs to catch the last 10% risk, and relentlessly investigate the black‑box integrations that scare you. Accept the shift to an interruptible, manager’s schedule and use advocacy, facilitation and motivation to keep the project on track.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:13I'm a PHP developer.
- 2:13have recently become a tech lead.
- 2:55A TECH LEAD IS...
- 4:28Tech leading looks a little different everywhere you go.
- 6:51Achieve tech lead mastery in three easy steps
- 7:54Always be asking yourself
- 9:59TACTIC #1
- 17:04TACTIC #2
- 18:29How to advocate when talking to...
- 22:38I don't want to scare you, but...
- 23:03First key to motivation
- 24:30TACTIC #3
- 26:51The Tech Lead Paradox
- 28:50Minimize Risk.
- 30:21It can be hard to code when you're a tech lead.
related talks
51mSo You’ve Just Become a Tech Lead - Great! Now What?
50mMaking the Leap to Tech Lead
47m"Talking with Tech Leads"
35mTalking With Tech Leads
36mBecoming a tech lead - Lessons learned
13mSo you want to be a Tech Lead?
42mThe Quantum Tech Lead: Hands-On and Abstract at the Same Time
23mTech leadership for everyone