How fast should an easy run be?

Between 1.20 and 1.35 times your threshold pace. If your threshold is 7:00 per mile, easy is 8:24 to 9:27. That range is deliberately wide because the only error that matters on an easy day is running it too hard, and most runners run their easy days 20 to 40 seconds per mile faster than they should.

Should I use heart rate or pace for easy runs?

Heart rate, at 60 to 70 percent of your maximum. Pace drifts several percent with heat, hills and accumulated fatigue while heart rate reflects the actual physiological cost. On interval days the reverse holds — heart rate lags the effort by 30 to 60 seconds and is useless for a three-minute rep.

Why do easy runs feel too slow?

Because the correct easy pace genuinely is uncomfortably slow at first, and because a lifter's instinct that hard work produces adaptation is correct in the gym and counterproductive here. Easy running produces its adaptation through accumulated volume at low intensity; running it harder converts a nearly free session into an expensive one.

Does running easy actually build fitness?

Yes, and it builds the part of endurance fitness that responds slowest and decays slowest. It also builds it at almost no recovery cost, which is precisely what makes it valuable to a hybrid athlete — it is the only training stimulus available that does not compete with your lifting.

How do I know if my easy runs are too hard?

Compare your last four easy runs against 1.20 to 1.35 times your threshold pace, or check what proportion of each run sat inside the 60 to 70 percent max heart rate band. If most of them ran faster than the slow end of the band, they were not easy days, whatever they were labelled.

Your Easy Runs Are Too Fast (And It Is Costing You Squats)

What "easy" is actually for

Easy running produces its adaptation through accumulated volume at low intensity. Capillary density, mitochondrial density, stroke volume, fat oxidation, tendon and bone tolerance for repeated loading. All of them respond to time spent, not to intensity.

That set of adaptations is the part of endurance fitness that responds slowest and decays slowest. It is also, for a hybrid athlete, the only training stimulus available that does not compete with your lifting. A genuinely easy hour costs almost nothing in recovery terms. An hour at tempo pace costs a great deal.

The whole reason easy volume is valuable to someone who also lifts is that it is nearly free. Running it hard removes exactly the property that made it worth doing.

Why a lifter gets this wrong specifically

A lifter arrives at endurance training with a correct and hard-won instinct: hard work produces adaptation, and if it did not feel like something, it probably was not. In the gym that instinct is right. Proximity to failure genuinely matters; a set at 6 RIR is a warm-up.

Applied to easy running it is exactly backwards, and it does not feel wrong while you are doing it. An easy run at moderate pace feels productive. It feels like you did something. That feeling is the problem — the session that felt like nothing was the correct one.

There is a second contributing factor, which is that the correct easy pace often feels embarrassing. Slower than people expect to run, slower than the people around you, slower than your own historical average. Nobody's ego is served by it.

What it actually costs

Consider a week with four lifting sessions and four runs: three easy, one threshold.

Run correctly, that is five hard sessions — four lifts and one threshold session — with three cheap aerobic sessions layered around them. That is a demanding but coherent week.

Run with the easy days twenty-five seconds per mile too fast, it is eight hard sessions. Nothing was removed to make room. Lifting volume was not reduced. Recovery capacity did not increase.

This is the mechanism by which people who have correctly scheduled around the interference effect — separate sessions, six hours apart, moderate volume — still experience interference and conclude the research is wrong. The research prescribes intensity. The field does not.

Finding your real band

Step one: get a threshold. Run as hard as you can sustain for a flat twenty to thirty minutes, record the distance, and project it to a one-hour equivalent with the Riegel formula. The threshold pace calculator does the arithmetic.

Do not skip to a rule of thumb. "Conversational pace" is the usual advice and it is unreliable — plenty of people can hold a broken conversation well above their easy band, especially when fit and especially when motivated.

Step two: use the band, and use heart rate to enforce it.

Metric	On easy days	On interval days
Pace	Secondary	Primary
Heart rate	Primary	Useless — lags 30–60 s

Heart rate is the right primary signal on easy days because pace drifts. The same effort is thirty seconds per mile slower in heat, on hills, into wind, and on tired legs. Chasing a pace number under those conditions means running harder to hit it — precisely the wrong response.

The band is 60 to 70% of your maximum heart rate. If you do not know your maximum, an age estimate is acceptable here because the band is wide; it is not acceptable for interval prescription.

Step three: check the last four runs. Not your perception. The recorded data. What proportion of each run sat inside the band?

The two-week adjustment

The correct easy pace will feel wrong for roughly two weeks. Specifically:

Days 1–4: frustratingly slow. Form feels awkward. Cadence drops and it feels shuffly.
Days 5–10: the pace stops feeling like a constraint. Heart rate at the same pace begins to fall.
Days 10–14: the same heart rate now buys a faster pace, and the band moves down with you.

That last effect is the entire point and it is measurable within a fortnight. It is also the reason to obey heart rate rather than pace: the band should move, and it only moves if you let the pace follow the heart rate rather than the other way around.

Getting graded instead of self-assessing

The reason this failure persists for years is that nothing tells you. You label a run "easy" in an app and the app agrees with you, because the label was an input rather than an assessment.

Being graded against the band changes it from an opinion to a fact. Base grades every endurance session on how much of its measured time fell inside the prescribed band, and reports "over" when an easy day ran hard. Three "over" grades in a row on easy days is a diagnosis, not a nag — and it is the pattern, not any single session, that means something.

Grading on time-in-zone rather than on the session average matters here more than anywhere. An average hides the run that went out too hard and limped home: the fast first half and the slow second half cancel, the mean lands comfortably inside the band, and a run that was almost never in the band grades as a success. How grading works.

Common mistakes

Using "conversational" as the test. Unreliable, and it drifts upward as you get fitter.
Chasing a pace number in the heat. The same effort is slower when it is 85°F. Let it be slower.
Treating an easy run as a chance to make up for a missed session. That is a hard session with an easy label.
Running easy days with faster people. The most common practical cause, and the least addressable by any app.
Not having a threshold at all, so "easy" is a vibe rather than a band.
Adding strides at the end and calling the run easy. Strides are fine. They also mean the session was not purely easy, and the week's hard-session count should know about it.

What to do next

Pull up your last four easy runs and compare their average pace against 1.20 to 1.35 times your threshold. If most of them were faster than the slow end of that band, you have found the reason your lifting has been degrading, and it is a free fix — the correction costs nothing and returns recovery capacity immediately.