The SaaS Industrial Complex: When Their Mirror Becomes Your Mold

From Eisenhower to Conway’s Law

In his farewell address on January 17, 1961, President Dwight D. Eisenhower introduced the term "military-industrial complex" to caution against the growing influence of a powerful alliance between the U.S. military and defense contractors. He warned that this partnership, while it would contribute to national defense, posed a potential threat to democratic governance if left unchecked. Eisenhower emphasized the need for an "alert and knowledgeable citizenry" to ensure that this complex did not acquire unwarranted influence over American policy and society. 

Just six years later, the programmer Melvin E. Conway observed in 1967 that “any organization that designs a system … will produce a design whose structure is a copy of the organization’s communication structure.” In plainer words: the way people and teams talk to one another inevitably shapes the architecture of the software, product, or process they build. 

Conway introduced the idea in his Datamation article “How Do Committees Invent?” (1968). He noticed that when a compiler was written by one small group, it was a simple one-pass design, but when responsibility was split between two groups, the compiler became two-pass, mirroring the organizational split. Fred Brooks later popularized the adage as “Conway’s Law” in The Mythical Man-Month and has since been validated repeatedly in software projects and beyond. 

Why Conway’s Law Happens

1. Communication boundaries create technical boundaries. People coordinate most closely with the colleagues they meet or message regularly. Interfaces between teams become interfaces between code modules or subsystems.