Just heard about Conway’s Law this weekend and even though it was coined in 1968 it seems incredibly relevant. Essentially the law states that systems (especially software) will reflect the organizational structure that created them. Going beyond the obvious aspect of organization of features, information architecture etc. it goes on to state that the software/system will reflect the disfunction of the organization that created it.
Think about this next time your trying to implement something with a large, extended team.
Also what does this say about the organization between such companies as flickr, google, 37signals etc.
Also, does it imply that if we organize our teams with the software/sytems/products/services we want to create in mind will we create a better software/sytem/product/service?
If we want to create web2.0ish tools that are “simple tools, loosely coupled” should we have “simple teams, loosely coupled”?
{ 2 trackbacks }
{ 3 comments… read them below or add one }
> Just heard about Conway’s Law
Just curious, whom did you hear it from?
I heard about Conway’s Law a couple of months ago, and found it, too, incredibly relevant for our company and for the whole industry (or set of industries) we are working in. Since then, I have been talking about it to everyone, and I have noticed that this “ideavirus” has now been resurrected and is now spreading fast
Actually I heard about it from some folks at Ideo
I’d forgotten about Conway’s law, but I think it’s right on.
Our research into experience design teams shows that the culture of the design organization is very important to the outcome of the experience. Organizations with a culture that thinks holistically are very likely to produce holistic experiences. Organizations that segment and silo will produce experiences that feel detached and conflicting.
Good find!
Jared