Intensity Control in Threshold Intervals

You have a threshold interval session on your training plan. Four eight-minute reps with short recovery. The first block starts, you check your watch, and your heart rate is in Zone 2. You feel slow, so you accelerate to force your heart into the target zone.

By minute three, your heart rate finally hits the target. By minute six, your breathing is out of control, your legs are burning, and you are counting the seconds to finish. On the third rep, you cannot hold the pace. On the fourth, you quit or finish shuffling.

You just made the most common mistake in quality training: using heart rate as your primary metric for short, intermittent efforts. You turned a session designed to push your aerobic threshold into an anaerobic effort that generates excessive fatigue and requires days to absorb.

The problem is not your fitness. The problem is your dashboard. Heart rate fails when intensity changes fast. To train your threshold without relying on lactate strips, you need to change your metric hierarchy and learn to self-regulate the effort.

Why heart rate lies during intervals

Heart rate does not measure the mechanical work you are doing. It measures how your body responds to that work. That response presents two fundamental problems when you run or ride intervals.

The first is physiological lag. When you go from an easy jog to threshold pace, your muscles demand oxygen immediately, but your heart takes 60 to 90 seconds to reach the heart rate corresponding to that effort. If you push to hit your target heart rate zone in the first 30 seconds, you are running at VO2max pace or faster. When your heart rate finally stabilizes, you have already built an oxygen debt and an accumulation of metabolites that you cannot clear at your current pace.

The second problem is cardiac drift. As the session progresses, your core temperature rises, you lose fluids, and your blood volume drops. To pump the same amount of blood and oxygen to the muscles, your heart has to beat faster. On the fourth rep of your set, holding the same heart rate as the first rep means you are running slower or pushing fewer watts. If you keep your heart rate fixed, the actual intensity of the session drops.

The metric hierarchy: power and pace

To solve lag and drift, we use output metrics. These are numbers that measure the exact mechanical work you are producing in real time, regardless of whether you are fresh or fatigued, hydrated or dehydrated.

In the Triaperformance model, intensity prescription follows a strict hierarchy based on the sport.

On the bike, power dictates over heart rate. Watts are absolute. If your target is 250 watts, pushing the pedal with that force will register 250 watts on the first second of the interval and on the last. Heart rate is monitored afterward to evaluate the internal cost of that effort, but it is never used to regulate the interval.

In running, the hierarchy is power (if you use devices like Stryd), followed by pace, and finally heart rate. Running power normalizes the terrain: it allows you to maintain the same physiological effort when running up a hill or into a headwind. If you do not measure running power, pace on flat terrain is your best anchor.

Heart rate is relegated to a secondary role. It ensures your easy runs (Zone 2) stay easy, and it serves as a post-session analysis tool. But in the moment of truth, during a threshold interval, you look at watts or pace.

Self-regulation and RPE: when the watch is wrong

Power or pace zones are calculated from a field test. That test was done on a specific day, at a specific temperature, with a specific level of fatigue. You do not train in a lab.

Today it might be 85°F (30°C) with 80% humidity. Or maybe you slept poorly three nights in a row. Or you are coming off a high-stress week at work. Under those conditions, your actual threshold today is lower than the number in your TrainingPeaks account.

If you cling to the prescribed number regardless of context, you will cross the line and enter anaerobic territory. This is where Rating of Perceived Exertion (RPE) comes in. RPE is not an excuse to back off when it hurts; it is a cross-calibration metric.

In our system, we teach athletes to correct the session on the fly. The physiological goal of a threshold session is to accumulate time just below the lactate inflection point. That state has a clear sensory signature:

• Breathing: Deep and rhythmic, but not panting. If you lose control of your breathing rate, you went too hard.
• Speech: You can say single words or a very short phrase, but holding a conversation is impossible.
• Sustainability: You feel you could hold that pace for 45 to 60 minutes in a pure race scenario, even though it hurts.

If the plan asks you to run at 4:00 min/km (6:26 min/mile) or pedal at 260 watts, and three minutes in your breathing is erratic and the effort feels like a 9 out of 10, you must slow down. You adjust to 4:05 min/km (6:34 min/mile) or 250 watts until the sensation matches the threshold signature. The physiological target beats the watch.

The 7-zone model and the traps in the middle

Almost all smartwatches come configured with five generic zones. We use a polarized seven-zone model (1, 2, X, 3, Y, 4, 5). This is not to overcomplicate training, but to isolate two intensities that destroy the progress of amateur athletes.

Zone X: the marathon pace trap

Zone X occupies the upper half of what is traditionally Zone 2. It is your marathon pace, or the pace you naturally settle into when you feel good and decide to push a little. We isolate it in our model for a clear reason: it accumulates significantly more fatigue than low Zone 2, but returns practically the same aerobic benefit.

Spending your recovery or base runs in Zone X is the fastest route to a plateau. You arrive at your threshold session with heavy legs, fail to hit the required watts or pace, and your quality training loses its effect. Easy sessions must stay below Zone X.

Zone Y: the false threshold

Zone Y is the floor of Zone 4. It is that intensity band near threshold but not quite touching it. We avoid it for the opposite reason we avoid Zone X: threshold is not a static line, it is a dynamic range. If you spend your quality session training in Zone Y, you pay the physical and mental cost of a hard workout, but you fall short of the stimulus required to force a real adaptation.

If you are going to pay the metabolic price of an interval session, pay it above Zone Y, at true threshold. Do not stop halfway.

The advanced layer: power and the WKO5 model

For cyclists training with a power meter, threshold is not managed as a fixed number reviewed every three months, but as a living model. We use WKO5 and its iLevels to keep zones updated in real time.

The software calculates your mFTP (modeled functional threshold power) based on everything you do. But a mathematical model is only as good as the data it receives. If you spend eight weeks doing only aerobic work and controlled intervals, your power curve artificially flattens. Your maximum capacity (Pmax) or functional reserve capacity (FRC) begin to limit the model, and your calculated mFTP drops even if your actual fitness is rising.

To prevent this, we insert very short maximum efforts (15 to 30-second sprints, 3 to 5-minute all-out efforts) into standard weeks. These peaks feed the algorithm, uncap the ceiling of the model, and ensure the threshold prescription remains precise without needing a 20-minute test every month.

When to recalibrate your numbers

If you are consistent, your threshold moves up. A pace that today requires an 8 out of 10 effort will be a 6 out of 10 in eight weeks. If you do not update your zones, you will end up training in Zone Y instead of Zone 4.

The standard testing cadence is every two to three months. However, two clear signals indicate you should test early:

• RPE drops. You hold your prescribed threshold watts or pace and notice you can speak more fluently or the muscular burn is gone.
• Negative decoupling. You finish a long interval and your heart rate, instead of drifting upward, remains flat or even drops slightly compared to previous weeks at the same intensity.

If, on the other hand, you have been sick, traveling, or missed more than ten days of training, your threshold drops. Do not try to resume your previous numbers. Execute a two-week return phase based on pure Zone 1 and 2 with short activations, assume your threshold fell, test again, and reset from there. Ego is not a training metric.

---

The lactate argument: precision vs. pragmatism

Those who advocate for blood lactate measurement point to an undeniable truth: lactate is the gold standard for measuring actual internal load. A test strip does not suffer from cardiac drift, is not affected by headwinds, and does not rely on your subjective perception. It tells you exactly what is happening in your capillary metabolism in that exact second. That is why Norwegian professionals prick their fingers during every recovery block.

But technical precision does not always translate to a better practical result. For a professional athlete training 25 hours a week, the difference between working at 98% of their threshold and 102% determines whether they will absorb the next day's double session or collapse midweek. Their margin of error is zero.

For an athlete training 6 to 12 hours a week, the margin is much wider. The biggest risk for this profile is not missing by two millimoles of lactate in an interval; the biggest risk is running easy runs too hard (Zone X) and hard intervals too easy (Zone Y).

If you execute a rigorous field test, correctly define your zones based on power or pace, and learn to self-regulate effort using RPE when environmental conditions change, you will get 95% of the physiological benefit. You will do it without the logistical, financial, and mental cost of stopping your workout to analyze a drop of blood on the side of the road. Consistency in execution always beats extreme precision on paper.