There is a Norwegian coaching line about the athlete who keeps digging up the carrot to check whether it has grown -- testing max on every session, chasing a personal best in training, proving fitness instead of building it. The claim behind it is that a steady, predictable baseline beats a program of dramatic peaks and crashes. Half of that is right, but the way it usually gets told sets up a fight that the evidence says doesn't exist. The steady baseline and the classic recovery week aren't rivals. They solve different problems, and which one you need is decided by your sport and your physiology, not your ideology.
The Simple Version
"Consistency over peaks" is real advice wrapped around a false dichotomy. What actually predicts success is not the shape of your training -- linear versus peaked -- but adherence: the athletes who complete their weeks win, and the ones who keep getting hurt or sick don't. Steadiness protects that adherence. But steadiness at the month level is not the same as monotony at the week level, which is harmful. And a predictable baseline does not abolish recovery weeks -- high-impact sports run flat because bone and tendon cap the volume, while low-impact sports pile up so many hours they genuinely need the deload. The honest rule: keep the baseline boringly consistent, keep individual sessions submaximal so you can train again tomorrow, and unload when your body -- not your calendar alone -- says so.
How It Works
The Fight That Isn't There
Adherence Is the Real Variable
Before arguing about linear versus periodized, look at what actually correlates with results. Raysmith and Drew followed 33 elite track and field athletes across five years and 76 seasons. The athletes who completed more than 80% of their planned training weeks were seven times more likely to hit their goal. Every week lost or modified to injury or illness cut the odds of success by about a quarter (OR 0.74). Training availability alone accounted for 86% of successful seasons.
That reframes the whole debate. The value of a steady baseline is not some special adaptation the linear curve produces. It is that a predictable, controlled load keeps you healthy and present, week after week, so the weeks add up. A peak-and-crash strategy that produces one brilliant block and then a tendinopathy has already lost, because the math of missed weeks swamps the benefit of the peak. Consistency wins by not losing.
Consistency Is Not Monotony
Here is the trap the slogan can lead you into. "Steady" at the level of months -- accumulating volume without long gaps -- is exactly what you want. "Steady" at the level of days -- every session the same moderate-hard grind -- is dangerous.
Foster quantified this decades ago with two metrics. Monotony is your daily mean load divided by its standard deviation across the week: do the same thing every day and the standard deviation collapses and monotony spikes. Strain is load multiplied by monotony. In his athletes, illnesses clustered when individuals crossed their personal strain threshold -- and it was the monotony, the absence of genuinely easy days between hard ones, that drove it.
So a consistent baseline has to be internally varied: truly easy days easy, hard days hard, and the hard ones kept submaximal. A flat line of grey-zone efforts is the worst of both worlds -- too hard to recover from, too easy to drive adaptation, and monotonous enough to make you sick.
Why the Deload Question Has Two Answers
Now the reconciliation with the recovery-week idea, which lives in its own article. Whether you need a scheduled deload is not a matter of taste; it depends on what limits your volume.
The Norwegian coaching synthesis by Tonnessen and colleagues -- practice from coaches whose athletes won over 370 medals -- shows the split. In high-impact sports like distance running, annual volume is capped near 600-700 hours by what bone and tendon can absorb. Runners are already training at a mechanical ceiling, so their weeks run relatively flat and they don't need to manufacture a deload -- the sport enforces one. In low-impact sports like cycling, skiing and rowing, athletes accumulate 1000-1200+ hours precisely because there is no pounding to break them, and that volume drives such deep metabolic and hormonal fatigue that scheduled recovery weeks become physiologically necessary.
Same principle, opposite prescription. "Linear, no deep deloads" is right where tissue is the limiter. "Load then unload" is right where systemic fatigue is the limiter. The recovery-week article and this one are describing two ends of one continuum, not disagreeing.
It Also Depends on You
Fiber type adds a second axis. Bellinger's runners went through an identical overload block; the ones with a faster-twitch profile tipped into non-functional overreaching -- performance dropping instead of rebounding -- while the slow-twitch runners absorbed it and supercompensated. Lievens showed the mechanism: after all-out efforts, fast-twitch athletes lost 61% of their power versus 41%, and hadn't recovered five hours later versus twenty minutes. A deliberate peak-and-crash block is a legitimate tool for a diesel and a trip to overtraining for a fast-twitch athlete. There is no universal answer because there is no universal athlete.
The Carrot and the Recovery Tax
Which brings us back to the carrot. Why not test yourself often? Because a maximal effort carries a recovery tax the average hides. Seiler measured how fast the autonomic nervous system rebounds: after low-intensity work below the first threshold -- even 60 to 120 minutes of it -- HRV was back to baseline in 5 to 10 minutes. Cross the threshold and recovery jumped to around 30 minutes; go to real max and, in less-trained athletes, well over an hour. The cost isn't in the duration, it's in the intensity spike.
Every time you pull the carrot -- an all-out test, a training PB, one more rep to failure -- you dig an autonomic and neuromuscular hole that costs 48-72 hours to fill, during which you can't do quality work. Leave a couple of reps in reserve and the system rebounds by tomorrow, so you can train again. Two controlled submaximal sessions accumulate far more time in the productive zone than one heroic session followed by forced rest. That is the actual engine behind the Norwegian double-threshold day, and it is why "don't test max" is training advice, not just poetry.
Example
Example: Two Eight-Week Blocks, Same Average Load
Two amateurs carry the same starting fitness and average the same weekly load over eight weeks. One holds a steady baseline; the other rides a 3:1 wave.
| Steady baseline | 3:1 peaks and valleys | |
|---|---|---|
| Week structure | Even load every week | 3 build weeks, 1 deload, repeated |
| Acute:chronic load ratio | Stays in the safe 0.8-1.3 band | Spikes on peak weeks, dips on deload |
| Injury/illness exposure | Low and predictable | Higher on the peak weeks |
| Who it suits | High-impact sport, fast-twitch, amateurs early on | Low-impact sport, slow-twitch, high volume |
Both can reach a similar average chronic load. The difference is not the destination but the risk taken to get there. The steady rider keeps their acute-to-chronic ratio in the safe zone the whole time; the peaking rider spends the build weeks with an elevated ratio, which is where injuries and illnesses concentrate -- and, per Raysmith and Drew, one forced-off week can erase the block's gain.
The point of the example is not that steady wins. It's that peaking is a bet: you accept higher risk on the build weeks in exchange for a supercompensation you may or may not tolerate. If you're a slow-twitch rower with 15 hours a week and good recovery markers, it's often a bet worth making. If you're a fast-twitch runner squeezing in six hours around a job, the steady baseline gets you to the same average load without the weeks you can't afford to lose. Choose the structure that protects your adherence, not the one that sounds most hardcore.
Practical Rules
Practical Rules
-
Protect adherence above all. The single best predictor of hitting your goal is completing your weeks. A plan you can execute consistently at 90% beats a brilliant plan you complete at 60% because it keeps breaking you. Judge every hard session by whether it threatens next week, not just today.
-
Keep the baseline consistent but not monotonous. Steady month-to-month volume, yes; identical grey-zone sessions day-to-day, no. Make easy days genuinely easy and hard days clearly hard, and keep the hard ones submaximal. That variation within the week is what keeps monotony -- and its illness risk -- down.
-
Don't pull the carrot. Stop turning sessions into tests. Ride or run the planned intensity, not your ego or your training-partner's pace. A max effort costs 48-72 hours of quality you then can't do; two controlled sessions in that window build more fitness than one heroic one plus forced rest.
-
Test fitness rarely and on purpose. You need occasional benchmarks to know you're progressing -- but a formal FTP or threshold test is a deliberate, scheduled event a few times a season, not something you drift into on a Tuesday because you felt good. Measuring progress and destroying it look identical in the moment.
-
Decide your deload need from your limiter, not dogma. If your sport pounds your tissues (running, high-impact) and your volume is already capped, a flat baseline may be all the recovery you need. If you're piling up big low-impact hours (cycling, swimming, skiing), you almost certainly need scheduled recovery weeks -- this is where the recovery-week guidance fully applies. "Norwegians don't deload" is a misread; it's sport-specific.
-
Unload on signals, not only the calendar. A fixed 3:1 is a fine default, but the evidence supports auto-regulation too: when morning HRV, resting heart rate, sleep or mood drop, or your power at a familiar effort sags, bring the deload forward. HRV-guided runners matched or beat a fixed plan. Use the calendar as the backstop and your objective markers as the trigger.
-
When life interrupts, shrink -- don't skip. A missed week is expensive. A short maintenance session -- even a third of the usual volume with the intensity kept -- holds fitness and, crucially, avoids the injury-prone spike of trying to make it all up next week. Consistency is a chain; protect the links.
Evidence Base
Evidence Base
The adherence finding is the strongest thing here, and it's a proper prospective study. Raysmith and Drew (2016) tracked real athletes over five years and 76 seasons, and the effect is large and specific: 7x, OR 0.74, 86% of successful seasons explained by availability. It is 33 athletes in one sport, so the exact numbers shouldn't be treated as universal, but the direction -- health and consistency beat heroics -- is about as solid as this field offers.
The monotony framework is old, observational, but foundational. Foster (1998) is 25 athletes and correlational, not a controlled trial, so monotony and strain are best read as useful monitoring tools rather than proven causes. Still, the core insight -- that unvarying load, not just high load, drives illness -- has held up and directly qualifies the "just be consistent" message.
The recovery-cost data are clean and mechanistic. Seiler (2007) on autonomic recovery and Lievens (2020) on fiber-type recovery both show, from different angles, that maximal intensity is disproportionately expensive and that the expense varies wildly between athletes. These are small studies -- treat the specific minutes and percentages as indicative -- but they give the "don't test max" advice a real physiological basis rather than a folk one.
The reconciliation with recovery weeks rests partly on practice, not trial. Tonnessen (2024) is a qualitative synthesis of elite coaching (level C/D), not a randomized comparison, and the specific "reduce volume 25-35% every 3-4 weeks" detail comes from coach reports in the full text rather than a controlled experiment. It is credible best-practice, but it is practice. The deeper point -- that impact load determines whether you need a scheduled deload -- is mechanistically sound and is why this article and the recovery-week article don't contradict.
Auto-regulation has actual trial support. Vesterinen (2016) and subsequent HRV-guided training studies found that steering daily intensity by morning HRV performed at least as well as a fixed plan, which is what licenses "unload on signals, not only the calendar." The samples are small and recreational, so it's a supported option, not a mandate.
What's genuinely missing: the head-to-head. There is no long-term randomized controlled trial pitting a purely linear baseline against a 3:1 periodized plan in matched athletes -- you cannot make elites abandon their methods for a study. So the central claim of this article is deliberately modest: not "linear beats periodized," but "the choice is set by your sport and physiology, adherence matters more than either, and the two approaches are compatible." Two limitations run throughout: the recovery and fiber-type research is largely on men, and the whole evidence base leans on observation and mechanism rather than the controlled trial that will probably never be run.