Scaling Teams with Ownership
summary
Company moves from 3→12 teams and ends up owning 40+ services, which explodes complexity and slows delivery. Workshops reveal feature teams touched many bounded contexts with no long‑term owner, so teams are reorganised into domain/stream‑aligned teams with strong ownership per bounded context, more autonomy, and product/business roles embedded to improve flow. An initial artificial ownership map, earlier team involvement, and new guardrail/self‑correcting initiatives are implemented; some domains remain too large and challenges around balance and handoffs persist.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 2:20Domain driven design limitations
- 5:34Feature teams gone too far
- 8:06Workshops to fix ownership
- 10:31Strong ownership approach
- 13:21Balancing ownership and autonomy
- 14:25Closing remarks and call to action
related talks
21mTeam Ownership - Who Owns Production
29mWho Owns What: Ownership Culture while Bitzscaling
31mScaling
43mScaling Yourself for Managing Distributed Teams...
31mScaling Tech Organizations
44mInsights on How Team Topologies Drive Organizational Success
26mThe Rise and Fall of Feature Teams
46mLeading Distributed Teams