Who Owns What: Ownership Culture while Bitzscaling
summary
Company grows from ~40 to 250+ engineers and the team builds a text-backed ownership source: per-team YAML checked by a GitHub Action, an inverted index exposed as callable code owners and an owner tag baked into core libs so alerts auto-route by file. Result: migration becomes trivial, manual instrumentation drops, MTTD shows a double-digit % improvement in mean time to detect, and automatic detection more than 100% increase in automatic detection, catching multiple prod-threatening bugs in staging.
AI-written summary · about
chapters (11)
- 0:00Ownership culture intro
- 3:45Monolith ownership problems
- 8:00Accountability vs ownership culture
- 10:26Monolith observability problem
- 13:39Code ownership as truth
- 17:33Callable code owners for alerts
- 21:43Instrumentation and migration
- 23:29Ownership-driven observability cycle
- 25:57Impact on teams
- 27:43Ownership Ops and architecture
- 28:26Closing remarks
related talks
21mTeam Ownership - Who Owns Production
15mBuilding Actionable Code Ownership
16mScaling Teams with Ownership
24mGrowing Pains: Taming the Post-Startup Stage With Backstage
58mKeynote: Seven Habits of a (Mostly) Successful Team
23mExtreme Ownership for Global Teams
51mScaling Sustainable Innovation through Team Autonomy
32mCode First, Ask Questions Later