3 ms·
This is a meme. Yes, you need to change something about the state of the world but that change absolutely does not need to be launching a product. I work in the
by UncleMeat 5y ago
This is a meme. Yes, you need to change something about the state of the world but that change absolutely does not need to be launching a product. I work in the Core organization, which builds tooling for the rest of the company. My org within that has among the highest promotion rates (even to high levels) in the company and the primary thing we focus on is the sort of grungy "keep everything functioning" work that everybody says is anathema to promotions.
It is no secret that Google's product strategy is a mess. But I'm not convinced this is caused by the promo process. For communications strategy I think it is instead the following:
1. Messy code stacks make surviving tool deprecation a problem.
2. Google seems to be bad at staffing for proactive protection against maintenance work. If a product is working, staffing dwindles to match the maintenance load. But if suddenly a huge mandate comes along like a stack switch, it is not easy to get the heads you need to handle that spike in maintenance. Instead, the product gets triaged or dies.
3. It is really hard to push past 1B users of anything, and growing populations outside of the US and Europe are not desktop focuses, encouraging a "mobile first" solution that leaves desktop integration in the dust.
- contravert 5y agoHow many PMs does Core have compared to other PAs? The problem isn’t really with SWEs but with the entire incentive structure of PMs and the product management chain. They in turn are able to get more SWE headcount for these unfruitful ventures and end up failing upwards.
- UncleMeat 5y agoCore seems to have fewer PMs but we have similar problems with triaged products due to lack of heads. The PMs we do have also struggle with getting heads just as much as the SWEs do. At the very least, I think it is clear that Google’s product failings are not just a result of the promo system.
- tdeck 5y agoI'd suggest a 4th reason: Google has so much money and so many high-traffic properties that it can keep a poorly designed or unpolished product going for years, more than long enough for the original people who designed and built it to move on/up inside the company. Google will just push the product on the front page of some existing property to bump traffic, or get creators/developers to use it in hopes of boosting their existing search rankings, or give away the product for free. Every company would try to do these things but Google has a big advantage. This allows Google to be lazy about product-market fit and avoid asking the hard questions like "is this thing really better than the alternative" and "what's the ROI for people who adopt this". I worked on what I'd consider a failed product, and there was no explicit acknowledgement of that fact ever, we just waited 3 years and quietly turned it off. A more drawn-out version of the same thing happened with Google Plus. There was never anything like a "product postmortem".