Modern Organizational Architecture, Are Microservices a Model for Diversity?
summary
Idea: treat organizational units like microservices, creating micro-cultures — small cross-domain teams with clear APIs for communication and autonomy over their codepaths — so culture becomes modular, fault-isolated and replaceable rather than a single top-down monoculture. Claims include faster time-to-market, improved user representation, and resilient delivery; cites Gartner research that inclusive teams perform 30% better. The Ortelius connection motivates mapping service properties (isolation, autonomy, ownership, two-pizza teams) to measurable diversity and delivery outcomes.
AI-written summary · about
chapters (12)
- 0:00Introduction and thesis
- 1:44DevOps and diversity gap
- 5:46Defining diversity in teams
- 7:10Why diversity matters
- 9:41The problem with current orgs
- 10:25Microservices explained
- 12:28Monolith vs microservices
- 13:33Traditional org structures
- 14:16Modern node-graph orgs
- 14:57Mapping microservices to orgs
- 17:26Microcultures vs monolithic culture
- 18:51Benefits of diverse microcultures
related talks
52mWhat Does a Good Microservice Architecture Look Like?
48mMeta Modern Software Architecture
52mMeta modern Software Architecture
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
36mIt's Simple...
42mMicroservices and Modularity or the difference between treatment and cure!
48mIT Architecture : All your micro-services are wrong PERIOD!
01h 01mArchitectural Principles and Practices to Build MicroServices