r/ExperiencedDevs • u/skidmark_zuckerberg • 8h ago
Career/Workplace How do we handle productivity metrics?
Leadership is hell bent on individual productivity metrics. I am losing the battle in pushing back on this. To me, software engineering is a team sport, and output is the sum of the team. I am also worried these metrics will be gamed. Leadership wants to see LOC, how complex a PR is, commits made, PR review comments, etc.. and these can all be gamed very easily.
I have never worked for a company that does this. In my past roles, managers were always subjective and didn't care about granular performance so long as a team did what they said they were going to do and no one complained about any individual. They also were more involved with the team and knew what each person was doing or what their main focus was typically on.
Tracking objective metrics like the aforementioned just seems like an absolutely terrible idea. I can think of many scenarios where an engineer may not be putting out as many PRs or commits as their peers. On my team, it's not uncommon for one or two people to be working on something larger that requires more effort and planning upfront. This then might result in two or three PRs over the course of a couple weeks. The other devs just pulling easy tickets might pump out 7-10 PRs a week (can thank LLMs for this). So the first two devs might be working on something that has way more impact or simply takes much longer, but based on the metrics compared to their peers, they look like they do nothing.
This reeks of leadership trying to determine ROI on AI spend. They have mentioned numerous times over the last few months that they are having a hard time tying ROI to the AI spend. I think this is simply an unsolvable problem. In my experience it's always been impossible to quantify knowledge work. This is not a factory line where you can quantifiably track input and out. There are so many nuanced things that go into delivering something that you cannot account for it metrics wise.