The Velocity Trap
The pattern in which an organisation responds to disappointing results by moving faster and doing more, only to make progress slower.
IN ONE LINE
When the system is already overloaded, pushing it harder can make it deliver less.
Three minutes.
What it is
When results are disappointing, speeding up feels like the obvious response. Move faster, add resource, launch the initiative, shorten the deadline, increase the cadence or put more pressure behind delivery.
There is nothing inherently wrong with that response. In a system with spare capacity and clear priorities, increasing effort can increase output.
The Velocity Trap appears when those conditions don’t exist.
The organisation is already carrying too much. People are switching between competing priorities, senior attention is fragmented and work is arriving faster than it can be absorbed. Adding more doesn’t simply increase the workload. Every additional initiative competes for the same attention, people and capacity as everything already underway. Direction changes create rework, new priorities interrupt old ones, and decisions made quickly are more likely to be revisited later.
The result is an organisation that can be extremely active without becoming correspondingly productive.
Activity starts masquerading as progress.
That is what makes the Velocity Trap difficult to see. From the outside, and often from the inside too, things appear to be moving. Meetings multiply, initiatives launch, milestones are announced and teams are visibly busy.
There is plenty of evidence of motion, but much less evidence of arrival.
What creates it
Pressure for results. When performance is behind expectation, increasing pace is a rational response. The problem comes when nobody checks whether the system has the capacity to absorb the acceleration.
Too much happening simultaneously. New work is added before existing work has finished, increasing competition for the same finite resources.
Changing direction. What feels like a relatively small adjustment at the top can land as substantial reprioritisation and rework further down.
No permission to pause. Slowing down long enough to clarify, finish or sequence work can look like a lack of urgency precisely when pressure is highest.
Visible activity. Starting things is easy to see. The interference between them is much harder to see, so organisations can end up rewarding the behaviour that is creating the problem.
How to recognise it
Everybody is working at capacity and more work keeps arriving. There is no meaningful flex left in the system, so new demands can only be absorbed by interrupting something already underway.
The top priorities keep changing. Ask people to name the three most important things and either the answers differ or they have changed since the last time you asked.
Direction changes create disproportionate amounts of rework. A decision that appears small from above forces teams below to revisit work they have already started or completed.
People are frustrated by conversations about prioritisation. The pressure to move makes any discussion about capacity feel like resistance to progress.
There is plenty of starting and surprisingly little finishing. New initiatives appear faster than old ones disappear, so the amount of work in motion keeps growing.
Goodwill is being used as capacity. People absorb the gaps through longer hours, extra effort and repeated recovery work. That can work for a while, which is one reason the underlying capacity problem remains hidden.
Every unexpected event becomes a major disruption. There is so little spare capacity that nothing new can happen without something else suffering.
No slack can look like efficiency. Right up until you need it.
What it gets mistaken for
Most often, urgency. The organisation believes it is responding decisively to a difficult situation, and leaders increase pace because the results matter and waiting feels irresponsible.
It can also look like ambition. A business with aggressive timelines, multiple initiatives and constant activity appears energetic, and sometimes it is. The distinction is whether the additional pace is producing additional progress.
If increasing effort repeatedly produces more rework, more unfinished work, more switching and less capacity to respond, the organisation does not have a motivation problem. It has exceeded the speed its current system can sustain.
This is why telling people to slow down is rarely useful. The objective isn’t slowness.
The objective is progress.
Why it persists
Because slowing down is visible and the cost of continuing usually isn’t.
A delayed launch can be challenged. A decision to pause can require explanation. A leader who suggests doing less may have to defend that choice, particularly when results are already under pressure.
The cost of continuing is much harder to point at because it is distributed across hundreds of small interruptions, changing priorities, repeated conversations, unfinished work and hours spent getting back up to speed. No single event looks particularly serious, but together they consume an enormous amount of the organisation’s capacity.
Meanwhile, all that activity provides reassurance. People are working hard, new initiatives are underway and something is visibly happening. So when results remain disappointing, the organisation can reach the same conclusion again: we need to move faster.
That is how the trap tightens.
What becomes possible
The alternative to the Velocity Trap isn’t a slower organisation. It is an organisation capable of moving faster because less is getting in the way.
When work is sequenced rather than piled on simultaneously, attention concentrates and teams finish more of what they start. Direction changes become choices with visible consequences rather than additional instructions that the system is somehow expected to absorb.
Spare capacity also creates resilience. An unexpected problem can be handled without destabilising everything around it, and people have enough room to fix problems rather than continually working around them.
Most importantly, effort begins producing a better return.
The prize isn’t doing less for the sake of doing less.
It’s getting more of what matters finished.
Where to start
Don’t start by asking people to slow down. Start by looking at everything the organisation is already trying to move.
Put the significant work currently underway in one place, then ask:
ASK THIS
What are we trying to accelerate simultaneously?
Look for the interference between those things. Which pieces of work compete for the same people? Which require the same senior decisions? Which repeatedly interrupt one another? Which could finish significantly faster if something else stopped competing with them?
The question isn’t whether every piece of work matters. Most of it probably does.
The question is whether doing all of it at the same time is actually making any of it happen faster.
Speed is useful. Simultaneity is expensive.
Last updated October 2026
