Good article, Angel (despite the clickbait title). As a developer and development manager for 50 years there are some insights that I think are worth sharing.

1: We do not need a monolith to share among development teams. We need to value communicating and we need leadership that understands that we're much more likely to succeed working together than working separately.

2: Conway's Law is not a cure for the problem, it's an explanation of why there is a problem. The intra-corporate tribalism described by Conway's Law is a barrier to positive communication and effective architecture and design.

3: More effective component and communications models can make it easier for teams to work together by: a) using domain-bounded contexts to define the scope of component services, b) taking advantage of loosely-coupled component models, and c) requiring the owners of data and services to expose access to them through documented and published service APIs.

Properly designed and implemented microservices are one of the ways to accomplish this, but they are certainly not the only way. You might find this link worth following:

https://medium.com/the-techlife/building-software-systems-2ff5bed06277

At Amazon, Jeff Bezos overcame Conway's Law with his famous memo. He was successful!

https://medium.com/nerd-for-tech/the-memo-amazons-secret-sauce-e99bdc37c65f

Keep up the good work!