How do Conway’s law work?

Conway’s Law is a concept in software engineering that states that the design of a system (e.g., a software system) is strongly influenced by the social and communication structures within the organization that produced it. Essentially, the law asserts that the structure and behavior of a system will reflect the structure and communication patterns of the organization that created it.

One example of Conway’s Law in action is the well-known case of IBM’s System/360 mainframe computer in the 1960s. The System/360 was a large and complex project involving many different teams and departments within IBM. The structure of the teams and their communication patterns had a significant impact on the design of the System/360, and the end result was a system that was highly modular and easy to modify, reflecting the hierarchical and centralized structure of IBM’s organization.

Another example can be seen in the design of many large software systems, where the design of the system often reflects the communication and collaboration patterns of the development team. For instance, if a development team is organized into smaller, self-contained units, the design of the software may also be organized into modular components that can be developed and tested independently. On the other hand, if the team is more centralized and focused on shared goals, the design of the software may be more tightly integrated, reflecting the more cooperative structure of the team.

Google has a decentralized and flat organizational structure, with a focus on innovation and experimentation. This is reflected in its development process, which emphasizes small, autonomous teams that are able to quickly prototype and iterate on new ideas. Google’s products, such as search and Gmail, are known for their simplicity and ease of use, reflecting the company’s focus on user experience and accessibility.

Microsoft, on the other hand, has a more hierarchical and centralized structure, with a focus on delivering enterprise-level products and services. This is reflected in the design of its software, which is often complex and feature-rich, designed to meet the needs of large businesses and organizations. Microsoft’s development process is also more structured, with a greater emphasis on process and planning.

Apple is well-known for its design-focused culture and its tightly integrated product line. Apple’s products, such as the iPhone and Mac, are known for their sleek design and seamless user experience. This reflects the company’s focus on design and user experience, and its organizational structure, which is centralized and focused on delivering high-quality, integrated products.

Oracle, as a provider of enterprise software and database solutions, has a highly centralized and structured organizational structure, with a focus on delivering robust and scalable products. This is reflected in the design of its software, which is often complex and feature-rich, designed to meet the needs of large businesses and organizations. Oracle’s development process is also highly structured, with a focus on delivering products that are reliable, secure, and scalable.

In short, Conway’s Law highlights the importance of considering the organizational structure and communication patterns within an organization when designing a system, as these factors can have a significant impact on the design and success of the final product.