SAG Expert Interview #01: Designing Knowledge Flow & Inclusive Architecture
summary
Claims that organizational structure shapes software via Conway's Law and that events as the beating heart of a system improve cohesion and boundaries, with concrete techniques: listen for pain, find a leverage point, model events and data, then apply data modeling, APIs or event streams (Kafka mentioned) as appropriate. Presents numbers to provoke change like 91.8% male engineers and 95% of enterprise women leaving over 20 years. Emphasizes trust built by due diligence, workshops using the iceberg model, and that solutions always depend on context.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:34Listening for pain and leverage points
- 6:44Building trust in architecture
- 9:13Aligning with business goals
- 11:24Inclusive systems design workshop
- 14:10Diversity and retention in tech
- 15:57Driving cultural change together
related talks
49mArchitecture is Designing Knowledge Flow
53mSoftware Design: Beyond Boxes & Lines
35mOrganization: A Tool for Software Architects
45mTeam and Software: Making an Impact as an Architect
45mConway's Law: when best practices aren't enough
31mHow and Why to Design Your Teams for Modern Software Systems
24mThe (too) Many Faces of Architecture
25mThe (too) Many Faces of Architecture