A common response I get when discussing Conway's Law is "don't ship the org chart" and that tells me that a lot of people know what Conway's Law is without understanding what it means.
Shipping the org chart is inevitable past a certain scale of system complexity. Despite our best efforts, teams will silo into the projects (apps, libraries, services, modules, whatever) that they are responsible for maintaining and consolidate the code that makes sense to them into the places where they do the most work. It takes an incredible amount of discipline for a team to keep their own work tidy and organized, let alone to organize the rats nest of dependencies between the teams themselves.
You can fight the tide and try to maintain a system architecture plan that does not resemble your team structure, and if you're successful then in the process you'll likely have created a shadow org of people who communicate and work together as if they are on the same team even though the org chart says that they are not. Alternatively you can just accept that people building a project together are going to need to collaborate closely and facilitate that by forming a team.
So when somebody says "don't ship the org chart" it's kind of like when somebody tells a smoker "you're massively increasing your risk of cancer" and they fire back "I'll be careful." The negative consequences for failing to heed Conway's Law cannot be avoided simply by claiming to understand the risks.
