I Hate to Sprint

I have a complicated relationship with running. The Army deserves most of the blame for that, having used it as both training and punishment, sometimes simultaneously, and the association stuck. What I hate even more than running is sprinting. It is not sustainable, it is uncomfortable in a way that does not build anything useful, and it exhausts resources that take time to recover. What I have always preferred is rucking. Give me a heavy pack and a long way to go, and I can fix my eyes on the horizon and put left foot in front of right for about as long as anyone needs me to. I once walked from Midtown Atlanta to Stone Mountain and back just to see whether I could. I could. The key was never going faster than I could sustain.

I take the same approach to work, and I have come to believe that the organizations that actually perform over time take it too, whether they frame it that way or not.

The sprint is a seductive idea. A team is underperforming, the numbers are off, something needs to change, and the most visible response available is intensity. Everyone rallies, the urgency is real, and for a few weeks the effort is genuine and the results show it. Then the sprint ends. The intensity fades. The numbers drift back. And three months later, someone calls another sprint, and the people who have been through this before feel something quietly shift in how seriously they take it.

The problem is structural rather than motivational. Sprints consume future capacity. The energy spent in a burst comes from somewhere, and what it comes from is the weeks on either side of it. The recovery period is real even when nobody names it that way. Teams that are repeatedly asked to operate in emergency mode eventually develop a kind of organizational callus around urgency. They perform it without being moved by it, because experience has taught them that the emergency will pass and be replaced by another one, and that none of it will have fundamentally changed how the work gets done.

What changes how the work gets done is a system that runs every week without drama. A pace, not a push. Review the numbers. Address the blockers. Fulfill the commitments. Begin again. It is not glamorous, and it does not produce the kind of visible, concentrated effort that gets noticed in the moment. What it produces is results that compound, steadily, over a long enough horizon that they start to look like something other than what they actually are. They look like talent, or market timing, or luck. Usually they are just consistency, applied without interruption.

Rucking taught me that the goal is to still be moving when other people have stopped. The organizations that understand this tend to build things that last. The ones that keep scheduling sprints tend to arrive at the finish line already tired, wondering why the distance felt longer than it looked.