This is a really interesting point, something this makes me think of is how productivity is also somewhat context dependent on what's going on in the workflow.
Certainly it's a paradox that if you define or measure something incorrectly you can encourage people to pursue things that inappropriately game those measures or goals!
Have you felt like any measures you've seen are particularly problematic? Very curious!
Yes, a lot throughout my career.
An example would be "Velocity" metric in agile software development teams. That number shows on average how much work gets done by that team in a sprint.
It is fine to use that number as a guideline for business estimations, but developers shouldn't care about that number. devs should only care about the product they are building and achieving the sprint goal.
developers should care about other numbers and metrics.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a really interesting point, something this makes me think of is how productivity is also somewhat context dependent on what's going on in the workflow.
Certainly it's a paradox that if you define or measure something incorrectly you can encourage people to pursue things that inappropriately game those measures or goals!
Have you felt like any measures you've seen are particularly problematic? Very curious!
Yes, a lot throughout my career.
An example would be "Velocity" metric in agile software development teams. That number shows on average how much work gets done by that team in a sprint.
It is fine to use that number as a guideline for business estimations, but developers shouldn't care about that number. devs should only care about the product they are building and achieving the sprint goal.
developers should care about other numbers and metrics.