Datasite's product-org redesign paired two changes deliberately: the org adopted Spotify's squad model for how people were grouped, and the platform was rebuilt as a modular microservices architecture. Team boundaries and service boundaries were made to reflect the same decomposition of the problem, so a squad could own a service (or small cluster of services) end to end rather than needing to coordinate across a monolith.
This is a deliberate application of what's elsewhere called the Inverse Conway Maneuver: instead of letting the org chart passively produce whatever architecture falls out of existing communication patterns (Conway's Law), Datasite designed org structure and technical architecture together, as one decision. It only became possible after Wholesale Leadership Replacement (Replace vs. Coach-Up) cleared out a management layer with no stake in the old, siloed structure, and it fed directly into the migration off the Oracle monolith.
Related: Product Model (vs. Roadmap Model), Monolith-to-Microservices Migration Playbook.
Thomas (CTO/CPO) frames the org↔architecture mirroring explicitly as a scaling mechanism: squads and microservices need to mirror each other's modularity so that both the org and the platform can scale in parallel — neither structure should have to wait on the other to catch up. This is presented as a deliberate design principle during the Datasite product-org rebuild (see Spotify Squad Model, Monolith-to-Microservices Migration Playbook), not an incidental resemblance.
Из тем: Transformation in Practice