An Engineering Team Where Everyone is a Leader
summary
A team that spends months without a manager and still ships a major elastic login cluster upgrade claims leadership comes from everyone and gives seven concrete practices: documented onboarding and step‑by‑step production releases, a peer buddy and technical mentor pairing, automated CI/CD pipelines and GitHub hooks, and metrics like lead time and cycle time, velocity and MTBF measured regularly. Monitoring uses ELK and Grafana. The result reported is fewer blockers, shared on‑call shifts, faster fixes and sustained morale.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:31an engineering team where
- 2:12what made this team's culture so special?
- 3:08you don't need to be a manager to be a leader
- 3:23leadership should come from everywhere
- 3:45identify and remove blockers that prevent the team from being productive
- 4:16onboarding tips
- 7:05comprehensive dev onboarding is a MUST
- 8:40what does the day in the life of a productive Engineering team look like?
- 12:19what is harder than it should be?
- 13:53ask questions that enable people to reach a new perspective on the problem and reach a solution on their own
- 14:23empower others.
- 14:41good leaders EXPLAIN WHY THEY NEED TO DO IT
- 15:13ensure that decisions are made at the level where the best information is available
- 15:57paired programming on complex features collaborative code reviews seek to understand and expose costly pain points · amplify your team's voice to influence organizational changes · advocate for anonymous pulse surveys · do stay interviews
- 19:25share credit, take blame.
- 20:04The best measure of a leader is how much responsibility they take for their team's failures.
- 20:42never devalue people in the process of delivering a solution.
- 22:48do not focus on tracking individual metrics - it should be about the team
- 25:58how are team members mentoring one another? · how effective are we at translating business needs into working software? · how aligned are we to our product's vision? · how strong are our relationships with other development teams and business partners? · does everyone on the team have an equal Voice?
- 26:30resist the urge to set arbitrary metrics goals
- 28:47building products to solve a new problem is all about creativity
- 29:09the quality of our work is affected by the degree of diversity of the team.
- 29:44vulnerability: the ability to own your mistakes and not try to cover them up
- 30:00stories of struggle
- 30:39establish trust.
related talks
33mAn Engineering Team Where Everyone is a Leader
44mEnhancing the Performance of Engineering Teams
28mBuilding High Performance Engineering Teams
43mThe Joys of Managing Engineering Teams
51mBuilding a High-Performance Team is Everyone's Job
27mLead Lead and Not Lead Follow
23mManaging diverse engineers for high-impact deliveries
20mBuilding Distributed Systems in Distributed Teams