Saved by Hagen Peters and
bliki: Conway's Law
Conway’s Law is a celebrated truism in software development: technical systems tend to resemble the communication structures of the organizations that create them.
Nathan Schneider • Governable Spaces: Democratic Design for Online Life
Brie Wolfson added
Conway’s Law:
‘For any organization that builds systems, the systems they produce reflect the communication structures of that organization.’
If your organization is inefficient and disjointed, or dictatorial and myopic, it shows in your products.
‘For any organization that builds systems, the systems they produce reflect the communication structures of that organization.’
If your organization is inefficient and disjointed, or dictatorial and myopic, it shows in your products.
James Rosen-Birch • Tweet
rob hardy and added
Conway’s Law doesn’t leave anyone guessing about how to make organizational communication structures work for the greater good. As the conclusion of Conway’s paper states: We have found a criterion for the structuring of design organizations: a design effort should be organized according to the need for communication.
Vaughn Vernon • Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))
"Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure."–Marvin Conway
Wikipedia • Conway's law
Brie Wolfson and added
A corollary of Conway’s Law is that an organization’s structures themselves can be constrained by the architectures that they designed many years earlier. And without intentional action, it’s a Catch-22. “We cannot solve our problems with the same level of thinking we used when we created them,” Einstein said. An example of this antipattern is a mi
... See moreJonathan Smart • Sooner Safer Happier: Antipatterns and Patterns for Business Agility
A corollary of Conway’s Law is that an organization’s structures themselves can be constrained by the architectures that they designed many years earlier. And without intentional action, it’s a Catch-22. “We cannot solve our problems with the same level of thinking we used when we created them,” Einstein said. An example of this antipattern is a mi
... See moreJonathan Smart • Sooner Safer Happier: Antipatterns and Patterns for Business Agility
Why do large systems disintegrate? The process seems to occur in three steps, the first two of which are controllable and the third of which is a direct result of our homomorphism. First, the realization by the initial designers that the system will be large, together with certain pressures in their organization, make irresistible the temptation to
... See more