Building a High-Performance Team is Everyone's Job
summary
Rewrites move a Drupal/PHP storefront into Java microservices, replace git submodules with automation and feature flags, and reduce deploys from 4+ hours to daily, which immediately raises morale and autonomy. A detailed, public career ladder resolves opaque promotions and pay; published engineering ladder and regular blameless postmortems institutionalize learning from failures. Over three years the output shifts from fear-driven to trust-based: faster shipping, clearer decision processes, and more candid, curiosity-driven technical conflict.
AI-written summary · about
chapters (15)
- 0:00Introduction and journey
- 1:08My time as a developer
- 2:18Joining a startup
- 5:07Cultural crisis
- 8:56Rebooting the culture
- 10:33Building speed and autonomy
- 15:57Structure and scaling
- 19:12Engineering career ladder
- 22:56Learning from failures
- 25:55Building trust and empathy
- 30:27Interviewing for culture
- 34:43Managing conflict
- 37:24The importance of apology
- 39:43Conclusion
- 41:28Q&A session
related talks
49mBuilding a High-Performance Team is Everyone's Job
30mThe Elements of Scaling
15mBuilding high performing teams
59mTech leadership, one year after
28mBuilding happier engineering teams
32mCode First, Ask Questions Later
18mAgile leadership and technical mastery, a harmonious alliance
34mAn Engineering Team Where Everyone is a Leader