Scaling Impact: Building High-Performing Product Teams Across Borders
summary
Three-site org splits identity work: Amsterdam owns data collection and storage, Bangalore owns end-to-end verifications and vendor integrations, with London adjacent; teams get weekly one-to-ones, carve European mornings free for Bangalore calls, and run two in-person meetups a year plus quarterly London visits. Progress uses yearly objectives with monthly KRs, a monthly offline MBR (automated dashboard) pulling roadmap and OKR updates, two user researchers supporting seven teams while PMs run light studies, and culture driven by ownership, bias to action, learner metrics: people surveys, strategy progress, and engineering velocity.
AI-written summary · about
chapters (13)
- 0:00Introduction and team setup
- 1:16Organizational design for speed
- 3:22Building team culture across time zones
- 4:47Weekly collaboration setup
- 7:18Toolkit and AI integration
- 8:44Strategy and OKRs alignment
- 9:24Quality control and processes
- 13:56Booking.com culture and values
- 16:26Daily reinforcement of values
- 19:15Measuring high performance
- 21:28Building trust remotely
- 24:43Leadership style evolution
- 27:11Q&A session
related talks
51mTales of a German Building Diverse Teams Across All Time Zones
23mAish Dahal at StaffPlus London 2023
37mBuilding & Scaling Distributed Teams
10mManaging across timezones; A retrospective
46mOptimizing for Speed
43mScaling Yourself for Managing Distributed Teams...
32mTales of a German Building Diverse Teams Across All Time Zones
52mToo many cooks! Supporting augmented teams without getting salty