3 ms·
I don't know anything about the inner workings of Google. However, if they were all mostly doing that kind of thing, it's probably what was expected and reward
by tyingq 6y ago
I don't know anything about the inner workings of Google. However, if they were all mostly doing that kind of thing, it's probably what was expected and rewarded by whoever they worked for.
If, for example, finishing projects on the original projected timeline is heavily weighted...you get the ruthless scope cutting you mention. Or, if compensation is tied to team size, you get empire building.
- enos_feedler 6y agoYes thats exactly it. the problem was in OKR setting and expectations. The PMs got unfairly rewarded for things that didn't matter. Android releases on a regular cadence and I think just meeting the release deadline with some set of namable new things was enough to receive the bulk of performance compensation. It didn't matter if app developers were still jumping through painful hoops to get Camera detection, usage, debugging, etc working across a highly fragmented ecosystem of chips and sensors. It wasn't part of the OKR to fix it, and it certainly wasn't fixable within an OKR planning cycle.