May 19, 2026
6 min read
Insights
Why Velocity Is a Terrible Performance Metric
A practical look at why velocity makes a poor performance metric, what it distorts in team behavior, and how to use it as planning context without turning it into pressure theater.
Velocity is supposed to support planning, not become a score
Velocity is a backward-looking signal. At its best, it helps a team notice roughly how much sized work it has completed over time under real conditions.
That makes it planning context, not a quality grade and definitely not a measure of how hard people are trying. The trouble starts when teams stop using velocity to understand planning patterns and start using it to judge performance.
Metric misuse
Velocity becomes harmful when it stops being context and starts being a target.
Velocity as target
Once teams are judged on the number, the metric starts driving behavior instead of describing delivery reality.
Gaming pressure
People adapt to the score, whether that means inflating points, splitting differently, or avoiding harder work.
Cross-team distortion
Comparisons flatten away context and quietly assume that different teams measure the same thing in the same way.
Planning signal lost
The more a metric becomes performance theatre, the less useful it becomes for real planning or forecasting.
Planning context only
Velocity is only useful when it stays local, contextual, and subordinate to better delivery judgment.
Why it turns bad as soon as it becomes a target
The moment velocity becomes something people are judged on, the incentives around it change. Teams stop asking whether the signal is useful and start asking how the number looks.
That usually makes the number less honest, not more meaningful. Metrics become easiest to improve when they are easiest to game.
Performance pressure distorts estimation
If velocity is treated like a performance metric, the cleanest way to improve it is often not better delivery but different estimating behavior. Teams start inflating points, slicing work differently, or avoiding estimates that might make the number look smaller.
At that point velocity is no longer reflecting the work. It is reflecting the pressure around the metric.
It also punishes the wrong things
Velocity as a score often punishes work that is valuable but harder to express as point accumulation. Quality improvements, dependency cleanup, cross-team support, onboarding, or necessary design work can all become invisible or politically inconvenient when the dashboard only cares about making the number go up.
That pressure can quietly push teams toward easier-looking throughput instead of healthier delivery choices.
Comparing teams by velocity is especially misleading
Different teams size differently, carry different risk profiles, and work in different delivery conditions. Comparing their velocity numbers as if they live on one shared scale usually creates false certainty and bad management behavior.
Even if the numbers look comparable, the underlying estimation systems often are not.
What velocity can still do well
Velocity can still help when it stays in its lane. It can show whether the team's historical sizing and delivery pattern is broadly stable, and it can offer one input into sprint planning when combined with real current capacity.
The key is to treat it as context, not as judgment.
A better question than 'how do we raise velocity?'
A healthier question is usually: are our estimates becoming more honest, and are our commitments becoming more realistic? Those questions help the team improve planning quality instead of chasing a metric that can be gamed faster than it can be trusted.
The goal should be better decisions, not prettier charts.
TL;DR
- Velocity is useful as planning context, not as a performance score.
- Once it becomes a target, teams start optimizing the number instead of the planning signal.
- It distorts estimation behavior and punishes valuable work that does not show up cleanly in point totals.
- Comparing teams by velocity is especially misleading because the numbers are not on one shared scale.
- Velocity becomes useful again when it stays a local planning signal instead of being turned into a score for judging people.