There was a great blog on here where an (ex maybe) Google engineer first pointed out this problem and a good reason why he left since he realized this too late and all his time making huge performance improvements in existing products meant nothing come review time and all his colleagues got promoted.
Since then it's been documented several times:
https://www.warp.dev/blog/problems-with-promotion-oriented-c...
https://twitter.com/petergyang/status/1576985038511448064
"Show me the incentives, and I'll show you the outcome"
Maintaining and improving existing projects is a footgun at Google because of the way their promotion structure works. Unless they've changed something fundamental about their review process, of which I've not heard, it's still the same. This launch of a new product rather than naturally being integrated into an existing one that already fills this space and has adoption seems to prove its still the case.