Theory to action: Architecting and implementing your team operating system
summary
Claims a workable method to document and iterate a team operating system by naming four concrete components — people, structure, setting, norms — and gives a reusable template, a calendar-to-sprint mapping, and a communication weather vane to map information flow. Recommends quick wins, root-cause debugging, and experiments like adding a rotating update segment What's Cooking? Uses common tools (Slack Jira Zoom whiteboarding) and reports that targeted, data‑informed changes reduce cognitive load and increase cross‑team visibility.
AI-written summary · about
chapters (13)
- 0:00Team visibility challenges
- 2:50Team operating system
- 7:09Team's people component
- 7:31Time structure and rhythms
- 11:23Communication flow patterns
- 13:06Setting and environment impact
- 15:36Team norms
- 18:30Quick wins for OS
- 19:12Debugging OS issues
- 20:57OS insights for visibility
- 23:09Sharing OS with team
- 24:54Culture via OS
- 25:15Summary and next steps
related talks
32mBuild Teams as an Engineer
29mTeam first
11mLeading without committing: Managing teams outside your tech stack
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
40mPractices from trenches for embracing evolutionary architecture in wild
27mHow to Iterate Together
46mAdaptive Socio-Technical Systems with Architecture for Flow
30mTurning stories into software