I’d like to hear more about in what specific ways is google bottom-up but the article is kinda shallow. Are the roadmap items that teams commit to driven by ICs, and if so does that contribute to becoming bloated and bureaucratic? How?

What does a top-down approach look like by comparison for a company as large as Google, and is that even feasible, given that top management are likely to be many layers away from code being written?

Or is it something like when a company gets past a certain size then it has switch management styles?

Was hoping the article would get closer to talking about these ideas but it’s lacking in substance imo.