15 ms·
Conway’s Law (2022)
- User23 4y agoUnderstanding this is of especial importance for remote first organizations.
- walterbell 4y agoWith Zoom-in-the-Middle communications security.
- User23 4y agoYou kid, but understanding the dynamics of various remote forms of communication is exactly what I mean.
- walterbell 4y ago______ has entered the chat!
- dang 4y agoHere's Conway's original paper from 1968: http://www.melconway.com/Home/Committees_Paper.html http://www.melconway.com/Home/Committees_Paper.html Related: Conway's Law - https://news.ycombinator.com/item?id=33604268 https://news.ycombinator.com/item?id=33604268 - Nov 2022 (1 comment) Bliki: Conway's Law - https://news.ycombinator.com/item?id=33289746 https://news.ycombinator.com/item?id=33289746 - Oct 2022 (1 comment) Ask HN: Is the inverse of Conway's Law valid, in your experience? - https://news.ycombinator.com/item?id=31066817 https://news.ycombinator.com/item?id=31066817 - April 2022 (2 comments) How do Committees Invent? (1968) [pdf] - https://news.ycombinator.com/item?id=30739888 https://news.ycombinator.com/item?id=30739888 - March 2022 (5 comments) Conway's Law - https://news.ycombinator.com/item?id=29883762 https://news.ycombinator.com/item?id=29883762 - Jan 2022 (12 comments) Thoughts on Conway's Law and the Software Stack (2019) - https://news.ycombinator.com/item?id=24811692 https://news.ycombinator.com/item?id=24811692 - Oct 2020 (24 comments) Conway's Law - https://news.ycombinator.com/item?id=23501644 https://news.ycombinator.com/item?id=23501644 - June 2020 (2 comments) Conway's Law - https://news.ycombinator.com/item?id=22557116 https://news.ycombinator.com/item?id=22557116 - March 2020 (1 comment) Conway's Law Is Real - https://news.ycombinator.com/item?id=19872131 https://news.ycombinator.com/item?id=19872131 - May 2019 (2 comments) Thoughts on Conway's Law and the Software Stack - https://news.ycombinator.com/item?id=19485964 https://news.ycombinator.com/item?id=19485964 - March 2019 (22 comments) Conway's Law - https://news.ycombinator.com/item?id=16856537 https://news.ycombinator.com/item?id=16856537 - April 2018 (51 comments) Twitter, Reddit and Conway's Law - https://news.ycombinator.com/item?id=16030694 https://news.ycombinator.com/item?id=16030694 - Dec 2017 (1 comment) Linux follows an inverse form of Conway's Law - https://news.ycombinator.com/item?id=14477680 https://news.ycombinator.com/item?id=14477680 - June 2017 (58 comments) Conway's Law - https://news.ycombinator.com/item?id=14166113 https://news.ycombinator.com/item?id=14166113 - April 2017 (1 comment) Conway's Law - https://news.ycombinator.com/item?id=9631810 https://news.ycombinator.com/item?id=9631810 - May 2015 (26 comments) Conway's law - https://news.ycombinator.com/item?id=9314445 https://news.ycombinator.com/item?id=9314445 - April 2015 (2 comments) How Do Committees Invent? (1968) - https://news.ycombinator.com/item?id=8458471 https://news.ycombinator.com/item?id=8458471 - Oct 2014 (9 comments) Conway's Law: How Do Committees Invent? - https://news.ycombinator.com/item?id=4727178 https://news.ycombinator.com/item?id=4727178 - Nov 2012 (1 comment) Conways' Law - https://news.ycombinator.com/item?id=437786 https://news.ycombinator.com/item?id=437786 - Jan 2009 (2 comments) Conway's Law (A software system will resemble the organization that built it) - https://news.ycombinator.com/item?id=82997 https://news.ycombinator.com/item?id=82997 - Nov 2007 (3 comments)
- gjvc 4y agoa hazard of the practice of listing all previous related articles like this might suggest the content of the newly-posted article is likely to be of little value
- atleastoptimal 4y agoEveryone's favorite law to cite but I rarely see a lot of examples
- walterbell 4y ago2011-era satirical org charts, https://www.globalnerdy.com/2011/07/03/org-charts-of-the-big-tech-companies-plus-an-enhancement/ https://www.globalnerdy.com/2011/07/03/org-charts-of-the-big...
- 082349872349872 4y agoHave you ever worked in a (>30)-person company? Edit: as dang posted the original article ("a principle with much broader utility than in software engineering"), I guess another example is the "county sheriff" and their occasionally newsworthy antics in the States. Reading about them from a country where counties are not a thing (nor do we suffer from their lack) makes me think the politicisation of the sheriff's office may be a less software-oriented example of Conway's law.
- bee_rider 4y agoHmm, I’m not sure. I think that example would need to be fleshed out a bit (at least, I don’t see it, but then I live in the US so maybe I’m missing the forest for the trees). Conway’s law is about the structure of the thing being built mimicking the organizational layout of the people building it. The county sheriff is just the sheriff attached to that unit of administration. It seems more like if Conway’s law was the observation that shape of the management tends to match that of the org chart. It is not really a correlation so much as a tautology.
- 082349872349872 4y agoFleshing out the example: as far as my experience goes, there is no governmental function that would be more effectively handled at a "county" level. Yet in the States the unit of administration exists, so law enforcement solutions incorporate (heh) county sheriffs departments (even when these are composed of personnel with no real law enforcement background).
- GauntletWizard 4y agoI don't view Conway's law as casting as negative a tinge as most seem to. It makes sense that responsibilities be split roughly along the same lines as they are in physical organizations, especially in orgs where software is not a hermetic black box but represents business processes. Groups probably have need to twiddle with the representations, and drawing the same lines of responsibility as permissions makes a lot of sense there. As a contrived and probably nonsensical example: if you have a widget factory, and you have two departments, sales and fulfillment, it's often better to represent a sales order as "An immutable list of items sold and prices, and a mutable list of references to fulfillments that satisfied that order" over "a list of items sold, prices, and how many have been delivered", with a separate object that is the fulfillment. Those are different departments, they move at different rates, and edit permissions for each should be limited to their respective orgs.
- deleted 4y ago[deleted]
- flappyeagle 4y agoYou described a functional department structure. Conway’s law is often helpful in those circumstances. Divisional org structures are where it can become problematic.
- metafunctor 4y agoIt's almost as if organizations tend to build tools that fit their needs. /s
- euroderf 4y agoAnd then they get SAP, and have to rewrite their organization to fit their ERP.
- cptcobalt 4y agoFleeting thought: is there any significant company that grew to a big (yet effective) size that's also a great example of NIH'ing their ERP? (edit: I mean, good homegrown ERP tooling, not excel sheets connected to a database)
- satisfice 4y agoAll Conway’s Law means is that to build a system (from new components, anyway) that work really well together it is very helpful for the builders of those new components to communicate with each other during the process. This is a fine heuristic, but it can be interpreted in different ways as you see fit. For instance, since I advocate for professional testing (rather than amateur testing that Agilists prefer) I say, by Conway’s Law, that testers should be gathered together in one team, rather than scattered around in little Scrum teams. Testers benefit more by working together than they do by hanging around developers, since only coding testers really can deeply understand the devs and the code, and when they try they simply become junior developers and lose all the critical distance that makes independent testing effective. By Conway’s Law, the “Whole Team” approach really just coopts testing and isolates testers (like being the only sober guy at a party), and puts the tester under pressure to get along instead of critique the product. Fowler poo poohs the idea of independent testing in his article, but he is not a professional tester and I think he hasn’t thought this through. The couple of times I met him he was friendly and listened well, though.
- kitd 4y agoNote that Conway's law states that systems will be structured according to how humans communicate. Often, for dev teams, that aligns with how the APIs interact, but for, eg, testing teams, doc teams, devops, etc, that communication might be all the non-functional stuff that doesn't have to be in code per se but is still valid communication, and will still drive org structure per Conway. So I think your idea is still compatible with Conway.
- q7xvh97o2pDhNrh 4y ago> it is very helpful for the builders of those new components to communicate with each other during the process. IMHO, it's about communication and incentive structures. Each person is naturally going to optimize for the incentives of their local team, so the job of the organizational-designer is to align these incentive structures across teams. > since I advocate for professional testing (rather than amateur testing that Agilists prefer) ... Testers benefit more by working together than they do by hanging around developers, since only coding testers really can deeply understand the devs and the code, and when they try they simply become junior developers and lose all the critical distance that makes independent testing effective. This is really interesting to me, since I largely believe the opposite: Engineers should be writing their own tests, because otherwise they won't be incentivized to write good, clean, maintainable, testable code. Can you share more about your take on this? Sounds like you've probably had similar conversations before — any particular case studies or data you like to lean on?
- jboy55 4y agoWhat I've found is that any large refactoring project that works against Conway's law will fail, until the plan adjusts to the org structure. This can be very explicit, in that one group will refuse to support it, or latent, in which teams won't use the new project until it is reworked to support them. The sad thing is that pretty much every large refactor that I've seen has started as an explicit attempt to remove the 'smell' of the software architecture being built off of the org structure.
- anonymouskimmer 4y agoConway's Law seem like a specifically social instance of Nietzsche's Beyond Good and Evil aphorism #6: https://en.wikiquote.org/wiki/Beyond_Good_and_Evil https://en.wikiquote.org/wiki/Beyond_Good_and_Evil > Gradually it has become clear to me what every great philosophy has been: namely, the personal confession of its author and a kind of involuntary and unconscious memoir; also that the moral (or immoral) intentions in every philosophy constituted the real germ of life from which the whole plant has grown. I originally came upon this quote in the context of a comparison of personality theories (Dave Kelly, Ptypes).
- osullivj 4y agoEven Wittgenstein's Tractatus?
- christo 4y agoOK so I just read the wikipedia page on that and I don't understand the origin of your uncertainty. What is apparent and certain is that you know it better than I do and I'm interested to understand your thinking. That and it's dope that we're only two branches offshoot from software architecture.
- anonymouskimmer 4y agoProbably. It is possible to think and write in another's mode. But it's difficult to do consistently, and it certainly isn't satisfying to the person doing so.
- molly0 4y agoI remember seeing a great explanation of Conway's Law by Casey Muratori: https://youtu.be/5IUj1EZwpJY?t=697 https://youtu.be/5IUj1EZwpJY?t=697 (The whole talk is good but Conway-s law starts at 11:37)
- fwlr 4y agoCame here to post this, yeah, it’s a fantastic and detailed explanation of Conway’s law. Casey provides a worked example at 19:50.
- concerned_ 4y ago[flagged]
- gorgoiler 4y agoWe put a horizontal team through a silo’d org structure with great success. The team is Release Engineering in all but name and we used the project of “make releases faster” to send a shock wave back up the org in order to bring a once-deliberately segregated product / org structure much closer together. The goal was to do so in the name of speed and flexibility. As with any shock wave, the healing energy dissipated the further it travelled. We don’t expect to be able to effect complete removal of product silos all the way up one end of the org by applying change from the release process from all the way at the other end. However, the wave propagated quite a long way. We only have 10^1.9 engineers which helped make the changes tractable and was also the basis for wanting to move to a much faster org structure. In short, we had a micro teams and microservices structure that would suit a team of 8,000 when in reality there are only 80 of us (series B, 9 digit valuation) so we drilled a hole in the side of the complicated old ship and got everyone into the same life/speedboat instead.
- Borrible 4y agoOrganizations are models of reality, with their communication structures reflecting past experiences and realities. As reality changes, these models may become outdated. However, organizations often invest more resources in maintaining the existing model instead of adapting to new realities. Conway's Law highlights this inertia by emphasizing the relationship between an organization's communication structure and the systems it designs. The natural evolution of a social model from tool to symbiont to parasite.
- anonymouskimmer 4y ago> The natural evolution of a social model from tool to symbiont to parasite. To be generous it seems like a child gradually turning into a cranky oldtimer.
- deleted 4y ago[deleted]
- ygouzerh 4y agoHow does this law works in Remote companies, where everyone is working remotely ?
- dxdm 4y agoThe same, at least in the remote-first org that I'm in Remote still has teams and department with reporting lines and clusters of incentives, responsibility, and who communicates how often with whom and in what manner.
- ajuc 4y agoYou still have groups of people who communicate hourly, daily, weekly, etc.
- christo 4y agoWhat this means to me is that you can't change your organisation with software alone. And I believe it was Martin Fowler who said to me "If you can't change your organisation, you should change your organisation".