An Engineering Team Where Everyone is a Leader
summary
Team runs without a manager for months and successfully ships a major Elastic login upgrade while staying motivated, claiming everyone shares leadership through seven tactical practices: streamlined onboarding with peer buddy and technical mentor, step‑by‑step dev environment and release docs, GitHub hooks and CCD pipelines for lead time and cycle time, ELK/Grafana dashboards, Jira linking, rubber‑duck paired debugging and shared credit, taken blame, plus simple rituals like a Monday “photo of the week.”
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:11Remove blockers for productivity
- 14:07Empower every team member
- 19:23Share credit take blame
- 26:44Value people over process
- 29:33Be vulnerable as a leader
- 30:35Establish trust on the team
- 33:04Q&A and closing
related talks
34mAn Engineering Team Where Everyone is a Leader
43mThe Joys of Managing Engineering Teams
23mManaging diverse engineers for high-impact deliveries
51mBuilding a High-Performance Team is Everyone's Job
20mBuilding Distributed Systems in Distributed Teams
41mElastic: How a Fully Distributed Team of 250 People Works
21mScaling Distributed Teams
59mTech leadership, one year after