Product Teams Need A Family Too
summary
Claim: moving to business-aligned product teams requires a family of team types to preserve flow and reduce handovers. The proposal defines four concrete topologies — stream-aligned, platform, enabling, complicated subsystem — and prescribes behaviors: platforms must provide a small, high-reliability, optional-but-compelling set of services (monitoring, provisioning, CI/CD); enabling teams coach and transfer skills; complicated subsystems host hard algorithms as products. Case examples include BMW, Adidas, Twilio, Farfetch; the measurable outcome is faster, higher-quality delivery by reducing cross-team wait times.
AI-written summary · about
chapters (8)
- 0:00The shift to product teams
- 2:15Overcoming silo challenges
- 4:15Identifying flow obstacles
- 6:01Reducing handover delays
- 9:15Equipping teams for success
- 12:49Four fundamental topologies
- 19:51Evolving team interactions
- 24:20Q&A and practical insights
related talks
37mPlatform as a Product for modern IT needs
30mTeam Topologies Applied to Platform Engineering
58mTeam Topologies Panel
07mProduct Org Design: Flow Follows Form
30mThe Art of Team Design
45mLessons learned from introducing Team Topologies
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
44mProduct Mode for Digital Platform Teams