Collaboration in Socio-Techinical Systems
summary
Argues microservice topology and organizational structure mirror each other and must be designed together: technical interactions fall into queries commands events and map to team bandwidth and collaboration modes (docs, chat, meetings, pairing). Uses DDD relationships—shared kernel partnership customer supplier published language—to show tighter coupling demands higher team coordination and looser APIs allow team distance. Demonstrates that a single heavily depended-on service creates a socio-technical bottleneck that breaks delivery and must be refactored.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 3:57Socio-technical systems explained
- 9:19Dependencies technical and organizational
- 12:10Collaboration types and classifications
- 19:12Domain-driven design and team relations
- 27:22Balancing coupling and cohesion
- 30:34Avoiding bad socio-technical architecture
related talks
01mChris Richardson at DDD Europe 2025
37mSociotechnical Architecture: What Drives Software Architecture & Teams
36mThe human factor you might be missing when designing your system
45mSystems Thinking by combining Team Topologies with Context Maps
40mSociotechnical Architecture: Aligning Teams and Software for Continuous Delivery
49mDomain-Driven Design & Team Topologies For Product-led Organizations
01h 00mThe fundamental misunderstanding in Team Topologies
45mAdaptive Socio-Technical Systems