The Runners Blueprint Blog

Put age and running pace in the same chart and runners do something funny. We immediately find our age group, check the number, and decide within about three seconds whether we’re feeling pretty good about ourselves or whether the data must be nonsense.

For Garmin users in this dataset, the average only moves from about 9:29 per mile in the 30s to 10:57 in the 70+ group. That’s roughly 5:54/km versus 6:48/km. The slowdown is real, but it’s probably smaller than a lot of people expect when they talk about getting older.

The dangerous part is turning an average into a target. These numbers mix different runners, different workouts, different terrain and different levels of fitness. Someone logging recovery miles is being compared with someone hammering every run. A trail runner and a flat-road runner can have completely different pace numbers without one being “fitter.”

Still, I understand why charts like this are irresistible. Running is full of uncertainty, and a number gives us somewhere to place ourselves. If you’re 58 and normally running 8:45 miles, you’re probably going to notice you’re faster than the average. If you’re running 11:30s, you might immediately start wondering whether you should be faster.

I think that second reaction is where people get into trouble. Age matters, but so do consistency, training history, body type, injuries, hills, heat and what kind of run you’re actually doing. Two runners can be the same age and live in completely different running worlds.

So forget the “good” or “bad” label for a second. How old are you, and what pace do most of your normal runs actually land around? I’m curious whether this chart feels surprisingly accurate for this group or completely disconnected from how people here really run.

One of the strangest things about Zone 2 is hearing runners argue over a single heart-rate number. Someone says 125 bpm is perfect. Someone else says 125 is barely a warm-up. Both of them could be right.

Using this simple 60–70% of max-heart-rate method, a runner with a max HR of 160 gets a Zone 2 of roughly 96–112 bpm. Give another runner a max of 200 and that becomes 120–140. Same training zone, completely different numbers on the watch.

That’s why copying somebody else’s Zone 2 makes almost no sense. Even worse is treating 130 bpm, 140 bpm or any other number as some universal ceiling every runner should stay under. The number has to come from something personal before it means much.

And even this chart is only one way of setting zones. Watches can use different methods, and the max heart rate stored in your watch may not even be your real max. If that starting number is wrong, you can follow the screen perfectly and still be training in the wrong place.

I like heart-rate training because it gives effort some structure, but I don’t want runners becoming prisoners of the green section on their watch. The better question is whether the number, your breathing and the actual effort are telling roughly the same story.

Find your max HR on the chart and compare it with your watch. Is your Zone 2 close to this 60–70% range, or does Garmin, Coros, Apple or whatever you use give you something completely different?

Runner confession time:

What gross thing do you do while running that you’d NEVER do in normal life?

Snot rocket?

Spitting?

Peeing behind a tree?

Wiping your nose on your shirt?

No clean answers. What’s yours?

Being slow doesn’t make the run less real. Some days the win is simply getting out there, grinding through it, and refusing to quit when the pace looks ugly.

You don’t need a fast number on your watch to be proud of yourself. Finish the run first. Judge it later. Who else needed this reminder today?

I think runners make two completely opposite mistakes with super shoes. One group acts like the shoes are basically doing the running for you. The other gets offended at the suggestion that the shoes might be helping at all.

The numbers make the argument more interesting. If a shoe really improved your marathon performance by 1%, that’s about 2 minutes for a 3:30 runner and nearly 3 minutes for someone running 5 hours. At 2%, now we’re talking about 4, 5 or even 6 minutes. That is not nothing.

But I also hate the idea of simply subtracting those minutes from somebody’s PB and calling that their “real” time. The shoes didn’t do the long runs. They didn’t get up early, hit the workouts, manage the bad days or hold pace when everything started hurting. And not every runner gets the same benefit from the same shoe anyway.

At the same time, I don’t think we should pretend footwear suddenly stopped mattering just because we worked hard for the result. If I race in a lighter, more efficient shoe and it helps me hold pace with a little less effort, I’m absolutely taking that advantage. That doesn’t make the training fake. It just means equipment is part of racing now.

The part I find funny is where runners draw the line. Good course? Fine. Pacers? Fine. Perfect weather? Fine. Carb load, caffeine, GPS watch, carbon shoes? Somewhere in there people suddenly decide the performance needs an asterisk.

So here’s the argument: you run a 3:59 marathon in carbon-plated shoes and finally break four hours. If somebody tells you the shoes were probably worth a few minutes, are you saying **“fair enough”**… or **“3:59 is 3:59 — the PB is mine”**?

What’s more impressive:
A sub-3 marathon at 30—
or still racing 5Ks at 70?

Tempo runs have a funny way of turning into races against ourselves. You start at the pace you planned, feel good after five minutes, speed up a little, then spend the last ten minutes hanging on because slowing down suddenly feels like failure.

That’s not really the point of the workout. A continuous tempo should feel comfortably hard for those 20–30 minutes. You’re working. You’re concentrating. You definitely know you’re not on an easy run. But you shouldn’t be counting lamp posts and begging for the finish by halfway.

I think this is where ego gets involved. A 25-minute 5K runner sees 5:15–5:25/km on the chart and thinks, “I can run faster than that.” Of course you can. The question isn’t whether you *can* run faster. The question is whether running faster still gives you the workout you came for.

Tempo pace also gets confused with time-trial pace far too often. If every tempo becomes a chance to prove your fitness, you’ve changed the session. Harder isn’t automatically better. Sometimes the discipline is finishing the run knowing you had another gear and deliberately didn’t use it.

The simplest check for me is the final few minutes. You should be glad it’s nearly over, but you shouldn’t be falling apart. If your form is going, your pace is fading and the last five minutes become survival, there’s a decent chance you turned “comfortably hard” into just plain hard.

Look at your 5K time on the chart. Is that actually close to the tempo pace you normally run, or have you been quietly racing your tempo days?

These numbers are going to annoy a few men. In this Berlin Marathon data, men were more likely than women to hit a serious second-half slowdown in every single finish-time group, and the overall difference wasn’t exactly tiny: 17.63% for men versus 9.66% for women.

Before this turns into “men are worse marathoners,” that isn’t what the data proves. The chart tells us what happened, not why it happened. Pacing, physiology, experience, fueling, race-day decision making and simple overconfidence could all be part of the story.

What caught my attention is how the pattern changes with finish time. Among sub-3 runners, the wall was relatively rare for both groups: 1.42% of men and just 0.23% of women. At 4:30+, it jumps to 41.62% for men and 17.66% for women. So whatever is happening here, it isn’t just a fast-runner problem or a slow-runner problem.

And “hitting the wall” here doesn’t simply mean feeling horrible at mile 22. It means the second half was at least 20% slower than the first. That usually tells a much bigger story about what happened earlier in the race, because marathons have a nasty habit of letting bad decisions feel perfectly fine for the first two hours.

The part I’d love to know is how much of the male/female gap comes from physiology and how much comes from behavior. Do men go out closer to what they *hope* they can run while women pace closer to what they actually trained for? Or is that explanation far too convenient?

If you’ve run enough marathons to have both nailed one and completely blown one, what actually caused your worst fade? Bad pacing, bad fueling, weather, fitness… or plain old ego?

I still think runners have gotten a bit weird about the 30-minute 5K. Somebody says they finally broke 30 and within five minutes another runner is there telling them that's basically their recovery pace 😂 Okay. And?

If you've been running 22 minutes forever, 30 probably does look slow. If you've been stuck at 31:20 for six months, 29:59 is gonna feel like winning something, and that's the part people forget when they compare everybody from their own starting point.

So tell me something better than your current PB. What was the first 5K time you were genuinely proud of? The one where you looked at the watch and thought yep... finally.

If sub-30 is that number for you right now, this is the training I'd use to get there without turning every run into a 5K test:

https://www.runnersblueprint.com/run-a-5k-in-30-minutes/

One of the easiest ways to ruin a good hard workout is to get greedy the next day. Tuesday’s intervals go well, you wake up Wednesday feeling decent, and suddenly the “easy run” turns into another solid effort because your legs seem fine and slowing down feels like wasted training.

The problem is your legs don’t have to feel destroyed for recovery to matter. A hard session creates the stimulus, but the improvement comes afterward, when your body actually gets the chance to absorb what you just did. Keep piling stress on top of stress and eventually you’re not training harder anymore — you’re just carrying fatigue from one run into the next.

This is why easy days can mess with a runner’s head. You finish them feeling like you could have done more, while a hard session gives you that satisfying feeling that you really trained. But the runner who can leave something in the tank on Wednesday usually has a much better Thursday or Friday than the runner who needed every day to feel productive.

And yes, there are times when back-to-back hard days are planned on purpose. Experienced runners might use them in specific training blocks, and certain race demands can justify them. That’s very different from turning two ordinary days into hard days because the pace felt good and your watch encouraged you.

The simple hard → easy → hard pattern isn’t exciting, but that’s kind of the point. Make the hard days hard enough to create a reason to recover, then make the easy days easy enough that you can actually attack the next quality session instead of surviving it on tired legs.

I think this is where a lot of runners quietly sabotage themselves, especially when fitness starts improving. Which are you worse at: making the hard day hard enough, or actually having the discipline to keep the next day easy?