Why code describes business
summary
Conway's 1968 paper gives the central claim: organizations that are tightly coupled produce tightly coupled systems, validated later by MIT and HBR studies. Practical fixes shown are value stream mapping to find costly handovers, reorganizing into cross‑functional teams that own code into production, and adopting continuous delivery and lean/DevOps practices. Examples include firms that reduce lead time dramatically and markets with high churn in the top 100, suggesting the death of the IT organization unless structures change.
AI-written summary · about
chapters (4)
related talks
50mConway's Law: When Best Practices Are Not Enough
49mConway's Law: When Best Practices Are Not Enough
01h 00mMicroservices and the Inverse Conway Manoeuvre
41mHow I Finally Stopped Worrying & Learnt to Love Conway’s Law
34mCode as Culture How Organization Shapes Your Code
58mMicroservices and the Inverse Conway Manoeuvre
47mMicroservices and the Inverse Conway Manoeuvre
05mcultures and microservices