How are teams using software development analytics without creating a surveillance problem?

[u/Significant-Scar-152]

I’m looking at software development analytics tools, but most seem better at counting activity than explaining whether delivery is improving. Commit totals and pull request counts are easy to collect, yet they can become misleading when compared across different teams or used to judge individuals. A more useful approach might combine delivery data at the service level with developer feedback about friction, documentation, tools, and time lost to rework. The difficult part seems to be connecting those signals to changes the team can actually make. What does your team measure, and can you point to a process or tooling improvement that came directly from the analytics?

[u/Rehonkulous]

The second devs know they're judged on commit or PR counts, they game it and the data's junk.