Learn a new word: Conway's Law

Have you ever noticed the tendency for large, complex, and difficult to navigate organizations to create to create large, complex, and difficult to navigate products, services, and policies?

Alternatively, have you noticed, (I am sure you have), how many startup companies (especially tech companies), who lack size, complexity and bureaucracy in their organizations tend to create much simpler, easy to use and intuitive kinds of products and services? 

It kind of makes sense, even if we never really consciously thought about the connection between the organization, its size, methods of working, and structure and the outputs of that organization. But it is a phenomenon, in technology certainly, that has been observed for at least 50 years, and it has a name - Conway's Law - today's Word of the Day.

Mel Conway, a programmer, came up with concept in 1967, and by 1968 it was dubbed his 'law'. What does the law actually say? From Mr. Conway's website:

Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.

Later, the Law was expanded to encompass not just the idea that an organization's communication structure would influence (and mirror) the systems that the organization produces, but the broad 'culture' of the organization has a significant impact on its products and services.

Think of a corporate website, which often has separate sections of information that copies the internal organizational makeup, not necessarily aligned and architected with how site visitors want to consume information. Or an enterprise technology product that offers complex and lengthy workflows for transaction entry, routing, and approval that tends to reflect the creating organization's own internal processes and hierarchies that do not always reflect what their customers want.

These kinds of examples show Conway's Law in effect - the way the fundamental elements of how an organization operates internally show up in the products they build, the services they offer, and more broadly, how they 'see' the relationship between themselves and their customers, shareholders, and community.

I have written in a few places that when making decisions around HR and other enterprise technologies that HR and business leaders should evaluate the culture and vision of any potential technology provider just as closely, (if not more closely), than they evaluate the capability and functionality of a particular piece of software.

Capability and functionality can change over time, and in mature markets tends to run together amongst established providers. But organization culture changes much more slowly, if ever, and no matter what new elements of functionality are introduced to the solution, the essential nature of the provider (and the priduct too), is likely to be pretty well entrenched.

Have a great day!