4 ms·
Or, you built a poorly architected piece of software that replicates your organizational structure.
by kkirsche 4y ago
Or, you built a poorly architected piece of software that replicates your organizational structure.
- jrockway 4y agoIt's basically a law of the Universe that your software will look like your org structure. You have to treat it as a hard engineering constraint, just like you'd treat seek latency on a spinning disk, or the speed of light between two data centers. You can't increase the speed of light, but you can still function. Treat org constraints like that.
- wan23 4y agoOr, you build a well architected piece of software that replicates your organization structure if the people (director+) who are in charge of the org structure do their jobs well.
- babyshake 4y agoAny organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. — Melvin E. Conway
- jbn 4y agoI guess the trick is to flip this by modeling your organization to the system design (i.e. create teams around the components of the system, not components around pre-existing teams). This is easier said than done, and as architecture changes one needs to adapt the organization structure... it's not a complete solution, as 1/I've seen this cause games of musical chairs happen that essentially stall the work and 2/ creating silos make cross-cutting concerns fail to be addressed...
- alostpuppy 4y agoHahaha. Perfect.