May 19, 2026
6 min read
Metrics anti-patterns
How Teams Accidentally Game Velocity
Why teams accidentally game velocity, even without bad intent, and how incentive pressure changes the meaning of the number surprisingly fast.
Why velocity gaming is usually not malicious
Most teams do not sit down and plan to manipulate velocity. The problem is usually more ordinary than that. Once the number becomes socially important, behavior starts adapting to it whether anyone says so explicitly or not.
That is why velocity gaming is often accidental. The team is not necessarily being dishonest. It is responding to incentives, dashboards, expectations, and pressure in the most predictable way possible.
Gaming pattern
Teams do not need bad intent to bend the metric once the system starts rewarding the number.
Score pressure
As soon as velocity is watched like a score, the team starts feeling the need to protect the number as well as the work.
Behavior adapts
People respond to incentives by changing splitting, sizing, or delivery boundaries in ways that improve the chart faster than the system.
Gaming without malice
The behavior is often defensive rather than dishonest, which is exactly why it is so easy to normalize.
Metric meaning drifts
Once the score is under pressure, the number stops describing delivery reality as cleanly as people think it does.
Less incentive distortion
The healthier move is to reduce scoreboard pressure so velocity can shrink back into a local planning aid.
How the pressure usually shows up
Once velocity starts behaving like a visible success signal, subtle adaptations begin to look attractive. Larger estimates feel safer. Stories get sliced to flatter the trend. Commitment language grows more defensive. The number still looks official, but the meaning underneath it starts shifting.
That is what makes the problem hard to spot early. The system can still look orderly while the signal is already weakening.
What accidental gaming looks like in practice
The common signs are less about fraud and more about slow drift. The team begins shaping work and estimates around the metric instead of using the metric as one local planning aid among others.
- Comparable work starts getting bigger point values.
- Work gets sliced to improve the trend instead of improving clarity.
- Velocity starts being discussed like success instead of context.
- The number becomes more important than the delivery behavior behind it.
Why this matters so quickly
Once people optimize for the metric, the metric stops describing the system honestly. Velocity may still rise, but the delivery signal becomes harder to trust because the team is now partly performing for the number.
That is the real damage. The team loses a local planning signal and replaces it with a socially distorted one.
How to reduce the pressure
The best fix is usually changing the incentive environment instead of correcting people one estimate at a time. Keep velocity local. Stop using it as a scoreboard. Reconnect planning to clarity, capacity, and real delivery outcomes.
That lowers the pressure to perform for the metric instead of through the work itself.
TL;DR
- Velocity gaming is often accidental because teams adapt to incentives around the number.
- The drift usually shows up through larger estimates, flattering slicing, and more defensive commitment behavior.
- Once people optimize for velocity, the metric stops describing the system honestly.
- The best fix is changing the incentive environment and keeping velocity local.
- Velocity gaming usually starts as rational self-protection inside a system that is asking the metric to carry the wrong incentives.