Speed is not the point

A team ships faster this quarter than it ever has. More releases, shorter cycles, every chart pointing the right way. And somehow, talking to the people on it, the overwhelming feeling is not triumph but exhaustion — and a strange sense of being further behind than before. They are moving faster than ever and arriving nowhere in particular.

For a company with the word speed in its name, this is worth sitting with honestly. Most of what passes for speed in an operation is not progress. It is just faster noise.

Running to stand still

The sociologist Hartmut Rosa has spent his career describing this exact condition. Modern life, he argues, runs on dynamic stabilisation: a system that must keep accelerating simply to hold its own position. You do not speed up to get ahead; you speed up so as not to fall behind — and so does everyone else, so the whole field moves faster while the relative positions stay precisely where they were. It is the treadmill turned into a way of life. More email answered faster produces more email. More meetings scheduled more efficiently produce more meetings. The acceleration is real, and the arrival never comes.

Paul Virilio, who built an entire philosophy around speed, added the warning underneath it: every technology invents its own accident. "When you invent the ship, you invent the shipwreck." The faster a system moves, the more violent its failures and the less time anyone has to see them coming. An operation tuned only for velocity has quietly chosen its catastrophes; it simply hasn't met them yet.

So the team that "got faster" often did no such thing in any sense worth having. It raised its rate of motion and called that progress — the way a person running on the spot is, undeniably, running.

Make the system fast, not the person

Here is the distinction the whole thing turns on. There is a speed that comes from asking people to move faster — to work later, reply quicker, context-switch harder — and there is a speed that comes from removing the friction so the right things move on their own. The first is paid for in people, and the bill always comes due. The second is a property of the system, and it costs the people nothing.

The goal was never for anyone to run faster. It was to redesign the track so the right things move at all.

When an operation is genuinely fast — fast in the way that compounds rather than burns — it does not feel frantic. It feels calm. The work flows because the handoffs are clean, the decisions have owners, and the system does the carrying instead of the heroics. The people inside it are not sprinting; they are thinking, because the system has taken the sprinting off their plate. A truly fast operation is one where almost no one feels rushed.

This is the only sense in which speed is worth chasing, and it is the opposite of the one most companies pursue. Speed applied to people produces exhaustion and accidents. Speed designed into the system produces calm and direction. The first asks how do we go faster? The second asks the better question — why is this slow in the first place? — and then removes the reason, so the question never has to be put to a person again.

The point underneath the speed

Speed, on its own, is not a virtue. A faster way of doing the wrong thing is just a more efficient mistake. The acceleration is only worth anything when it is pointed — when the friction being removed sat between the work and the thing the work was actually for.

Which means the real work is almost never to go faster. It is to look hard at where the time actually goes, remove the friction no one ever decided to keep, and let the system carry the speed so the people don't have to. The fast operation is not the one that runs hardest. It is the one that had to run least.