Why Your Watch Pace Is Lying to You

You ran 9:00/mile today. Last Tuesday, also 9:00/mile.

Same fitness. Same effort. Right?

Maybe not. Tuesday was flat, 60°F, fresh legs after a rest day. Today was rolling hills, 82°F, and you slept five hours. Your watch displayed the same number both times. But Tuesday’s 9:00 was a cruise. Today’s 9:00 nearly broke you.

Your watch pace is measuring the wrong thing. It’s measuring speed over ground. What you actually need to know is how hard your body is working to produce that speed — and those are two very different questions.

Pace measures motion, not effort

GPS pace is simple: how fast are you covering distance. It’s been the default running metric since GPS watches hit the market in the early 2000s, and it stuck because it was the first thing watches could measure reliably.

But pace was never designed to be an effort metric. It’s a speed metric. The distinction matters because your body doesn’t experience speed — it experiences workload. And workload depends on variables that pace ignores completely.

There are three big ones.

Hills change the math

This is the one most runners intuitively feel but rarely quantify.

Running a 9:00/mile on a 4% uphill grade requires roughly the same energy as running an 8:15/mile on flat ground. The physiologist Alberto Minetti published the energy cost curves for graded running decades ago, and the data is unambiguous: even a moderate incline dramatically increases the metabolic cost per mile.

The reverse is also true. A 9:00/mile on a gentle downhill is easier than a 9:00 on flat ground. Your watch says the same number in both cases. Your legs and lungs know better.

This is why hilly runs are so demoralizing for pace-focused runners. You look at your splits and see 9:30, 9:45, 10:00 on the climbs, and some part of your brain whispers that you’re getting slower. You’re not getting slower. You’re running uphill. The effort might be exactly where it should be — but pace can’t tell you that.

Strava partially addresses this with Grade Adjusted Pace, which adjusts your splits for elevation changes after your run. It’s a useful tool. But it only adjusts for one of the three variables, and it only shows up in post-run analysis. You can’t make mid-run decisions based on a number you won’t see until you’re back home.

Heat and fatigue change the cost

Same route. Same pace. One day it’s 58°F, the next it’s 88°F.

Your pace is identical. Your heart rate is 15 beats higher on the hot day. Your body is doing significantly more work to maintain the same speed — diverting blood to the skin for cooling, increasing cardiac output, burning through glycogen faster.

Pace doesn’t know any of this. It reports 9:00/mile and moves on.

Fatigue works the same way. Mile 3 of a long run and mile 18 of the same long run at the same pace are not the same effort. By mile 18, your cardiac cost per unit of pace has drifted upward — your heart rate is higher for the same speed. This is cardiac drift, and every distance runner has experienced it. Your watch pace stays steady while your body quietly deteriorates underneath it.

The practical consequence: runners who train by pace alone regularly run their easy days too hard and their hard days not hard enough. The pace number looks right, but the internal cost is wrong.

Your body isn’t the same every day

Even without hills or heat, the same pace costs different amounts on different days. Poor sleep, stress, dehydration, incomplete recovery from a hard session, hormonal cycles, altitude — all of these shift your cardiac cost for a given pace.

Experienced runners develop a feel for this. They learn to recognize when 9:00 feels easy and when 9:00 feels like 8:15. But “feel” is imprecise and unreliable, especially when you’re tired — which is exactly when you need the information most.

Heart rate monitors help, but they only tell you part of the story. Knowing you’re at 152 bpm tells you which zone you’re in. It doesn’t tell you whether 152 bpm is appropriate for your current pace on your current terrain. Zone 3 at 9:00/mile on flat ground means something different than Zone 3 at 9:00/mile on a 5% grade.

What runners actually do about it

Most runners solve this problem manually, whether they realize it or not. They glance at pace, then glance at heart rate, then factor in the terrain they can see, then make a gut judgment about whether the effort is right.

This works reasonably well for experienced runners on familiar routes. It breaks down on new routes, in unfamiliar conditions, during races, and for anyone who hasn’t developed years of calibrated intuition.

Some runners abandon pace entirely and train by heart rate alone. This solves the cardiac cost problem but creates a new one — heart rate lags pace by 30-60 seconds, making it a poor real-time guide for anything faster than easy running. And heart rate zones don’t account for terrain either. If your Zone 2 ceiling is 150 bpm, a 4% climb will push you past it even when your effort is genuinely easy for the grade.

There’s a gap here. Pace measures motion but not cost. Heart rate measures cost but not context. Neither one, alone, tells you what you actually want to know: how hard is this effort, really, right now, given everything?

The metric that’s missing

What you’d want — in a perfect world — is a single number that combines all three inputs. Your actual pace, your cardiac cost relative to your own personal baseline, and the terrain you’re on. A number that adjusts in real time. A number that, on flat ground with normal effort, just equals your pace — but on hills, in heat, or on tired legs, shows you the truth about what that pace is actually costing.

A number that answers: if this terrain were flat and my body were in a neutral state, what pace would I be running?

That’s what I’ve been building. I call it Effort Pace, and it’s coming to Apple Watch this summer.

But even if you never use the app, the core idea is worth internalizing: pace is a speed metric, not an effort metric, and treating it as both leads to bad training decisions. The next time you finish a hilly run and feel disappointed by your splits, remember that the number on your watch was only measuring one of the three things that determine how hard you worked.

The hills knew. Your heart knew. Your watch didn’t.

Effort Pace launches on Apple Watch in Summer 2026. Free. No account required. Get notified at launch →