Scaling Happy Engineering Teams
summary
Concrete team rules and outcomes: start small with feedback loops, prioritize trust first and empower people to decide while holding them accountable, and avoid vetoes that freeze teams. Code practices include PRs under three days, two-reviewer, 24-hour review goal, extensive CI, per-PR review apps, feature flags and multiple daily deploys. Processes favor lightweight weekly cadences (goals, scoping, retros), async daily check-ins, and observability of organizational problems. Product is a Ruby on Rails monolith using Rails and Stimulus at Wrapbook.
AI-written summary · about
chapters (15)
- 0:00Happy engineering teams intro
- 2:48Remote work and trust
- 4:15Org change principles
- 5:40Decisions without paralysis
- 8:53Learning from mistakes
- 10:50Redesigning orgs as products
- 13:56Making org problems visible
- 15:41Choosing agile process
- 17:51Process design parameters
- 20:18Strong accountable teams
- 22:49Breaking teams without silos
- 25:14Team lifecycle and conflict
- 26:59Hiring and career growth
- 28:43Actionable steps
- 29:46About Dropbook
related talks
28mFrom Startup to Scale Up: How to Scale Engineering teams
59mTech leadership, one year after
29mBoot the backlog: Optimizing your workflow for dev happiness
46mLeading with Radical Transparency: Empowering Product Teams
09mBuilding High-Trust Teams to Supercharge Product Development
45mFast Track to World-Class Service
52mSecrets of a Strong Engineering Culture
22mOptimizing Product Development: Balancing Speed, Quality, and Process