Training Paces
The honest answer is that both are tools, both lie sometimes, and the runners who do best use them to inform effort rather than replace it.
The short answer
Use effort as the primary guide, pace for quality sessions on flat, measurable ground, and heart rate for easy running and long runs where the risk is going too hard. Pace is the better tool for structured sessions because it responds instantly. Heart rate is the better tool for controlling easy days and for spotting fatigue. Neither should override how you actually feel.
What each one is good at
Pace
Pace is objective, immediate, and directly connected to the outcome you care about — racing is a pace event, not a heart rate event. When you run a threshold rep, pace tells you straight away whether you are on it.
Pace also gives you a clean training record. You can compare 5 x 1km on the same loop in January and April and know something real has changed.
Where pace fails: hills, wind, heat, trails, altitude, and any day where your legs are not the legs you had last week. In Wellington, that is a lot of days.
Heart rate
Heart rate reflects internal cost rather than external output. That makes it excellent on hills and in the wind, where pace becomes meaningless. It also picks up things pace cannot — dehydration, heat, illness coming on, accumulated fatigue.
Where heart rate fails: it lags by a minute or two at the start of hard efforts, which makes it close to useless for short intervals. It drifts upward over long runs even at constant effort. It is affected by caffeine, sleep, stress, temperature and how much you have eaten. And optical wrist sensors, in particular, produce genuine nonsense often enough that you should never trust a single reading.
Effort
Rate of perceived exertion — the 1 to 10 scale — is the one everybody underrates and the only one that is never wrong about how hard you are working. It requires no battery and it accounts for every variable automatically.
Its weakness is that it takes time to calibrate. Newer runners routinely rate a 4 as a 7 and vice versa. That calibration is a skill, and it is worth building deliberately.
How I actually use them
Every athlete I coach gets paces and an RPE reference card. Heart rate is available in the data and I look at it, but it is rarely the instruction.
In practice:
- Easy runs: effort first, heart rate as a ceiling. If you are above about 75 percent of max on an easy day, you are not running easy, whatever the pace says. More on that in What pace should I run my easy runs?
- Long runs: effort and heart rate. Expect drift of 5 to 10 beats over a long run at constant effort — that is normal, not a signal to slow further.
- Threshold and intervals: pace and effort. Heart rate is too slow to be useful inside a rep, though it is informative afterwards.
- Hills and trails: effort, always. Pace is nonsense on a climb and heart rate lags on rolling ground.
- Racing: pace, checked against effort. Never race to a heart rate number.
Coach's note
Wellington settles this argument in about a week. Run the same threshold session on the waterfront on a still morning and then into a northerly on Cobham Drive, and you will produce two pace files that suggest you lost a month of fitness. You did not. The wind here means I will always take an athlete's effort and heart rate over their pace when the two disagree — and I will always take how they say the session felt over all three. If you are going to train by pace alone, choose your ground: Newtown Park, the Petone Esplanade, the Hutt River Trail. Everywhere else, run the effort, or use my Wind Pace Calculator to adjust your target pace for the wind.
Setting heart rate zones without a lab
Skip the age-based formulas. "220 minus your age" is a population average with an error range wide enough to make it worse than useless for an individual — plenty of 45-year-olds have a max above 190 and plenty of 25-year-olds do not.
Better options, in order:
- Lactate threshold heart rate. Run a 30-minute hard time trial. Your average heart rate for the final 20 minutes is close to your threshold heart rate. Build zones off that percentage rather than off max.
- Observed max. The highest reliable number you have seen in the last year, usually at the end of a hard hill session or a 5km race.
- Reserve method. Use both your resting and maximum heart rate, which accounts for individual variation better than max alone.
As a rough guide off threshold heart rate: easy is under 85 percent of it, steady 85 to 92, threshold 95 to 100, and intervals above.
Calibrate your effort scale
Once, do this deliberately. Run 5 minutes at what you believe is 4/10, 5 minutes at 5/10, 5 minutes at 6/10 and 5 minutes at 7/10, with a minute easy between each. Do it on flat ground with the watch face covered. Afterwards, look at the paces and heart rates you actually produced. Most runners find their "4" was closer to a 6, and their "6" and "7" were barely different. Now you know, and you can adjust.
The case for occasionally using neither
One run a week with no watch at all is one of the more useful things you can do, particularly for runners who have become dependent on the numbers.
It rebuilds the connection between how a pace feels and what it is. It removes the temptation to chase a segment. And on the days when you are genuinely tired, it stops the watch talking you into a session your body did not want.
This is #NoAudienceRequired in its most literal form — a run nobody sees, including you.
So which should you use?
If you are new to running: effort, mostly, with heart rate as a guard rail on easy days. Pace will do strange things while your fitness is changing week to week.
If you are a club runner chasing times: pace for sessions, effort for everything else, heart rate as a diagnostic when something feels off.
If you are over 40, or coming back from injury or illness: weight heart rate and effort more heavily. Both pick up accumulated fatigue earlier than pace does, and that early warning is worth more as you get older.
What matters far more than which metric you pick is that you are honest with it. A runner who consistently runs easy days easy using any of the three will beat a runner with perfect zones who runs everything at 6 out of 10.