Overtraining vs undertraining: the two-sided risk nobody talks about.

Wearables are cautious by default. They never tell you to train harder. Every yellow score, every low readiness number, every recovery alert pushes in one direction: do less.

Coaches and training plans are aggressive by default. They assume you can execute what’s written. The plan says 5×1000m at threshold, so you do 5×1000m at threshold. It doesn’t know you slept four hours and your hamstring is tight.

Neither approach protects both edges. One makes you cautious. The other makes you reckless. And both edges are equally dangerous to your season.

This is the edge everyone talks about. Burnout. Illness. Injury. Forced time off.

The session you should have skipped. The build week you pushed through when your body was begging for adaptation. The niggle you ignored because the plan said “key workout.”

Overtraining syndrome is rare in recreational athletes. But overreaching without adequate recovery is common. The cost is typically 1–3 weeks of forced rest, a missed race, or a nagging injury that lingers for months.

Most wearables are built to catch this edge. That’s good. But it’s only half the problem.

This is the edge nobody talks about. Plateau. Missed fitness. Arriving to race day underprepared.

The session you almost skipped because your Oura showed yellow, but it was just a bad night’s sleep. The interval workout you downgraded to easy because WHOOP said 42% recovery. The meh Monday that would have cleared with a warmup 4 out of 5 times.

Over a 16-week training block, skipping one session per week that you could have completed costs you roughly 15% of your training stimulus. That’s the difference between a PR and a plateau.

No wearable will ever tell you: “You’re being too cautious. Train harder.” That warning doesn’t exist. The undertraining risk is invisible.

Build-week fatigue isn’t overtraining. It’s the point. You accumulate load deliberately, then recover. Feeling tired during a build week is the plan working.

Taper flatness isn’t illness. Reducing volume makes athletes feel sluggish, heavy, and anxious. HRV often improves while feel gets worse. This is normal.

Recovery weeks aren’t weakness. Dropping volume by 30–40% lets adaptation happen. The fitness you built during the build weeks doesn’t appear until you rest.

The right call depends on where you are in the plan. A yellow readiness score during a build week means something completely different than the same score during a recovery week. Most tools don’t know the difference. They show you the same number regardless of context.

We catch the session you should skip AND the session you almost skipped but shouldn’t have.

• ·When signals converge on fatigue (feel bad, data bad, multi-day trend), we tell you to rest. No ambiguity.
• ·When signals conflict (feel fine, data dipped, one-off cause), we tell you to train. Often with a warmup gate: start easy, check in after 15 minutes.
• ·When you're in a build phase and fatigue is expected, we adjust the threshold. Tired is the plan working. Broken is not.
• ·When you're tapering and feel flat, we reassure instead of alarming. The sluggishness is temporary. Race fitness is loading.

Both edges matter. Protecting only one is worse than protecting neither, because it creates a false sense of safety while the other edge quietly erodes your season.