What actually causes training plateaus for amateur cyclists

You have been training consistently for months and the numbers have not moved. The usual advice arrives immediately: push harder, add volume, find a new plan. All three assume the cause is effort. For most amateur cyclists it is not — and prescribing before diagnosing is how a three-week stall becomes a three-month one.

What a plateau actually is

A plateau is a stretch — call it eight weeks or more — where your training is broadly unchanged and your performance is broadly unchanged with it. That definition matters, because two common experiences get mislabelled and are not the same thing.

The first is normal variation. FTP measured in February and again in March can differ by several watts in either direction for reasons that have nothing to do with fitness: sleep the night before, caffeine, room temperature, how hard you were willing to suffer that day. Two flat tests six weeks apart is noise, not a trend.

The second is a diminishing-returns curve being read as a wall. A rider in their first full year of structured training might add 30 or 40 watts to FTP. In year four, on the same hours, 5 to 10 watts is a good season. Nothing has broken — the easy gains were spent. That situation calls for a different response, covered further down.

Your training load stopped going up

This is the most common cause and the easiest to miss, because it hides behind consistency. You ride four times a week, every week. Tuesday is 3x10 at threshold, Thursday is 4x4 at VO2, Saturday is two hours endurance, Sunday is an easy hour. It has been that way since last autumn.

That is a well-built week, and it is a maintenance week. The body adapts to a stimulus and then stops adapting to that same stimulus. If 3x10 at 100% of FTP was hard in October and comfortable in March, you got fitter and then held there, because nothing asked for more.

Progression does not require more hours, which matters if hours are the thing you do not have. It requires one variable to move:

• Interval duration. 3x10 becomes 3x12, then 3x15, at the same target.
• Total work at target. 3x10 becomes 4x10 — 30 minutes at threshold becomes 40.
• Density. Recovery between reps drops from five minutes to three, so the session gets less forgiving without getting longer.
• Target. Sweet spot moves from 88% to 92% of FTP; VO2 reps move from the bottom of the range to the top.

Move one variable at a time, hold it for three or four weeks, take an easier week, then move it again. A week that never gets harder produces a season that never gets faster.

Your easy rides got harder and your hard rides got easier

This is the signature failure of a rider on five or six hours a week, and it arrives gradually enough that nobody notices the day it started.

With limited time, easy riding feels wasteful. So the Saturday endurance ride creeps from 60% of FTP up to 72%, then 78% — still conversational for the first hour, but heart rate now drifts steadily and the ride costs real recovery. Meanwhile Tuesday intervals arrive on legs that never quite cleared, so 4x4 that should sit at 110 to 118% of FTP gets ridden at 102% with heart rate pinned from the second rep.

The result is a week where everything happens in one narrow band around tempo and upper endurance. That band is expensive: enough fatigue to blunt the next session, not enough time near maximum aerobic power to drive the VO2 adaptations, and not enough genuinely low intensity to build the aerobic base underneath. You pay for two kinds of training and buy neither. The Zone 2 versus Zone 3 trade-off is the same mechanism seen from the other side.

The fix is uncomfortable for about two weeks: make the easy rides genuinely easy — low enough that you finish feeling you could do it again tomorrow — and spend the recovery that buys on hitting the hard sessions at their actual targets. Weekly training stress may drop slightly. The training effect usually goes up.

Every session is landing at 90 percent

The third cause is subtle, because nothing looks wrong in the log. Every planned session got done. Tick, tick, tick. But the VO2 reps came in at 102% of FTP instead of 112%. The sweet spot session held 85% instead of 90%. The long ride finished 20 minutes short.

Individually those are rounding errors. Repeated across every session for three months, they add up to a systematically weaker stimulus than the plan intended — which is what a plateau is. The cause is almost always accumulated fatigue: hard days too close together, poor sleep, a heavy stretch at work, or an easy day that was not easy.

The counterintuitive fix is to train less for a week. A real recovery week — half the hard work, easy rides kept easy — often produces a jump in the numbers that no amount of added intensity would have. That is the argument made at length in why fatigue management matters more than FTP gains. If the tiredness feels unusually severe or persistent, or arrives with symptoms beyond ordinary fatigue, it is worth raising with a medical professional rather than training through it.

The plateau may be in the test, not the fitness

Before accepting that a stall is real, check what produced the numbers. A ramp test done after a bad night, compared against a 20-minute test done fresh, will disagree by more than a season of honest training gains — the two protocols measure different things and reliably return different values. Comparing across them tells you nothing about fitness.

More importantly, FTP is a narrow measurement, and for an experienced rider on limited hours it is often the slowest-moving thing about their fitness. Improvements FTP will not show: holding the same power in hour three of a ride that used to fall apart at hour two; completing a fifth VO2 rep at a target you could previously only hold for four; heart rate settling faster after hard efforts; a lower heart rate at the same endurance power. Riders in that position have not stalled. They have outgrown the metric.

How to work out which one you have

Three checks, all doable in about ten minutes with your ride history:

1. Compare this month with four months ago. Same weekly hours? Same interval durations and targets? If yes, your load stopped rising and progression is the fix.
2. Look at the spread of your last 15 rides. If most sit in a narrow band around tempo, with few genuinely easy rides and few genuinely hard efforts, the distribution collapsed. Push the ends apart.
3. Check your last six quality sessions against target. If they were consistently under, you have a recovery problem, not a training problem — take the easy week before you change anything else.

Run them in that order. Two of the three often show something, and where they conflict, treat under-recovery first: adding progression on top of accumulated fatigue is the reliable way to turn a stall into a setback.

When the ceiling is real

Sometimes all three checks come back clean. Load has been progressing, the distribution is sound, sessions are hit at target, and the numbers are still flat. That happens, and it is worth saying plainly rather than selling a fix that does not exist: on a fixed number of weekly hours, fitness settles at a level, and after a few seasons you will be near it.

Three honest options at that point. Add hours, if your life genuinely has them — that is the only lever that reliably raises the ceiling. Change what you are optimising, toward durability and repeatability, which affect how your rides actually feel far more than a few watts of FTP. Or accept the level and hold it, which for a rider with a job and a family is a legitimate and often correct goal — the case for that is made in cycling fitness for busy professionals. What does not work is grinding harder against a ceiling using the same tools that built it.

How SmarterTraining thinks about this

Plateaus get blamed on the wrong thing because the evidence is spread across months of rides and nobody sits down to review it. Flat load and drifting easy-ride intensity are both obvious in aggregate and invisible day to day. SmarterTraining builds from your recent riding rather than from a fixed template, so progression keeps moving and easy days stay easy — which removes two of the four causes before they get a chance to compound.

If you are stalled right now, though, do the diagnosis by hand first. Knowing which cause you have is most of the fix.

Takeaway

Takeaway: A plateau is a diagnosis problem, not an effort problem. Check three things before changing anything — whether your load has actually risen in four months, whether easy and hard days have collapsed into the same tempo band, and whether your recent quality sessions were hit at target. Fix under-recovery first, progression second, and stop comparing FTP numbers that came from different tests.