Training Plateaus: The Five Causes and How to Diagnose Them

A plateau is the training state where progress measured on the main lifts stalls for longer than a normal accumulation of fatigue would explain. Two weeks of flat numbers is not a plateau; it is a deload coming. Four to eight weeks of flat or declining numbers, across multiple lifts, with no injury, is a plateau. The reflexive response to a plateau is to change the program, and that is wrong about 60-70% of the time. Most plateaus are caused by factors the program cannot fix: insufficient recovery, technique breakdown, nutritional deficits, or a mismatch between the lifter's training age and the programming style.

Cause one is recovery debt. Sleep has slipped, life stress has climbed, the lifter has skipped two or three deloads in a row, or the volume has crept up without a corresponding increase in food and rest. The diagnostic markers are non-specific but cumulative: bar speed is slower at familiar weights, RPE has drifted up by half a point at the same weights, sleep feels less restorative, mood is flatter, and minor joint aches have appeared. The fix is a real deload — not a lighter week with the same schedule, but 50-60% of usual volume for 5-7 days, followed by a return to a slightly lower starting point than before the plateau. Most recovery-driven plateaus resolve within 2-3 weeks of proper recovery.

Cause two is technique drift. Under heavy load, technique slowly drifts away from its ideal form — the squat depth gets shallower, the bench arch flattens, the deadlift rounds. The lifter does not notice the drift because it happens across many sessions, but the leverage the drift costs is real. A squat that was hitting depth six months ago and now stops two inches high is not moving more weight because the range of motion has been cut. The diagnostic here is video — record one set per session for two weeks and compare against older footage. Fix technique at lighter weights for 2-4 weeks before returning to heavy loads.

Cause three is nutritional deficit. A plateau in a lifter who is undereating, undereating protein, or recently lost weight from a cut is a nutrition problem first and a programming problem second. The diagnostic is bodyweight stability on the scale (dropping weight during a strength phase is usually the signal) and protein intake logged over 2-3 days. If weight is dropping and lifts are stalling, the fix is calorie intake up to maintenance or small surplus, protein to 1.6-2.0 g/kg, and patience — nutritional recovery takes 2-4 weeks to show in strength numbers.

Cause four is training age mismatch. A lifter running a novice LP program at an intermediate level will stall, and the stall is the program, not the lifter. Similarly, an intermediate lifter running an advanced program with too much total volume will stall because recovery cannot keep up with the load. The diagnostic is the lifter's own history: how long have they been training, how much weekly volume has produced results in the past, and does the current program represent a step up or a step down in complexity from what has worked? The fix is usually to step down in programming complexity, not up. Most "stuck" intermediates are running programs designed for lifters with more training age.

Cause five is true neuromuscular plateau. After causes one through four have been ruled out, some plateaus really are programming adaptation problems — the lifter has accommodated to the stimulus, the overload principle is no longer being met, and a change is required. The fix is a genuine change in stimulus: new rep ranges, new exercise variations, a different periodization model. This is where programming variation (switching from 5x5 to 5/3/1, adding a DUP block, running a hypertrophy-focused cycle) does its real work. But this should be the last diagnostic reached, not the first.

The diagnostic sequence matters. Lifters who jump straight to programming changes often change programs while still carrying recovery debt or technique drift, and the new program stalls for the same reason. The honest sequence is: deload for two weeks and see if numbers return (rules out cause one), film a few working sets and compare to old video (rules out cause two), log nutrition for a week (rules out cause three), audit training history against programming style (rules out cause four), and only then consider a programming change (cause five). Most plateaus are resolved by the first three steps before the programming change is needed.