Every developer productivity metric I have used measured something real, and every one stopped meaning that thing within a quarter. Not because anyone cheated. Because people are smart and metrics are visible, and once a number matters, the work bends toward the number.
Why I think this is structural
The output of engineering is a change in a system. The value of that change is only visible later, somewhere else, in a customer who can do something they could not before, in an outage that did not happen. The distance between the work and its value is long, and every metric that is quick to collect measures something on the near side of it.
Pull requests, commits, story points, lines of code, cycle time. All are measures of motion, and motion correlates with value only when nobody is watching it, because motion is easy to produce and value is not.
I have watched cycle time fall as work got sliced into pieces that each moved quickly and together took longer than before. Nobody did anything wrong. The metric just taught people what it wanted.
What a manager is actually trying to learn
When I ask myself why I want a productivity number, the honest answers are few. Is this team healthy, or is something wrong that I cannot see. Is the investment in this area paying off. Did the new tool or the new process help. Who needs support.
None of those is answered by a single number, and I think the search for one is where measurement goes wrong.
The measures I still trust
Delivery outcomes over time. Not how many things shipped but whether they did what they were meant to, measured by whoever they were for. This is slow, and it is the only measure that points at value.
The questions the team asks. A team that is stuck asks about blockers, environments, and approvals. A team that is healthy asks about the problem. Listening is not a metric, but it is the fastest signal I know.
Change failure and recovery. The share of changes that cause a problem and the time it takes to recover are the hardest to game, because gaming them means breaking less and recovering faster.
Whether people say the same thing in private. If the dashboard is green and the one-on-ones are full of frustration, the dashboard is wrong.
What I try not to do
I try not to compare individuals on any output measure, because individual output is a property of what the person was assigned, who they were unblocking, and what they were cleaning up, none of which the number sees. I try not to put a motion metric on a wall, because that is the moment it stops working. And I try not to promise anyone a single number that says whether engineering is productive, because I do not think it exists, and the honest thing is to say so.
Photo source: https://photos.robertstowe.com/niagara
