↓ Skip to main content

It’s a bit counterintuitive but I think it’s a good point that all the efforts to more and better coordination are harmful. We should have less coordination which will inevitably lead to more work between teams, but that is work you should be doing anyway. I think teams are in general very heavily underfacilitated.

When we change the system later, strong boundaries make those changes faster. Deep coordination makes those changes harder: the tight coupling still exists but the armies have moved on, the armies of project managers who heroically held together that initial release.

https://jessitron.com/2021/08/02/better-coordination-or-better-software/

Alper Cugun
Author
Alper Cugun

Related

I’ve been thinking along these lines and a DNA type meeting as an informal place of leadership and sparring sound great. In our case, I think I’ll call it “Debt and Architecture”.

Slack has an interesting S-Curve based approach to adopting new technologies where they mention that getting through the trough of adoption is more like product-work than anything else.

The correct sequence is to start with a business goal, translate that into a technical strategy and have architectural initiatives follow from that.