Leading without committing: Managing teams outside your tech stack
summary
Lays out a concrete playbook: builds a cross-platform glossary and redesigns the logged‑in homepage to stop confusing terminology, uses exploratory testing and product/browser/device data to find pain, shadows on‑call and deployment to learn developer experience, pushes documentation and monitoring improvements, and runs a bi-weekly book club plus shared one-on-one notes to map career paths and collect feedback — practical steps that reduce confusion and raise engineering trust.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:55Unprepared for leadership
- 2:59Knowledge gaps
- 4:43Building trust
- 6:35Breaking habits
- 8:00Engineering fundamentals
- 9:02Coaching engineers
- 10:05Key takeaways
related talks
30mEquipping your team to support junior developers
32mBuild Teams as an Engineer
28mTechnical leadership and glue work
28mDesigning for Success: UX Principles for Internal Developer Platforms
32mLessons Learned from 7 Years of Running Developer Platforms
43mScalable Best Practices for Your Development Team
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
33mPaving the Road to Effective Software Development