At this point, I think issue is not about products Google build, it is about how Google put their incentives in place. - Build new shiny thing -> promoted - Support shiny thing -> it's not difficult, everyone can do it This type of culture is influencing future direction of Google products, they put together awesome team, solve problem and get from 0 to 1, then team moves on, others don't have incentive to make 1 to…
This is a meme that people love and there's some truth to it, but also a number of ways in which it's inaccurate. Sure you can get promoted for launching a new thing, but you can also get promoted for fixing a first pass implementation, for scaling something from a small user base to a large user base, and so on, as long as you can show the "impact" of the change – whether that's revenue, savings, productivity, impro…
To estimate the impact, we need to run controlled experiments. And we have lots of A/B testing infrastructure to help us run those experiments when it comes to launching shiny new things. But when it comes to maintaining things, not so much.
So if there are two possible projects of equal difficulty and impact that you could take on, and one is to launch a shiny new thing and the other is to maintain an existing thing, you're always better off launching the shiny new thing because the cost of quantifying your impact will be low, whereas had you chosen the maintenance project, quantifying your impact would be prohibitively expensive.
And that's why building shiny new things dominates maintaining existing things: you get full credit for your work, not a small fraction.