On the 18th of April 2026, I was convinced my running career was over.

Seven years and roughly fourteen thousand kilometres, and it all came to a halt during a warm-up jog. Just five minutes into a 25 km run, my leg suddenly felt like it might detach itself and pursue a quieter life.

The thought that hit me was simple and uncomfortable: what if I've broken something I can't fix?

Looking back, that reaction was a bit dramatic. But if you've ever been injured doing something that has quietly become part of your identity, you'll understand how quickly your mind runs ahead of reality. One strange sensation and suddenly you are imagining life without the thing that has been keeping you grounded.

This post is not really about that moment.

It's about what I realised because of it. The uncomfortable part is that this wasn't random. I didn't just wake up unlucky one morning. I built that injury over time, one decision at a time, without noticing where things started to drift.

How I Got Here (A Short Running History)

I started running in July 2018. At first, it was just something to do, a way to stay active and clear my head after spending too much time behind a screen.

Somewhere along the way, it became something else.

Running turned into a mix of therapy, structure, and quiet discipline. It also came with a bit of ego. There is something addictive about watching your pace improve and your distances stretch out. You start doing mental calculations mid-run, convincing yourself that if you can hold this pace for a few more kilometres, you are not too far off from something impressive. You are usually wrong, but that does not stop the thought.

Over time, I settled into a rhythm:

• running six days a week
• covering between 10 and 14 km per day
• operating in a pace range of about 4:00/km to 4:45/km

For the most part, it worked.

I had one notable injury in September 2022. Classic runner's knee. At the time, I was running in what can only be described as tennis shoes with very little cushioning. Every step felt like a direct conversation with the pavement, and the pavement was not particularly sympathetic.

I couldn't run for about three weeks. Eventually, I made a few changes:

• switched to proper running shoes with more cushioning
• increased my cadence (we'll define that properly later)
• added some strength work

The knee pain disappeared. Like most people who recover from an injury, I assumed I had solved the problem. What I actually did was solve one part of it and quietly ignore the rest.

Road to Disaster

By April 2026, running had become routine. I was averaging around 50 km per week, and it felt manageable.

That's usually when people get into trouble.

I decided to increase my workload to around 65 km per week. On its own, that probably would have been fine. The issue is that the mileage increase didn't happen in isolation.

At the same time:

• I had just come back from a week-long break
• I resumed running at a fairly aggressive pace immediately
• and I introduced hill repeats for the first time

The hill I chose is known as the "Hill of Death", which should have been enough of a warning on its own. Instead, I attacked it enthusiastically, doing multiple repeats and then running about 4 km back home afterwards.

The session felt great. That was part of the problem.

Feeling good after a workout does not mean your body has adapted to it. It usually just means the consequences have not shown up yet.

A few days later, I did another hillier run. My legs felt heavier than usual, but I treated it as normal fatigue and carried on with my routine.

At that point, everything still looked fine on paper. The mileage was reasonable, the paces were consistent, and there were no obvious signs of trouble.

Underneath that, however, I had started stacking multiple stresses at once without giving my body much room to adjust.

The Turning Point

On the 18th of April, I set out for a 25 km run. There was nothing unusual about the plan. It was a distance I had handled before, and based on how the previous days had gone, I expected it to be just another long run.

The first few minutes felt normal, exactly the kind of uneventful start you hope for when you know you have a long distance ahead of you. Then something shifted. It wasn't a sharp pain or anything dramatic, just a strange stiffness around my hamstring, close to the knee. The kind of sensation that doesn't immediately stop you, but quietly raises a question in the back of your mind.

I kept going for a bit, expecting it to loosen up as I settled into the run. That usually happens with minor tightness. This time, it didn't. With each step, the feeling became more noticeable, like the muscle was under tension in a way it shouldn't be. At one point, it genuinely felt as if pushing a little harder might cause something to give.

That was enough.

I stopped and stood there for a moment, trying to decide whether this was one of those things that would pass or something I needed to take seriously. Deep down, I already knew the answer. This didn't feel like normal stiffness, and pretending otherwise wasn't going to change that.

So I turned around and walked back.

The Mental Battle

Physically, the decision was straightforward. Something wasn't right, so I stopped. Mentally, it was far less clean.

The first reaction was frustration. I had planned that run and committed to it, and stopping five minutes in felt like I had failed, even though I knew it was the sensible choice. That disconnect between logic and emotion is one of the more irritating parts of being injured.

Not long after that, doubt started to creep in. I found myself wondering what exactly I had done. Was this a minor strain that would settle in a few days, or had I crossed into something that would take weeks to recover from? Without a clear answer, the mind fills in the gaps, usually with the least helpful possibilities.

That's when the replay begins. You start going back over recent runs, looking for the moment where things might have gone wrong. The hill sessions, the heavier legs, the decision to keep pushing through fatigue all begin to stand out more clearly in hindsight. Individually, none of them seemed like a problem at the time. Together, they started to form a pattern.

There was also a more uncomfortable realisation sitting underneath all of that. Running had become a core part of my routine. It gave structure to my days, helped clear my head, and provided a steady sense of progress. The idea that it might be taken away, even temporarily, was difficult to sit with.

At that point, the familiar temptation showed up. The thought that maybe it wasn't that bad, that maybe I could just ease into a run and see how it felt, that maybe I was overreacting. I've followed that line of thinking before, and it has never ended well.

This time, I didn't push through it. Not because I suddenly became disciplined, but because experience had already shown me where that approach leads. Ignoring warning signs doesn't make them disappear. It simply delays the consequences and usually makes them worse.

So I stopped running, not out of choice, but out of necessity.

What Actually Went Wrong

Looking back, the injury wasn't caused by one bad run or one poor decision. It was the result of several small changes that, on their own, didn't seem particularly risky, but together created more stress than my body was ready to handle.

The most important thing I missed is that the body doesn't just respond to mileage. It responds to the total load placed on it, and that load comes from a combination of distance, pace, terrain, and recovery. I increased my weekly distance, but I also returned from a break at a fairly aggressive pace and introduced hill repeats at the same time. Each of those changes added a new layer of stress.

The hills, in particular, deserve attention. Running uphill places a much higher demand on the posterior chain, especially the glutes and hamstrings. It's a different kind of effort compared to flat running, even if the total distance doesn't change. When I added hill repeats, I effectively introduced a new training stimulus without adjusting anything else around it.

There's also the question of intensity. Most of my runs sat in a fairly narrow pace range. They weren't all-out efforts, but they weren't truly easy either. That meant my body was constantly working at a moderate level without getting enough low-intensity running to properly recover.

Another factor that played a role is something runners talk about often but don't always define clearly: cadence.

Cadence is simply the number of steps you take per minute while running. A higher cadence usually means shorter, quicker steps, while a lower cadence often comes with longer strides and more impact on each landing. One way to think about it is like typing. You can either hit the keyboard with slow, heavy keystrokes or use lighter, quicker taps. The total output might be the same, but the strain on your fingers is very different.

In my case, my cadence had dropped slightly, which likely meant I was overstriding more than usual. That increases the load on the legs with each step, especially when combined with higher mileage and hill work.

Put all of that together, and the picture becomes clearer. I didn't just increase distance. I increased distance, kept the pace relatively high, added hills, and reduced the amount of true recovery. The injury was simply the point where my body stopped absorbing that load and started reacting to it.

What I Got Wrong

Understanding what happened is one thing. Accepting my role in it is another.

The first mistake I made was assuming that mileage was the main variable that mattered. I focused on the jump from 50 km to 65 km per week, but ignored the fact that I had also changed the type of stress I was applying. Introducing hills while maintaining the same pace and frequency made the workload very different, even if the numbers looked reasonable.

I also ignored early warning signs. The heavy legs after the hill sessions were not just a sign of a good workout. They were a signal that my body was under more strain than usual. Instead of adjusting, I treated that feeling as something to push through.

Another mistake was the way I approached pace. I had convinced myself that anything slower than about 4:45/km wasn't worth doing. That belief removed an important tool from my training: genuinely easy runs. Without those easier days, there was no real separation between effort and recovery. Everything blended into a steady, moderate grind.

Then there's strength training. I had been doing squats and other exercises consistently at one point, and they helped. Over time, I let that slip. It didn't feel urgent, and running was already taking up most of my time. The problem is that running alone doesn't strengthen everything equally.

If your glutes are weak, you're not using your bum properly when you run. And the bum is supposed to do a significant portion of the work. When it doesn't, other muscles have to compensate, usually the hamstrings and quads. Over time, that imbalance increases the risk of injury, especially when you add more load through distance and hills.

Finally, I underestimated the impact of returning from a break. Even though I felt strong, my body had lost some of its recent conditioning. Jumping straight back into longer runs at a fast pace created a gap between what I felt capable of and what my body was ready to handle.

Taken individually, none of these mistakes seemed significant. Together, they created the conditions for an injury that, in hindsight, was entirely predictable.

What I'll Do Differently

The injury forced me to take a step back and look at how I train, not just how far or how fast I run, but how I manage the overall load on my body.

The first change is how I introduce new stress. If I add something like hill repeats, something else has to give. That could mean reducing mileage slightly, slowing down the pace on other runs, or simply allowing more recovery time between harder sessions. The idea is simple: don't stack new challenges on top of an already full plate.

I also need to redefine what an easy run looks like. Up to now, most of my runs have lived in a narrow band of effort. They weren't all-out, but they weren't easy either. Going forward, some runs will have to feel slower than I'd like. Not because they are pointless, but because they serve a different purpose. Easy runs are where recovery happens, even if they don't feel impressive in the moment.

Cadence is another area I'll pay more attention to, not by chasing a specific number, but by focusing on shorter, quicker steps and avoiding the habit of overstriding. It's a small adjustment that can reduce the load on the legs over thousands of steps.

Strength training is going back into the routine, and this time it stays there. Running doesn't take care of everything. The glutes, or more plainly, the bum, need to be doing their share of the work. If they're not, something else will, and that something else usually complains sooner or later. A couple of focused sessions each week is a small investment compared to the cost of being sidelined.

Finally, I need to respect the signals my body sends. Heavy legs, unusual stiffness, or a persistent sense of fatigue are not just background noise. They are information. Ignoring them doesn't make me tougher, it just delays the moment where I'm forced to listen.

Final Thought

I didn't get injured because of one bad decision.

I got injured because I made a series of reasonable decisions without considering how they combined.

That's the part that's easy to miss. Most training mistakes don't look like mistakes at the time. They look like progress. A bit more distance, a bit more intensity, a new type of workout to push things forward.

The problem is not any one of those things on its own. The problem is how easily they stack.

The body is usually patient. It absorbs a lot before it reacts. But it does keep score, and eventually it asks for that balance back.