When Power Lies: Cadence, Terrain, and Fatigue

Power meters changed cycling training permanently. A number that doesn't lie, tied to the actual work your body is doing — or so the story goes. The reality is more complicated. Raw wattage is an objective measurement of mechanical output, but it is a poor proxy for physiological stress when context is stripped away. Three factors corrupt the signal more than any others: cadence, terrain type, and accumulated fatigue.

Understanding these distortions does not mean distrusting your power meter. It means reading the data correctly.

Cadence: Same Watts, Different Muscles

Two rides, both averaging 250W. One at 95 rpm, one at 65 rpm. Physiologically, these are not the same effort.

At lower cadences, you produce each watt by generating higher force per pedal stroke. That muscular force demand shifts the work toward slow-twitch and fast-twitch fibers differently, increases peripheral fatigue in the legs faster, and raises blood lactate at the same absolute power output. At higher cadences, force per stroke drops, but cardiovascular and metabolic cost rises — heart rate climbs, oxygen consumption increases, and you burn through glycogen faster per kilojoule of work done.

This matters practically in several ways:

• Comparing workouts: A threshold session at 60 rpm is not equivalent to the same session at 95 rpm, even if the power files look identical. The muscular damage and recovery cost differ significantly.
• Pacing on climbs: Many riders naturally drop cadence on steep gradients. If your power target stays fixed but cadence falls from 85 to 55 rpm, your legs are taking on a disproportionate share of the load, and fatigue will arrive earlier than your power number predicts.
• Indoor vs. outdoor: Trainers, especially older fluid and magnetic models, often feel harder at lower cadences than outdoor equivalents at the same power. The inertia profile differs from a real wheel, which can make low-cadence power feel — and physiologically be — more costly.

When reviewing a ride, always look at power and cadence together. A power file without cadence data is missing a key dimension. Most training with power frameworks treat power as the primary variable, but cadence is the modifier that explains why two identical power numbers produce different fatigue outcomes.

Terrain: The Variability Problem

Steady power on a flat road and variable power over rolling terrain can produce identical averages, but they do not produce identical stress on your body.

Consider a rider averaging 220W over an hour. On flat roads, that might mean holding 210–230W continuously. Over a hilly course, it might mean repeated spikes to 380W on punchy rises followed by recovery segments at 100W on descents. The average is the same. The physiological cost is not.

Why Variability Costs More

High-power surges above threshold are expensive. The energy systems recruited during a 10-second spike at 150% of FTP do not recover instantaneously. Each surge draws down glycogen, taxes the neuromuscular system, and generates lactate that takes time to clear. Repeated spikes leave you in a deeper hole than sustained steady-state work at the same average wattage.

This is the core reason that Normalized Power (NP) was developed — to produce a wattage figure that better reflects physiological cost by weighting high-power efforts more heavily than low-power recovery. If your average power and NP diverge significantly on a ride, that gap tells you how much variability you absorbed. A high Variability Index (NP divided by average power) means your body worked harder than your average watts suggest.

For pacing purposes this has direct implications:

• On a flat time trial, riding close to FTP for the duration is manageable because power is steady.
• On a punchy course with repeated short climbs, riding the same average power will leave you far more depleted at the finish, because the surges are burning matches that steady riding does not.
• Descents are nearly free mechanically, but they do not undo the cost of the climb that preceded them. Average power can look moderate while the actual effort was severe.

Terrain also changes the relationship between power and speed in ways that mislead effort perception. A rider generating 300W on a steep gradient moves slowly and may feel like they are not working hard enough, while the same 300W on flat ground at 40 kph feels entirely different. Power is independent of speed, which is one of its great strengths — but it means you cannot use feel or speed to validate whether a power number is appropriate for the conditions.

Fatigue: The Shrinking Yardstick

This is the most insidious distortion. Your FTP — and the zones derived from it — is calibrated at a point in time, under conditions of reasonable freshness. Fatigue moves the goalposts.

When you are deeply fatigued, the power you can sustain at a given RPE drops. The power you generate at lactate threshold drops. Your neuromuscular peak power drops. Every number on your training file is now being measured against a standard that no longer applies.

Acute vs. Chronic Fatigue

Acute fatigue is session-level. Deep into a hard ride, late in a long week, your power at a given heart rate falls — a phenomenon sometimes called cardiac drift in reverse. You are working physiologically harder to produce fewer watts. A target of 270W in the final hour of a five-hour ride costs more than 270W in hour one. Chasing the number in the final hour can mean exceeding your actual physiological threshold even while appearing to ride below it on paper.

Chronic fatigue — accumulated over weeks of training load — suppresses absolute power capacity more broadly. A rider three weeks into a high-load block may find that their perceived FTP tests lower, not because fitness has declined, but because the measurement is no longer being taken at baseline. Using that depressed number to set zones will under-prescribe intensity during a taper or recovery week when the athlete has returned to freshness.

The practical consequence: power zones need to be treated as living benchmarks, not fixed constants. An FTP estimate taken during a recovery week and one taken mid-block can differ meaningfully, and both can be valid — they are just measuring different things.

Signs That Fatigue Is Distorting Your Data

• Heart rate elevated relative to power output (higher than typical HR at a given wattage)
• RPE significantly higher than the power number suggests it should be
• Inability to reach target power during intervals despite strong effort
• Power output declining across repeated efforts that should be matchable

When these signals appear, the right move is to trust RPE and heart rate as secondary inputs rather than forcing the watts target.

Reading Power Honestly

None of this makes power data less valuable. It makes it more valuable, because understanding the distortions lets you extract the real signal.

A practical checklist when reviewing any power file:

1. Check cadence alongside power — identical average watts at very different cadences represent different physiological efforts.
2. Compare average power to Normalized Power — a large gap signals high variability and higher real cost than average watts alone convey.
3. Note where in the ride the power was produced — 300W in the first 20 minutes and 300W in the final 20 minutes of a hard four-hour ride are not the same physiological event.
4. Contextualize against training load — a solo data point without knowing the week's cumulative load is hard to interpret accurately.
5. Use heart rate as a cross-reference — if power and heart rate diverge from their established relationship, fatigue or environmental factors are altering the equation.

Power meters measure mechanical output with precision. What they cannot measure is the physiological state of the athlete generating that output. Cadence, terrain variability, and fatigue all change what a given watt number costs. Accounting for those factors is what separates data-literate training from number-watching.