Thanks for this post. Velocity can easily become a vanity metric for leaders because it measures activity, not impact. In fast-moving, AI-enabled environments, it can even end up reflecting internal performance signaling more than external value creation.
If we’re using velocity as a productivity metric, then we should first ask: what do we actually mean by productivity? Only then can we decide whether velocity is the right measure. For now, velocity is still measured but not as an isolated metric.
Your point that velocity can end up reflecting internal performance more than external value is nuanced - I like it! How do you determine productivity for your teams? Do you have a standard or is it project/product dependant?
Thanks for sharing your article, I'll check it out.
Thanks for this post. Velocity can easily become a vanity metric for leaders because it measures activity, not impact. In fast-moving, AI-enabled environments, it can even end up reflecting internal performance signaling more than external value creation.
If we’re using velocity as a productivity metric, then we should first ask: what do we actually mean by productivity? Only then can we decide whether velocity is the right measure. For now, velocity is still measured but not as an isolated metric.
I wrote a post last week about this here: https://theaitrain.substack.com/p/how-i-changed-the-way-my-team-measures
Thanks for your comment!
Your point that velocity can end up reflecting internal performance more than external value is nuanced - I like it! How do you determine productivity for your teams? Do you have a standard or is it project/product dependant?
Thanks for sharing your article, I'll check it out.
I think it's project- and product-dependent. To me, productivity is about choosing measures that align with the team's purpose.
Yes, purpose is paramount. Thanks Just J!