For a long stretch of my running life, I ran almost every run at the same heart rate — somewhere between 140–160 bpm. It felt aerobic. I could hold a conversation. I'd tell myself it was an easy day. And I'd come home and log it as one.

The problem was that 140 wasn't actually easy for me. It was the high end of easy creeping into the low end of moderate — the grey zone where you feel productive and accumulate fatigue without accumulating fitness. I wasn't recovering. My hard days weren't sharp. And I plateaued for longer than I'd like to admit.

I see the same pattern constantly with athletes who reach out to me. They'll say something like, "I'm so tired from my training, I don't know what's wrong." I'll ask if they have any genuinely easy days. They'll say yes. Then I'll look at their Strava and almost every run is sitting at the same elevated heart rate. Every day is a little strenuous. Nothing is recovery, and nothing is hard enough to drive adaptation.

The fix usually isn't more workouts. It's learning to run easy days slower than your ego wants to let you. Heart rate training, used well, is the single highest-leverage thing a self-coached runner can do. Let me walk you through why.

What elite runners actually do

In the early 2000s, a Norwegian-based sports scientist named Stephen Seiler started studying how the world's best endurance athletes actually trained. Not what they said in interviews — what their training logs showed.

He found something that surprised a lot of coaches at the time: roughly 80% of training volume was at low intensity, and only 20% was at moderate to high intensity. Almost nothing in the middle. This pattern showed up across sports, nationalities, and coaching philosophies. Elite athletes had independently figured out the same distribution.

This became known as polarized training, or the 80/20 rule. The research that's piled up since has been pretty consistent:

If you're a 4:00 marathoner running easy days at 9:00/mile because that "feels easy," there's a real chance your true easy pace is closer to 10:00. And running closer to 10:00 isn't going to make you slower. It's going to make you faster.

Why "easy" is the hardest pace to run

Here's what nobody admits: easy is uncomfortable in a different way than hard. Hard hurts your lungs. Easy hurts your ego. And trust me, I've been there. Even now, after years of coaching, someone will start running past me in the park and every part of me wants to match their pace. I have to consciously hold back. The pull doesn't go away. You just learn to override it.

There are usually four reasons easy days drift too hard:

Ego. Easy pace looks slow on Strava. It looks slow next to your training partners. It looks slow next to what you ran last year. Slowing down feels like losing something, even when the data says it's the opposite.

Misunderstanding what "easy" means. Easy is conversational — you should be able to hold a full sentence without breath gaps. If you're answering questions in three-word bursts, you're not in the easy zone anymore.

The grey zone trap. Moderate effort feels productive. It's where you feel like a runner. But it's the worst possible compromise: too hard to recover from, too easy to drive real adaptation. Most plateaued runners I work with are stuck here. Never fresh enough to do quality work, never relaxed enough to build a real aerobic base.

Your watch is lying to you. GPS pace fluctuates with terrain, wind, signal, and how you started the run. Heart rate is more honest. It tells you what your body is actually doing, not what your splits say.

Why heart rate beats pace as a training guide

I get pushback on this from experienced runners pretty often. They know their paces. They've been running for years. Why complicate things with another data stream?

Here's why I push back. Pace is an arbitrary number. It doesn't know whether you slept four hours, whether it's 85 degrees out, whether you're three weeks into a hard block, or whether you're carrying low-grade fatigue you haven't named yet. Pace doesn't adjust. Heart rate does.

Heart rate is a measure of effort — what your body is actually doing to produce that pace today. Two runners can run the same 8:30 mile and one is cruising while the other is hanging on. Two of your 8:30 miles, on different days, can mean completely different things. Pace tells you the output. Heart rate tells you the cost.

That's why I treat HR as the more useful guide for most runs — especially easy days, long runs, and recovery efforts where the entire point is managing physiological stress. Pace is fine for workouts where the prescription is specific (mile repeats at threshold, marathon-pace miles). Outside those, the watch should be following your effort, not the other way around.

How to actually find your zones

Heart rate zones are personal. Two runners the same age can have max HRs 20 beats apart. A formula that says you're a "Zone 2 runner at 140 bpm" might be telling the truth — or it might be 15 beats off and quietly sabotaging every easy day you do.

So the work is figuring out your numbers, not generic ones.

Step 1: Estimate your max HR (knowing it's just a starting point)

The 220-minus-age formula is everywhere because it's easy. The problem is it can be off by 10 to 30 beats per minute for any individual runner. The Tanaka formula (208 − 0.7 × age) is slightly more accurate, but still an estimate.

For a 40-year-old, both formulas land around 180. For a 25-year-old or a 55-year-old, the gap between formula and reality starts to matter. A 9-beat error in max HR can be the difference between training in your easy zone and training in the grey zone — every single day, for a year.

Step 2: Validate with a field test

If you're going to take HR training seriously, do an actual test. The protocol I like:

  1. Warm up for 15–20 minutes, easy.
  2. Find a steady hill that takes about 90 seconds to run hard.
  3. Run it hard. Jog down. Repeat 3 times.
  4. On the final repeat, sprint the last 20 seconds with everything you have.

Your peak heart rate during that final repeat is much closer to your real max than any formula will give you. (Skip this if you're sick, under-recovered, or have any cardiac concerns flagged by your doctor — it's a maximum effort.)

Step 3: Set your zones

Once you have a real max HR, the zones are pretty standard:

A more accurate method uses heart rate reserve (the Karvonen formula), which factors in your resting HR. If you know both numbers, that's the way to go.

But honestly, the exact zone boundaries matter less than most calculators make you think. The number that matters most is the ceiling on your easy days. Whatever 75% of your max works out to be — that's the line you don't cross. Build your easy runs around that ceiling for 80% of your weekly minutes, and you've solved the problem the math can't solve for you.

The diagnostic that changed how I coach: cardiac drift

This is the part most articles on heart rate training skip. And it's the part I think every runner with a real goal time should understand.

Cardiac drift — sometimes called aerobic decoupling — is the gradual rise in heart rate during a steady-state run, even when your pace stays the same. It happens because as you run, blood plasma volume drops, stroke volume decreases, and your heart has to beat faster to deliver the same amount of oxygen. Heat, dehydration, and underfueling all amplify it.

Why does this matter? Because cardiac drift is one of the cleanest signals of aerobic fitness you can measure without a lab.

The general rule: if your long run shows less than ~5% drift between the first and second half (HR rising relative to pace), your aerobic system is handling the duration well. More than that, and you're running above your true aerobic capacity, even if the pace feels manageable.

The way I use this with athletes: I watch for sessions where drift is unusually high. Sometimes it's just heat or under-fueling — easy to fix. But sometimes it's a leading signal that an athlete is overreaching, that their easy pace has crept up, or that they're not yet aerobically ready for the long-run distance we've planned. Either way, it tells me to pull back, not push harder.

You can run the same diagnostic on yourself. Pick a flat route or a treadmill. Run 60 minutes at conversational effort. Compare your average HR-to-pace ratio in the first 30 minutes vs. the second 30. If the gap is wide, you've got a useful piece of feedback to work with.

Run the 7-day audit on yourself

I put together a simple audit you can run on your own training data this week — plus an interpretation guide that explains what each pattern means and the first thing to fix. Enter your email and I'll send both.

The case for slowing down

I'll close with what I tell every athlete in their first month of working with me: this part is uncomfortable. You will feel like you're losing fitness. You will feel slow. You will see paces on Strava you haven't seen in years and wonder if anyone knows what they're doing.

Then somewhere around week four or five, your tempo run will feel different. Your long run will feel different. The pace you used to hit on a "good day" will start showing up on regular days. And you'll realize that the slowest you've run in a year is what made the fastest you've run in a year possible.

Heart rate training isn't magic. It's just honesty — about what your body is actually doing, what kind of stimulus you're actually applying, and whether your training is actually working. For most runners I meet, it's the unlock.

If you want help putting this into practice — building zones around your real fitness data, structuring a week that actually drives the adaptation you're after — that's the work I do with every athlete I coach. Let's talk.

Related reading

Marathon training for busy professionals →

How to get into the World Marathon Majors →

Olivia Papa
Olivia Papa

Brooklyn-based run coach. 6x marathon finisher. Boston, NYC, London, Berlin, Chicago, and counting!

Read full bio →