Why “Average Pace” Can Be Misleading in Ironman
1. It’s backward-looking, not forward-planning.
Average pace tells you what you’ve already done, not what you should do next. Especially in the early stages of the bike or run, it can lure you into chasing numbers that feel “right” but don’t match the course, conditions, or your physiology.
2. It ignores terrain, wind, and conditions.
Your average pace will naturally fluctuate depending on the terrain – especially on hilly or windy courses. Trying to “hold pace” uphill or into a headwind can be costly. The best pacing adapts moment by moment, not based on a single number.
3. It fuels ego, not execution.
It’s tempting to anchor to an average pace target because it feels concrete (“I’m riding at 30km/h,” “I’m running at 5:15/km”), but this can shift your focus away from internal cues – like how your effort feels or how your nutrition is going – and into a performance tunnel that doesn’t always end well.
The Trap: Why Chasing Average Pace Can Undo Your Race
It often starts on the bike.
You’ve trained with a number in mind – say, 30km/h average – and now you’re out on course, feeling good, maybe even with a tailwind, and your average pace is climbing. Great, right?
But then comes a headwind, a climb, or a stretch of rough road, and suddenly that average dips. That’s the trap: instead of adjusting effort and accepting the change, you start chasing the number back. You push harder into the wind. You try to “win back” time on the downhills. You override your body’s signals because the number on your screen is slipping.
This costs energy – lots of it – and the price is paid on the run.
Then, when the run starts, the same trap shows up in different shoes. You glance down, see that you’re 10 seconds per kilometre off your target, and feel the urge to “fix it.” But the run is not a place to fix anything. It’s where you cash in wisely on the discipline and patience you showed on the bike.
Chasing average pace on the bike and run leads to burning matches you didn’t need to burn, and Ironman is a game of conservation, not correction.
Smarter Alternatives for Ironman Pacing
→ For the swim:
Use feel (RPE) and stroke rhythm. Conditions vary too much for pace to be reliable here.
→ For the bike:
Use power (if you have a meter) or heart rate + perceived effort. Focus on staying in a manageable zone, especially in the first half. Use average pace only as a rough secondary metric – don’t chase it.
→ For the run:
Heart rate, effort level, and a sustainable feel should guide you. If your average pace is dropping in the second half but your effort is steady and nutrition is in check, you’re doing it right.
The Ironman Pacing Mantra
“Start smart. Settle in. Stay patient. Save your best for the last 10K of the run.”
If an athlete really wants to use average pace, fine – but frame it as a result, not a goal. The best Ironman performances come from athletes who know how to pace from the inside-out, not just the watch-down.
Ready to race smarter?
If you’re heading into an Ironman soon, take some time to review your pacing strategy. Are you relying on numbers that serve your ego – or ones that serve your energy? Talk it through with your coach, trust the work you’ve done, and above all, race with patience.
The watch can show you pace, but only you can control your effort. Choose wisely.
Discover more from Triathlon Swim Squad
Subscribe to get the latest posts sent to your email.