There is a moment somewhere past the three-hundred-kilometre mark of an ultra where you stop thinking about the finish. The distance is too large to hold in your head, so your world shrinks to the next feed stop, the next climb, the next handoff with your support crew.
That shrinking is not a failure of concentration. It is the correct strategy. And it is the same strategy that makes long, complicated operational work actually finish.
The middle is where things break
When I mapped the Procure-to-Pay cycle during my internship at Godrej & Boyce, I expected the delays to sit in the obvious places — the negotiation, the approval, the supplier's lead time. They mostly did not.
The delays sat in the gaps. A specification finished on a Tuesday and picked up on a Friday. A query raised to a supplier that nobody was formally waiting on. Each individual gap was defensible. Added together, they were most of the cycle time.
An ultra is identical. Nobody loses a 646-kilometre race because they were slow on the bike. They lose it in the eleven minutes at each stop that should have been four, repeated fourteen times.
Plan the handoffs, not the effort
The instinct, in both cases, is to optimise the hard part — ride faster, negotiate harder. It feels like the serious thing to do.
But the hard part is usually already near its limit. The handoff is not. A support crew that knows exactly which bottle, which food, and which layer goes where before you arrive turns a stop from four minutes into ninety seconds without you pedalling any harder. A procurement process where the next owner knows a document is coming does the same thing.
This is unglamorous work. It produces no story worth telling at the finish line. It is also, reliably, where the time is.
Fatigue is a design constraint
The last thing an ultra teaches — and the one that transfers most directly — is that you should design a process for the version of yourself that is tired.
At hour twenty-two, I cannot be trusted to make a good judgement call about nutrition. So the call gets made at hour zero, written down, and executed by someone else. The plan is not there because the plan is smarter than me. It is there because it was made by a rested me.
Operations run on the same principle. A process that only works when everyone is attentive, unhurried and fully staffed is not a process. It is a hope. The good ones assume the people running them are stretched, and still hold.
I write occasionally about supply chain, operations, and what endurance sport teaches about both. If something here is useful — or wrong — I'd genuinely like to hear it.