2 ms·
This is a symptom of the strongly autonomous teams that Google uses. Autonomous teams are great in that allow the team to control their own destiny. However, t
by nl 15y ago
This is a symptom of the strongly autonomous teams that Google uses.
Autonomous teams are great in that allow the team to control their own destiny. However, they don't make for a great cross-product experience.
The alternative is the Microsoft way - where all products are supposed to work together and support each other. The problem there is that Microsoft is very, very slow to ship stuff as everything needs to be synchronized.
Facebook has it easy - they only have one product. Apple has this problem occasionally, but doesn't have the breadth of product Google has.
(I'd note that many people think Google should become more startup like. In effect, that is asking for more chaotic product development - no startup co-ordinates feature releases across as many products as Google has to)
- ahalam 15y agoThe teams maybe autonomous in Google but I'm sure that they are aware that they are duplicating functionality and thus really harming the company. What the heck the are product managers and their managers doing at Google? Building their own little empires?
- nl 15y agoWhat the heck the are product managers and their managers doing at Google? Building their own little empires? It's not as simple as that. In every case, if you look carefully there are good reasons why each version operates like it does. Each team is trying to make the best possible product. The lack of oversight doesn't necessarily indicate empire building.