The Architecture of Power: Leadership, Systems, and Software Architecture
summary
Friday’s release sits blocked until the absent lead architect returns, decides in ten minutes, and the team learns that the architect is indispensable — a dependency the incident amplifies. The talk maps power as a power loop of six domains — events, narratives, beliefs, institutions, agendas, decisions — and shows tactics: register events and surface repeated blockers, weave them into a narrative, take the issue to a retrospective, introduce lightweight ADRs and formalize rituals so the arrangement changes and Fridays stop needing one person.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:26Blocked release dependency
- 7:28Power loop model
- 14:16Changing arrangements
- 20:34Power tactics
- 23:27Q&A
- 25:12Live AI demo
- 51:55AI deployment lessons
- 1:00:18Business-driven .NET microservices
- 1:20:34Scaling to 10M users
- 1:34:31Q&A and closing
related talks
45mTeam and Software: Making an Impact as an Architect
35mOrganization: A Tool for Software Architects
46mTHE too MANY FACES OF ARCHITECTURE
37mSoftware Architecture for Humans!
45mArchitecture: The Stuff That's Hard to Change
24mThe (too) Many Faces of Architecture
51mSoftware Architecture for Humans!
41mSoftware architecture as a contributor to high performing teams