Amazon is proud of being data driven and that is fine when the data is chosen correctly and applied wisely. Here are some examples of applying it wrongly, but still sticking to the point of "I am driven by data" crap.
A manager I worked for tracked individual story points delivered by members in sprints and used those points to compare and push developers for delivering more. It doesn't matter whether you were oncall during one of those 2 weeks sprints(and didn't work on sprint stories) or the other person worked 18 hours a day - you have to be on par. If you try to explain that is not how sprints should be treated and it is all about team effort - he would brand you as having incomplete understanding of scrum!
Another manager in Dublin uses the number of code commits/reviews you sent out to measure your delivery effectiveness. A code change or configuration change that takes 2 minutes is counted the same as a code change you would be working on for 4 days in introducing a new feature. I wish he had the backbone to publish his data driven logic of counting code commits to measure developer effectiveness to the wider developer community within the company and seek feedback.
All those measurements are done secretly by the way. There is no upfront notice of "this is what I am tracking to measure developer's delivery effectiveness" heads up. If you believe you are right about your data driven "developer effectiveness measure", why are you coy about it?
