I used to think effort and output were the same thing. Push harder, run faster, get fitter. So I did. I went out too hot on every run, hit a wall by kilometer three, limped home, and wondered why my times weren't improving. Turns out I wasn't training smart — I was just training tired. If you've been stuck in the same cycle — grinding every session at the same all-out effort, burning out mid-run, and seeing no real progression — the fix isn't more willpower. It's understanding how to manage your energy across different types of runs.

Your body runs on two fuels, and intensity decides which one

Your muscles don't run on hustle. They run on adenosine triphosphate (ATP), which your body produces by burning two main fuel sources: fat and carbohydrates.

Here's the part most runners don't know: the fuel your body chooses depends almost entirely on how hard you're working.

At low to moderate intensity, your body prefers fat. At Zone 2 effort, fat oxidation peaks — your body derives approximately 60–70% of its energy from fat at this effort level. Fat is slow to convert, but you have enormous stores of it. Even a lean 150-pound runner carries enough fat energy to fuel hours of moderate-intensity running.

At higher intensities, your body switches to carbohydrates. Your body pulls glucose from your bloodstream first. When this is exhausted, it taps into stored glucose, called glycogen, in your liver and muscles. The rate at which glycogen is depleted depends on the intensity and duration of exercise. The problem? Carbohydrate stores are limited. Most people have roughly 90–120 minutes of glycogen at moderate-to-hard effort before things start going south.

This is why running at the same hard pace every day is counterproductive. You're draining your carbohydrate tank on sessions that should be easy, leaving nothing in reserve for the sessions that genuinely demand it.

What heart rate zones actually mean

Heart rate zones are a way of translating intensity into something measurable. Most systems use five zones, though the specific percentages vary slightly by coach or platform.

Here's a practical breakdown:

The classic formula for max heart rate is 220 minus your age. A 30-year-old would have an estimated max of 190 bpm. So Zone 2 for them sits between roughly 114–133 bpm. That said, this formula has a standard deviation of ±10–12 beats per minute, so treat it as a starting point rather than gospel.

The bigger insight here is that as exercise intensity increases beyond Zone 2, the body's energy demands shift to favor a lactate-producing metabolism (glycolysis) over a lactate-consuming metabolism. At these higher intensities, carbohydrate use increases as a rapid fuel source while fat burning slows down.

In plain terms: go too hard too often, and you're constantly draining the tank you need the most.

How hard should each session actually be?

Not all runs are created equal. Professional coaches divide training into distinct session types, each with a specific intensity target. Here's how to think about them.

Recovery and easy runs: effort 3–5 out of 10

These runs make up the bulk of your week — somewhere between 70–80% of your total mileage. They should feel genuinely easy. You should be able to hold a full conversation without any audible strain. Aim for Zone 2, keeping your heart rate below 72% of your maximum.

Most runners get this wrong. They run their easy days too hard, which means they show up to hard sessions already depleted. Easy days are not wasted miles. They're when your aerobic engine gets built.

Tempo and hill sessions: effort 7–8 out of 10

These runs should feel comfortably tough. You can say a few words, but not a complete sentence. You're working hard and you know it, but you're not panicking. This is your lactate threshold zone — the effort level you can sustain for roughly 30–60 minutes depending on your fitness.

A key rule here: stay disciplined. It's tempting to push into Zone 5 territory on a good day, but if you do, recovery takes significantly longer, and your next quality session suffers.

A typical tempo structure:

• For a 5K runner: 3 × 6 minutes (2-minute jog between)

• For a marathoner: 10 × 2 minutes on / 1 minute off

Interval and track sessions: effort 8–9.5 out of 10

This is where you push hard. These are your VO2 max efforts — short, intense bouts that train your cardiovascular ceiling. Heart rate should peak at around 95% of your maximum toward the end of the session. Most of the work is done faster than your goal race pace.

A typical interval structure:

• For a 5K runner: 6 × 2 minutes (75-second recovery)

• For a marathoner: 8 × 1km (90-second recovery)

Keep a small reserve — about a half a percent — for race day. Training should be hard, but it shouldn't empty the tank completely.

Quality long runs: effort 8–9 out of 10

If you're targeting a half marathon or marathon, this is the week's most important session. Large portions of this run should be done at your target race pace, teaching your body what that effort actually feels like. Start in Zone 3, build into Zone 4.

The critical rule: don't fully empty the tank. That's what race day is for. Save 5–10% for when it counts.

A typical quality long run:

• For a 5K runner: 10/8/6/4/2 minutes (2-minute jog between)

• For a marathoner: 4 × 5K (1km recovery jog between)

RPE: the best tool you're probably not using

Heart rate monitors are useful, but they have blind spots. Heat slows your pace while spiking your heart rate. Altitude, dehydration, poor sleep, and stress all skew the numbers. Factors like weather, terrain, stress, and fatigue can make pace and heart rate unreliable metrics. That's where Rate of Perceived Exertion (RPE) comes in — a simple yet effective way to measure effort and keep your training on track.

RPE is a 1–10 scale of how hard you feel you're working. It's not scientific in the clinical sense, but it's validated by decades of sports science. Research shows that RPE scales with the proportion of exercise time that remains — meaning your body's perception of effort is closely tied to pacing and duration, not just heart rate.

Here's what each zone feels like in plain language:

• RPE 3–5: Easy. Could chat happily. Breathing is barely elevated. (Recovery runs)

• RPE 6–7: Moderate. Breathing is deeper but controlled. A sentence takes some effort. (Steady aerobic work)

• RPE 7–8: Comfortably hard. Short phrases only. A little uncomfortable. (Tempo)

• RPE 8–9.5: Hard to very hard. One or two words at most. Heart is loud. (Intervals, long run portions)

RPE adapts to factors like heat, hills, and fatigue. An easy pace on a hot day might feel like a 5 RPE instead of a 3. Stick with the effort rather than trying to match your usual pace. This makes RPE especially useful on days when conditions aren't ideal.

I personally use RPE as my primary guide on anything over 10 kilometers. It's freed me from obsessing over my watch and helped me tune into what my body is actually telling me.

Fuel your session type, not just your hunger

What you eat before a run directly affects which fuel your body uses — and how long it can sustain the effort.

Your body's muscles run on two primary fuel sources: carbohydrates and fat. Dietary carbohydrates are broken down into simple sugars called glucose. During the start of a run, your body pulls glucose from your bloodstream. When this is exhausted, the body taps into stored glucose, called glycogen, in your liver and muscles.

Here's how to match fuel to session type:

For easy and recovery runs: These sessions run primarily on fat. A light meal 1–2 hours before is fine, or you can run fasted (in the morning, before breakfast) to train your fat-burning capacity. No need to carb-load for a 40-minute easy jog.

For tempo and interval sessions: These are carbohydrate-dependent. To burn more carbohydrates, consume foods high in carbohydrates 2–4 hours before your workout. This ensures that both your liver and muscle glycogen stores are topped up. A banana, rice, or oats a couple hours out is a reliable approach.

For long quality runs: A 2024 study in the journal Nutrients found that when runners completed a 1,500m time trial after restricted carbohydrate intake (less than 1.5g/kg/day), their performance was significantly slower — by about 2% — compared to a high-carbohydrate condition. For race-pace work, carbohydrate availability isn't optional.

And don't forget hydration. Even mild dehydration (losing 2% of body weight in fluids) has been shown to impair endurance performance. Drink 400–600ml of water 2 hours before a run, and aim to replace fluids during longer efforts.

Start conservative, finish strong

One of the most consistently reliable strategies in endurance running is progression pacing: starting slower than you think you need to, then building speed through the session.

This works because glycogen is finite. If you start at 90% effort in the first kilometer, your glycogen stores are already racing toward empty. By kilometer five, your pace slows, your form deteriorates, and the run becomes a grind instead of a training stimulus.

The reverse approach — starting controlled and picking up pace — keeps glycogen in reserve, lets fat do more of the early work, and allows you to finish strong. This is exactly what you want your body to practice before race day.

A simple rule: if you feel unusually good in the first 10 minutes of a run, resist the urge to speed up. Use that energy in the back half.

Running consistently burns a meaningful number of calories per session. If you're curious about the exact figures, I've broken them down in detail in How many calories are burned running a mile?

The 80/20 principle: most of your running should feel easy

Here's the uncomfortable truth for hard-charging runners: most of your weekly training should feel easy.

For endurance athletes like distance runners, about 80% of their training is spent building a huge aerobic base, and the rest of their training focuses on speed work and race pace practice.

This is called the 80/20 rule, and it's backed by decades of research on elite endurance athletes. The logic is simple. Hard sessions break your body down. Easy sessions rebuild it. Without sufficient recovery volume, you can't absorb the adaptation from the hard work you're putting in.

If every run is hard, no run is actually hard. Your body adapts to whatever stimulus it gets repeatedly. Variety — specifically the contrast between truly easy and genuinely hard — is what drives improvement.

Final thoughts

Managing your energy during a run comes down to one idea: match the effort to the session. Easy days should genuinely feel easy. Hard days should be hard — but controlled. And the fuel you bring to each session should reflect what that session actually demands.

The runners who improve fastest aren't the ones who push hardest every day. They're the ones who understand when to go hard, when to hold back, and how to read their own body's signals. Start applying this framework to your next training week, and I'd bet you notice the difference within two or three sessions.