Especially because there are also skill differences and the differences in job title and salary that come with that. So the level of difficulty of the work people get to do is also different, and so on.
The problem is people realise they can gain as much from playing political games as they can from improving productivity. Once that starts everything goes to shit.
I don’t understand your position. Is it that all developers are equally productive, or that they do vary in productivity but it is immeasurable, an æther, with literally zero signals one could possibly mine to see how valuable a developer is to the team?
Soccer is a good metaphor because it's EASY to measure/see the value a good player that does not shoot a lot of goals make. In programming this is not the case.
It's certainly the case that managers that want hard numbers and don't know how to code won't be able to understand the situation at all. This is why this McKinsley nonsense is so dangerous.
"Better" isn't linear. It can multiply, and it can be highly dependent on the rest of the team.
Can you elaborate?
So you're saying that it's impossible to measure developer productivity at all, since it's cognitive work? Strong disagree.
All of us here that work with other developers know that some of their peers get more done than others. Or conversely, that there's a few in the team who don't seem to get much done. The minute you make even that simple assessment, you've measured productivity.
One of the jobs of eng managers is to then make this measurement as accurately, realistically, and fairly as possible. This guides bonuses and raises, which should reflect people's contributions.
I'm not defending McKinsey's proposal here, but I agree with the general notion that it's possible to measure productivity and this is something management should always be doing.