The human factor you might be missing when designing your system
summary
Argues that design fails when organizational communication and team mental effort are ignored, using Socio-Technical Systems and Conway’s Law to explain why microservices often become hidden monoliths or distributed monoliths. Recommends concrete fixes: clear ownership and fracture-plane boundaries, reduce work in progress, prioritize smaller stories, automate CI/CD and empower teams so services can deploy independently. Highlights Team Cognitive Load metrics and symptoms (slow delivery, poor architecture, burnout) and cites The Unicorn Project as a practical example.
AI-written summary · about
chapters (6)
- 0:00Introduction and empathy definition
- 5:18Empathy in system design
- 13:55Align social and technical systems
- 18:11Conway's law and system design
- 28:55Reducing team cognitive load
- 33:26Key takeaways and conclusion
related talks
39mThe Human Side of Microservices
50mHow and why to design your Teams for modern Software Systems
01h 00mThe fundamental misunderstanding in Team Topologies
47mMicroservices and the Inverse Conway Manoeuvre
58mMicroservices and the Inverse Conway Manoeuvre
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
33mMonoliths vs Microservices is Missing the Point—Start with Team Cognitive Load
32mCollaboration in Socio-Techinical Systems