Beyond Comfort Zones: Why Endurance Challenges Change How We Solve Problems
Endurance events are often described in physical terms. In reality, they reshape how we approach difficulty, uncertainty, and persistence — lessons that extend far beyond sport.
Introduction
There is a moment in any long endurance effort — several hours in, with many more ahead — when the question stops being about the distance and becomes about something else entirely. Why am I here? What does it mean to continue? What does finishing actually prove? These are not dramatic questions. They surface quietly, in the space between steps, when the crowd is gone and there is no external signal telling you what to do next. I have found, over years of endurance training and racing, that sitting with those questions — rather than suppressing them — produces a different quality of thinking. This article is an attempt to describe what that is, and why it seems to carry over.
The Myth of Pure Physical Strength
The assumption most people make when they encounter ultramarathon running for the first time is that finishing one is primarily a physical achievement — that the people who complete 160 or 250 kilometres through mountains are simply built differently, or have been training harder than ordinary people can sustain. This is partially true and mostly misleading.
Training matters enormously. There is no shortcut to the physiological base required to cover those distances without serious injury. But physical capability is not the limiting factor for most participants at the distances involved. The people who do not finish — and at extreme distances, a meaningful proportion of starters do not — are, in most cases, mentally prepared to complete the race. The commitment required to enter and train for an event of this scale means that those who reach the start line have already crossed a significant psychological threshold. What stops them is more often physical: an injury that worsens with each kilometre, an accumulation of exhaustion so deep that the body cannot recover sufficiently overnight to continue the next stage, or a cascade of physical breakdowns — blisters, muscle damage, heat stress — that collectively push past what the body can sustain. These are not failures of will. They are encounters with hard physiological limits.
What completion actually requires is different from what it appears to require from the outside. It is the management of energy over time, the monitoring and response to discomfort signals, the maintenance of decision-making quality across extended fatigue, and the sustaining of motivation when the event is no longer interesting — when it is simply very hard and very long with no end in sight. These are less athletic capabilities than cognitive ones, and they are as trainable as cardiovascular fitness, though the training looks quite different.
Complex professional work requires the same distinction. Starting a difficult project is not the same as sustaining it well over two years. The intelligence required to conceive a good architecture is not the same as the discipline required to make consistent good decisions when the project is tedious, the organisation’s attention has moved elsewhere, and the original team has partly dispersed. Both matter. They develop through different means.
Learning to Manage Energy Instead of Speed
There is a specific transition that most endurance athletes go through at some point, usually after a race that ended badly. The instinct, before that transition, is to optimise for pace: to go as fast as sustainable, to push on climbs, to take advantage of feeling good in the early miles. The feedback loop that corrects this instinct is usually painful.
Experienced endurance athletes learn to manage effort instead of speed. This sounds like a small semantic shift. In practice, it changes how you train, how you race, and how you interpret your body’s signals during an event. Heart rate zones, perceived exertion, the deliberate cultivation of the ability to run at a pace that feels too slow — these are all tools for maintaining a sustainable output rather than maximising a momentary one. The discipline is not in going faster. It is in resisting the urge to go faster than the event will allow you to sustain.
The parallel in engineering and leadership work is structural rather than metaphorical. Teams that move as fast as possible in the first year of a complex programme often create technical and organisational debt that slows the second and third years significantly. Features shipped quickly without adequate architecture cost more to maintain and adapt than features shipped carefully. People pushed beyond sustainable output for extended periods develop the kind of chronic low-level dysfunction — reduced judgment, lower collaboration quality, higher attrition — that is difficult to see in real time but very visible in retrospect.
The teams and systems that deliver well over years tend not to be the ones that moved fastest in month one. They tend to be the ones that found a pace they could sustain, and sustained it.
Discomfort as Information
Early in endurance sport, discomfort is something you push through. The novelty of the distance is discomfort enough to manage; you learn to treat the background ache as noise rather than signal. This is useful up to a point, but it is an incomplete strategy.
With more experience, the relationship with discomfort changes. Pain on the outside of the knee on a descent has a different character than muscular fatigue in the quadriceps, and both are different from the hollow, slightly nauseated sensation of running low on glycogen. Each signals something specific. The response to each is different — one might warrant slowing down and adjusting gait, another might warrant eating, another might warrant stopping. Athletes who treat all discomfort identically — either ignoring all of it or responding to all of it with alarm — make worse decisions than those who have learned to read the signal and respond proportionately.
This is a trainable skill, though training it requires deliberate attention that is counterintuitive when you are tired and uncomfortable. The question to ask is not “how do I make this stop?” but “what is this telling me?”
The translation to professional contexts is direct. Friction in a system design — the places where things do not fit together cleanly, where integration requires more than expected, where a design review keeps returning to the same concern — is a signal that something has not been resolved. The instinct to push through it, to ship and address it later, is understandable. It is also how systems accumulate the kinds of structural debt that become very expensive to pay down. A team that consistently finds a particular kind of work difficult — coordination across certain boundaries, testing certain categories of functionality, onboarding engineers to certain parts of the codebase — is revealing something about its structure or its technical design. Curiosity is a better response than suppression.
Thinking in Stages Instead of Endpoints
Multi-stage races — events covering 200 or 250 kilometres across five or six consecutive days — make it physically and cognitively impossible to hold the full distance in mind as the operative objective. Thinking about the complete event while running day three is not a useful cognitive strategy. The distance remaining is too large, the variables are too many, and the information available about days four, five, and six is insufficient to plan against them usefully.
The viable approach is stage-by-stage. Each day is its own problem: this terrain, these conditions, this weather, this state of the body. What worked yesterday may not apply today — a pacing strategy that was comfortable on the flat sections of stage two becomes untenable on the climb-heavy profile of stage three. The goal each day is not to win. The goal is to finish well enough to start the next stage in a state from which finishing that stage is possible. The frame is explicitly short-term in service of the long-term.
This cognitive approach turns out to be useful for long-running technical and organisational initiatives. A multi-year platform transformation is not a project in the conventional sense — it is a sequence of decisions, deliveries, and organisational changes, each of which has its own conditions and each of which creates the context for what follows. Trying to plan the full transformation in detail at the start encodes assumptions about year two and year three conditions that will not hold. Thinking in stages — what does the next meaningful increment look like, what does completing it enable, what should we learn from it — preserves optionality and reduces the paralysis that comes from the overwhelming complexity of the whole.
The discipline is in maintaining awareness of the longer arc while operating stage by stage. Neither end alone is sufficient: stage-by-stage thinking without directional orientation becomes reactive; long-arc thinking without operational grounding becomes abstract. Holding both is the harder skill, and it is one that multi-stage racing teaches in an unusually visceral way.
The Quiet Value of Persistence
The observation that persistence is valuable is too general to be useful on its own. Most people would agree with it in the abstract, and most people also struggle to sustain effort through the specific kinds of difficulty that persistence actually requires.
The more specific claim, and the one that endurance experience seems to clarify, is this: certain kinds of important problems are not solvable through insight alone, regardless of how capable the person attempting them is. They require sustained engagement over time — returning to the problem repeatedly, after setbacks, after the initial interest has faded, after the people around you have moved on to different concerns. The willingness to do that, without the external reward of novelty or progress that is visible to others, is not a personality trait that people either have or do not. It is a developed capability, and it develops through practice.
The physical correlate is clear. The training adaptations that matter most in endurance sport are not produced by exceptional workouts. They are produced by consistent moderate effort, accumulated over months. The body adapts slowly, cumulatively, and reliably. A single brilliant training session produces almost nothing lasting. A hundred unremarkable ones, performed consistently over six months, produce substantial physiological change. The mechanism is repetition and time, not intensity.
Professional and organisational capability tends to build the same way. A team that consistently revisits its architecture decisions as conditions change will make better decisions over time than one that makes one large architectural bet and defends it. An engineer who returns to the hard problems — the ones that resist quick resolution, the ones that are not satisfying to work on — tends to develop deeper expertise than one who always gravitates toward new work. The compounding is quiet and slow, and therefore easy to underestimate.
Closing Reflection
The book Beyond Comfort Zone is an attempt to articulate what happens when you commit to hard things voluntarily and repeatedly — what changes in you through that commitment, and how those changes manifest in the way you approach work and the way you think about difficulty. The endurance experiences described in this article sit at the centre of that project.
The point is not that everyone should run ultramarathons, or that athletic achievement is a useful measure of anything beyond itself. The point is more modest and, I think, more durable: voluntary difficulty, engaged with honestly rather than romanticised, produces a different quality of thinking about difficulty in general. The person who has spent many hours somewhere very uncomfortable, making decisions when they would rather stop, tends to approach the next difficult thing with a different character of patience than they had before. Not because suffering is inherently instructive — it is not — but because the practice of continuing deliberately, without certainty, without a clear signal that continuing is the right decision, is itself a form of training.
That mindset — patient, grounded, willing to proceed in the absence of confirmation — turns out to be useful in most worthwhile endeavours. It is the thing I keep returning to, both in races and in everything else.