High-performance teams
summary
Argues architects need as much soft skill work as technical decisions and that the highest-leverage change is shaping how teams work rather than choosing frameworks. Recommends building team knowledge through mentoring, pair programming, shared ownership and regular retros; track outcomes with deployment frequency and failure rate so architecting choices map to customer-facing reliability. Shows concrete interventions—coaching, coding standards, team rituals—and claims these shift quality more than switching libraries or architectures.
AI-written summary · about
related talks
45mTeam and Software: Making an Impact as an Architect
46mTHE too MANY FACES OF ARCHITECTURE
41mSoftware architecture as a contributor to high performing teams
46mTechnical Leadership and Empowered Teams
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
49mCultivating Architecture
01h 02mThinking Like an Architect
45mArchitecture: The Stuff That's Hard to Change