Earlier quoted context omitted.
I think “rediscovering” the old ways of operating is a charitable interpretation that makes it sound like these patterns are somehow better. Silos and fiefdoms don’t benefit the company, they benefit the professional managers that are using them to grow their careers. I subscribe to the interpretation that sufficiently successful companies inevitably attract ladder climbers whose goals are personal advancement at all…
Silos and fiefdoms allow small gelled teams who know and trust each other, have similar levels of competence, and sit physically near each other to put their heads down and execute with extraordinary speed and quality. Once silos are broken down and cross-team/cross-org collaboration becomes valorized, everything is strangers and Zoom meetings and time zones and Process and maybe if you’re lucky one person in your pa…
Google in the mid aughts still had tightly aligned teams with clear priorities. But they were also transparent in what they were doing, and open to collaboration where it made sense. Teams felt empowered to reject requests that would trip them up, but also empowered to do small things to help another team (and got rewarded for doing so).
The reality at a large org is you’re going to have dependencies. In my experience, highly-siloed orgs have tremendous coordination barriers to even the smallest request across teams. Your one-line API change didn’t make it onto your dependency’s roadmap this quarter? Too bad, try again in three months.
And I’m not sure we have the same understanding of “fiefdom.” I’m talking about the pattern where middle managers try to grow their headcount as large as possible without a clear purpose other than building status within the org. This often manifests as disparate and disjoint teams aggregated under a leader who has little understanding or care as to what exactly it is they’re doing. It is hard to find value in this arrangement.