Why Your FTP Plateaus After Year Two
5 min read
FTP often stalls when stimulus, recovery, or testing drift. Learn how to diagnose the limiter and apply one clear correction this week.
On this page
Photo by Oleg Kukharuk on Unsplash.
FTP often stalls when the training system around you drifts, not because your ceiling is fixed.
This refresh keeps the original promise: explain why FTP progress slows after a long run of gains, then give you one next move. Direct evidence for a fixed “year two” switch is not established here, so treat the timing as a common coaching pattern, not a hard biological rule.
A plateau is not one verdict. It is often a mismatch between the work you repeat and the change you want next.
The first cause is stimulus monotony. If most weeks feel alike, the same rides may no longer give a strong enough training signal.
The second cause is hidden fatigue. Your threshold did not disappear; your recovery inputs shifted, so the output dropped.
The third cause is a weak high-end signal. If you rarely ride well above threshold, your FTP work may lack support from harder power ranges.
The fourth cause is test noise. Pacing, heat, device setup, and motivation can move the number even when your actual fitness is steady.
This is why an FTP number needs context. Durability beyond one FTP test often tells a truer story than one fresh, short effort.
If your number keeps drifting, also check the method behind it. A clean threshold testing process reduces false alarms before you change the plan.
Check whether your last four weeks looked too similar.
Compare hard-session quality before judging FTP alone.
Assume fatigue first if power falls while effort rises.
Review test setup before changing training zones.
Choose one likely limiter, then test one precise correction for the next block.
In N+One terms: the limiter lives in one subsystem, so diagnose it before you add more load.
Photo by Munbaik Cycling Clothing on Unsplash.
Before you rebuild the plan, ask whether the data are clean. A poor fan setup indoors or a loose power-meter routine can look like lost fitness.
Testing errors compound over time because small changes become the new baseline. If the baseline is wrong, every zone built from it is wrong too.
Start with repeatability. Use the same bike, power source, warm-up, route or trainer mode, and pacing plan whenever you compare FTP efforts.
Power data also need basic care. Accurate power-meter setup is not glamorous, but it keeps your decisions tied to the work you did.
If you use modeled FTP, treat it as a live estimate, not a moral score. Why FTP estimates move can help you read changes without overreacting.
A true plateau shows up across similar sessions, not just one hard day. Look for the same pattern in power, heart rate, and RPE.
Use the same test setup each time.
Check power-meter zero offset or calibration routine.
Compare like sessions with like sessions.
Log RPE beside power and heart rate.
A true plateau often reflects a mismatch between stimulus and recovery, not a sudden loss of fitness.
Data analysis is free, forever. The Dynamic Coach is Pro. Connected to Garmin, Strava, Whoop, and intervals.icu.
Use two weeks to find the likely limiter. Keep the checks simple, because messy tests add more doubt than they remove.
First, repeat a controlled sub-threshold or threshold-style session you know well. If RPE climbs fast or heart rate drifts more than usual, fatigue may be masking fitness.
Second, test hard-repeat quality on a separate day. If your later repeats fade badly, your high-end repeatability may need a fresh signal.
Third, hold training load steady and watch recovery for several days. Poor sleep, high strain, and stale legs point toward recovery, not a missing work ethic.
This late-season window is a good time to run those checks. Shorter daylight and race fatigue can lower readiness even when your planned workouts look sensible.
If your events are done, avoid panic testing. A short diagnostic block gives cleaner feedback than chasing one more peak with tired legs.
Repeat one known benchmark session.
Do one hard-repeat session on a fresh day.
Track sleep, resting heart rate, and freshness.
Do not add load during the check window.
Once the pattern is clear, make one change. Changing volume, intensity, fueling, and testing all at once hides the cause.
If fatigue is the limiter, keep intensity but trim total work for a short block. The goal is to let fitness show, not to detrain yourself.
If high-end repeatability is weak, add a small dose of hard work. Keep the rest of the week easy enough that those sessions stay sharp.
If monotony is the issue, stop stacking the same middle work. Use clearer contrast between easy aerobic rides and focused hard sessions.
Riders who lean on sweet spot can still use it well, but not as the only tool. When sweet spot fits depends on the limiter and the season.
If you are time-limited, do not fill every open slot with hard work. A busy-rider training structure still needs recovery space.
Recovery-limited: cut weekly volume for one short block.
High-end limited: add hard repeats, not more threshold.
Monotony-limited: split easy days and hard days clearly.
Time-limited: protect quality before adding sessions.
Your next move is one lever, held long enough to see a clean response.
In N+One terms: keep the useful stress, cut the noise, and let the next test answer one question.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Maximize Performance with Cycling Strength Training — Learn how cyclists should use strength training: two focused weekly sessions, clear exercise choices, smart timing, and simple signs to adjust before...
- Adaptive Training Plans: The Science That Boosts Cycling Performance — Adaptive training plans use real-time data (power, HRV, sleep, TSB) and decision algorithms to deliver the right stimulus at the right time. Learn th...
- Power Profile Analysis: Find Your Strengths — Sprinter, Climber, Pursuer, or Time Trialist — Learn how to build and interpret a cycling power profile (MMP across durations), identify your phenotype and limiters, and turn that insight into foc...
FTP is useful, but it is not the whole performance story. Many riders can hit a number fresh yet fade when the ride gets long.
That matters when autumn goals shift from racing into base work. You may need steadier aerobic work before the next threshold jump appears.
Durability asks a different question: what power can you hold after real riding has already taken a cost? That question often explains race gaps better than a single test.
If long rides show late-session fade, add steady aerobic work before more threshold stress. Holding power after long work is a skill you can train.
Use FTP as the anchor, then read it beside repeatability and long-ride power. A higher number that falls apart late may not solve your race problem.
The first backfire is adding more threshold work by default. If the body has adapted to that stress, more of it can deepen the rut.
The second backfire is testing too often. Frequent testing adds stress and turns normal day-to-day swings into a false fitness story.
The third backfire is chasing training load without asking what power you are building. Load is context, not the goal.
The fourth backfire is treating a plateau as a character flaw. Your job is not to prove toughness; it is to fix the system input that moved.
If repeated hard days keep failing, the issue may be repeatability, not grit. Training repeated hard efforts works best when the easy days are truly easy.
Do not add threshold by reflex.
Do not retest every few days.
Do not chase load as the main score.
Do not change every variable at once.
Week 0: run one known threshold-style benchmark and one hard-repeat session on separate days. Keep recovery notes for the whole week.
If recovery-limited, keep intensity but cut weekly volume for one to two weeks. Add one full rest day and keep easy rides easy.
If high-end limited, replace two low-priority rides with short hard-repeat sessions. Keep one long aerobic ride and stop intervals when quality falls.
If monotony-limited, replace one familiar threshold ride with progressive intervals. Add contrast by making easy days clearly easy.
If external constraints seem likely, keep claims narrow and seek qualified help for nutrition, weight, or health issues. Track only small, clear changes.
After three weeks, repeat the same benchmark session. If the signal is better, continue the block; if not, switch only one lever for the next block.
FTP often stalls when the training system around you drifts. Clean up the test, identify the limiter, change one lever, and reassess before you add more work.
No exact timing is proven here. Many riders notice slower gains after a long period of steady training, but the better question is which input stopped working.
If power is falling while effort feels high, make recovery the first correction. Keep key intensity, cut non-essential volume for a short block, then retest the same session.
Sometimes, but only if sweet spot is the missing useful stress. If your weeks already sit near the same middle intensity, add contrast instead.
Check the test setup before changing the plan. Pacing, power-meter routine, heat, sleep, and motivation can all shift one result.