> The only way your outcome is unmeasurable is if your outcome had no observable impact. I don't think this is correct? Your work having observable impact and

> The only way your outcome is unmeasurable is if your outcome had no observable impact. I don't think this is correct? Your work having observable impact and being able to show exactly what observable impact your work had in a quantifiable manner are two very different things. I feel this is a huge problem at Google, where performance reviews/promotions are supposed to be based on objective measures. If you fix a lot of bugs, the end user might be much happier. However, to quantify exactly happy you need to have some existing infrastructure, and even if you do have that infrastructure, how do you know whether they are happy because of the bugs you fixed or the bugs someone else fixed? It may be possible but is not really worth the effort for a company to invest in. So, what ends up happening is people (who care about perf/promotions) fight for the projects which will give them the most easily measurable impact, and ignore other things which may well be very important to a project or company but are difficult to measure. Ideally, your performance should only be rated on things that were actually in your control. Admittedly, I don't know how one would do this though.