Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.Melvin Conway
Conway’s law was not intended as a joke or a Zen koan, but as a valid sociological observation. It is a consequence of the fact that two software modules A and B cannot interface correctly with each other unless the designer and implementer of A communicates with the designer and implementer of B. Thus the interface structure of a software system necessarily will show a congruence with the social structure of the organization that produced it.
Easily observed in organisations today Conway’s law still has merit and should be considered when designing software or reviewing organisational design.
Also, from https://www.linkedin.com/posts/jonny-williams-83433836_do-you-care-about-conways-law-if-youre-activity-7009445165320790016-ZYTW/
So what might caring about Conway’s Law help you to do as a team enabler?
👉 Understand misalignment between the organisation’s communication structure and the systems and products they are creating.
👉 Recognise potential organisational impediments that might limit effective collaboration and communication.
👉 Offer practices, tools, and techniques that can help teams to navigate the limitations of the structure around them.
👉 Avoid common pitfalls and challenges that arise when working on complex systems.
👉 Help senior colleagues to understand that they play a role in shaping systems and products through their influence over communication structures.