Take two runners who both hold 300 watts—or a 4:00/km pace—for a flat-out 30-minute threshold test. If you plug their numbers into a standard calculator, they get the exact same training zones and the exact same race predictions. Yet when you put them on a rolling 10K or half marathon course, one absorbs the surges on the hills and finishes on target, while the other blows up at kilometer seven and jogs to the line.

The single-number Functional Threshold Power (FTP) model cannot explain why this happens. It assumes that if two athletes share the same threshold, they share the same physiology above it. They don't.

To see why one runner survives a surge and the other detonates, you have to replace the single threshold number with the two-parameter Critical Power model. Instead of treating your fitness as a single ceiling, it separates your pure aerobic capability from your anaerobic battery—and gives you strict rules for workout execution and race-day pacing discipline.

The blind spot of single-number rFTP

Running Functional Threshold Power (rFTP)—and its equivalent, threshold pace—is the anchor of structured training. As we outline in our guide to setting running zones with Stryd, a properly executed 30-minute field test gives you a reliable benchmark to build your seven-zone system. In our methodology, we prioritize power over pace, and pace over heart rate, because a foot pod reacts immediately to hills and wind while your pulse lags behind.

When I sync a structured workout from TrainingPeaks to my Garmin Forerunner 970, the watch holds me to that single threshold anchor. For steady, uninterrupted running at or below threshold, one number is all you need.

The blind spot appears the moment you cross that line. A single-point test tells you the power or pace where lactate production begins to exceed clearance. It tells you nothing about how much work you can do once you are in the red. One athlete reaches a 300W 30-minute average through a massive aerobic engine with almost no sprint capability; another hits 300W by leaning heavily on a large anaerobic reserve over the final ten minutes. Give them both the same suprathreshold interval session or the same undulating race course, and their responses will diverge completely.

The two-parameter model: Critical Power (CP) and W' (W Prime)

While we have covered how FTP and Critical Power differ in cycling, the distinction is even more punishing in running because of the eccentric muscle damage that accompanies every stride. The Critical Power model splits your high-intensity performance into two distinct metrics:

In the advanced layer of our coaching, we track these exact parameters using WKO5 iLevels, where they are modeled as mFTP (modeled threshold) and FRC (Functional Reserve Capacity). Regardless of whether your software calls it W' or FRC, the mechanics are identical.

The math of a pacing blow-up: Every second you spend above CP drains your W' battery in direct proportion to how far over the line you are. The formula is simple: Work Depleted (Joules) = (Current Power − CP) × Time in seconds.

If your CP is 300W and you surge to 350W up a bridge for 60 seconds, you are running 50W above CP. Multiply 50 watts by 60 seconds, and you have just burned 3,000 Joules (3.0 kJ) of your W' battery.

When that battery hits zero, you do not gradually slow down. You are forced to drop your intensity significantly below CP just to allow the battery to recharge. Even worse, burning through W' early in a race leaves behind metabolic byproducts—hydrogen ions and inorganic phosphates—that impair muscle contractility for the rest of the day. Your legs feel like concrete even after you return to your normal race pace.

Why identical thresholds fail at different points

Now let's return to our two 300W runners lining up for a 10K or a half marathon. Both have set their zones using the Running Zones Calculator, and both plan to pace the race right around their threshold.

Scenario 1: The 10K with aggressive surges. The gun goes off, the pack goes out 30W too hot for the first two kilometers, and the course features three short, steep overpasses. Runner A only has 9 kJ to play with. Every surge up an overpass takes a 2.5 kJ bite out of their reserve. By kilometer six, Runner A's battery is empty. They are forced to back off the pace while Runner B, sitting on an 18 kJ reserve, absorbs the surges and kicks to the finish.

Scenario 2: The flat, steady Half Marathon. Here, the roles reverse. A half marathon for most amateurs takes between 75 and 110 minutes—a duration where W' contributes almost nothing to average speed, and pure aerobic capacity dictates the outcome. If Runner B tries to pace the half marathon off their 300W 30-minute test number, they are actually running 12W above their true 288W CP from the very first step. By kilometer twelve, their 18 kJ battery is completely drained, and they face a long, painful walk-jog to the finish line.

Runner A, meanwhile, sits comfortably at 290W—safely below their 298W CP—without touching a single joule of W' until the final kilometer sprint.

How to apply CP and W' to your workouts and race pacing

Understanding the two-parameter model changes how you execute interval sessions and how you manage effort on race day. In our seven-zone system (1 · 2 · X · 3 · Y · 4 · 5, adapted from Matt Fitzgerald's 80/20 framework), Critical Power sits inside Zone Y, the narrow transition band between Zone 3 and Zone 4.

Because threshold is a shifting physiological boundary rather than a static line on a screen, we avoid prescribing entire workouts in Zone Y. Training right at 100% of a single-point test guarantees nothing: if your W' is large, you might actually be working above your true CP and accumulating excessive fatigue; if your W' is small, you might be under-stimulating your upper aerobic ceiling.

1. Match your Zone 4 and 5 intervals to your battery

When we prescribe work above threshold—Zone 4 and Zone 5—you are intentionally draining and recharging W'. A runner with a large W' will find short micro-intervals (like 30 seconds hard, 30 seconds easy) deceptively comfortable because their anaerobic battery buffers the effort before their aerobic system is forced to adapt. To genuinely pull their CP upward, they need longer, continuous threshold and VO2max blocks (such as 3 × 15 minutes in low Zone 4, or 5 × 4 minutes in Zone 5) that exhaust the battery early and force oxidative metabolism to carry the load.

Conversely, a low-W' diesel runner who struggles to hit top-end paces benefits from shorter, higher-power reps that develop neuromuscular recruitment and build anaerobic capacity without causing premature form breakdown.

2. Feed the model accurately

If you rely on automated Critical Power tracking in Stryd or WKO5, remember that the algorithm only knows what you feed it. In our coaching setup, we actively monitor the power-duration curve. If an athlete has only run steady aerobic miles and marathon-pace blocks for eight weeks, their short-duration power (Pmax and W') drops in the software, which artificially caps or distorts their modeled threshold. When we see that happen, we insert dedicated short max-effort probes—such as all-out 15-second hill sprints or a 3-minute hard effort—into the weekly schedule to keep the model honest.

3. Cap your power on hills in the marathon and half marathon

In a half marathon or marathon, your W' is an emergency reserve, not a pacing tool. Your goal is to cross the start line and reach the final two kilometers without burning a single match. Because running power rises instantly when you hit an incline, holding an even pace on a rolling course will repeatedly spike your output above CP.

The race-day ceiling rule: In any race lasting longer than 60 minutes, your hard ceiling on hills is 100% of CP. Shorten your stride, let your pace drop on the incline, and keep the watts below threshold so your W' stays untouched for the final kilometers.

This pacing discipline only works if you have built the underlying fatigue resistance to hold your form late in the race—what we cover in our breakdown of marathon durability and avoiding the wall. You build that durability through polarized volume (80% of your week in low Zone 1 and 2, staying out of the Zone X marathon-pace trap on easy days) combined with year-round heavy strength work in the gym.

If you are preparing for a 42K block and want that exact structure—polarized volume, specific threshold progression, and integrated strength sessions already laid out in TrainingPeaks—choose the build that matches your current weekly mileage and preferred metric:

[70% OFF] 12 Week Marathon Build: Run 🏃 + Gym Lifting 🏋️ (Intermediate 90-110km)

12 weeks · Intermediate · Pace based · Includes gym work

For intermediate marathoners running 90–110 km per week who want a 12-week pace-based build with integrated gym strength.

US$ 49.99

[70% OFF] 18 Week Marathon Build: Heart Rate 💓 (Intermediate Vol: 90-110km) - Includes Strength

18 weeks · Intermediate · Heart rate · Includes gym work

For intermediate runners who prefer an 18-week heart-rate-guided marathon progression (90–110 km/week) with full strength programming.

US$ 59.99

12 Week Marathon: Run 🏃 + Gym Lifting 🏋️ (Beginners 55 to 88 km / week)

12 weeks · Beginner · Pace based · Includes gym work

For marathoners building up on 55–88 km per week who need a structured 12-week pace and gym plan.

US$ 49.99

When a single 30-minute test is still all you need

Here is the honest counter-argument against the two-parameter model: calculating true Critical Power and W' requires multiple all-out exhaustive efforts across different durations—typically a 3-minute max effort and a 12-to-20-minute max effort on separate days, or a continuous feed of max-effort data into a foot pod ecosystem. If you pace the 3-minute test poorly, or if you run the 12-minute test on tired legs, the linear regression tilts and gives you a skewed CP and a useless W'.

For a recreational runner training five to eight hours a week without a power meter, staging three separate maximal field tests in a ten-day window costs too much recovery and invites injury. In that case, a single, well-executed 30-minute threshold test—as detailed in our guide to threshold training without lactate strips—remains the most practical anchor you can use.

You do not need a software curve to apply the lesson of W' prime. Even if you train and race purely off a single 30-minute threshold pace and a heart rate strap, the physiological law holds: every second you spend surging above threshold in the first half of a race is borrowed against a tiny, finite battery. Respect the ceiling on the hills, keep your easy days genuinely easy, and save the battery for the finish line.