THE LONG EFFORT
Smarter training for real life.
ISSUE 01 / 2026-09-10
Your Watch Says Recover. You Feel Fine. Who Wins?
A key workout changed overnight. Here is how to follow, resize or move it without losing the week.
MAIN STORY
Thursday's threshold set has become a 45-minute recovery run. Sleep was poor, HRV is down and the app is worried. Your legs feel normal. This session gives the week its shape. What now?
You can follow the change or ignore it. Usually, there is a third option: make the session smaller. The app is reacting to the last few days. Your plan is trying to hold the week together. Before you choose, decide how much risk makes sense today and where the key session goes if it moves.
A low readiness score may change today's workout. It should not make the key session disappear from the week.
Why the recommendation and the week disagree
One bad score is just one bad score. HRV-guided adjustment looks promising, but it has not clearly beaten a fixed plan. Wearables miss things, and how you feel still matters. Normal legs are another piece of the picture.
Then add what the device may not know: the indoor ride that failed to sync, a work trip, yesterday's under-fueling, extra cross-training or broken nights with a sick child. The watch sees the data that reaches it. You know what happened around it.
DECISION TOOL
THE OVERRIDE CHECK
Before you accept or override the change, check four things:
SIGNAL - One odd reading, a repeated trend, or several signals agreeing? Was the measurement clean?
CONTEXT - How do your legs feel? What did the device miss - work, travel, fueling, family or cross-training?
CONSEQUENCE - Which mistake costs more today: the full session, a resized one, or moving it?
NEXT 72 HOURS - If the key work moves, where does it go? What stays easy so hard days do not stack up?
Start with the smallest change that still protects today and the week. If the score is an outlier, your legs feel normal and the warm-up is clean, try fewer reps or a lower target. You do not have to choose between the full session and the sofa.
Several warning signs, heavy legs, illness symptoms or a poor warm-up call for a bigger adjustment. Move the workout, make the next day easy and write down where the key work returns. Otherwise, the session can vanish and reappear as two hard days stacked together.
Often, resizing the session is enough. Whatever you choose, keep the rest of the week in view.
Pain, illness, unusual symptoms or safety concerns are not override puzzles. Stop and seek qualified medical or coaching help.
TRY THIS
Run a seven-day recommendation audit
For seven days, take one minute before each workout. Note the recommendation, how you feel from 1 to 5, and one thing the device may have missed. Choose follow, resize or move. Afterward, jot down session quality and how you felt the next morning. At the end of the week, look for one pattern. Did the watch catch fatigue before you did? Stop if pain, illness or unusual symptoms appear.
SIGNALS
FIVE FAST PROBLEMS
QUICK READS
Five familiar moments where the number looks more certain than the decision.
SIGNAL 01 / TRAINING STACK
One App for the Plan. Another for Everything Else.
One athlete planned workouts in Garmin and kept a spreadsheet because the week was easier to scan there. Others described similar stacks: one tool for the plan, another for analysis, another for the social side. Give each subscription a clear job. If two do the same job, ask which one actually changes a decision. One triathlete discovered their current training app could also handle indoor rides and cancelled another subscription. That is an easy piece of overlap to cut.
SIGNAL 02 / AI COACHING
Your AI Coach Just Told You What You Already Knew
You rode for 90 minutes. Heart rate was steady. Training load went up. You already know. You were there. Then the paid insight repeats those facts. Athletes in r/Garmin wanted patterns and useful next steps; one built a Garmin-to-Claude workflow instead. A useful insight points out something you missed, explains why it matters or helps with the next decision. If it only narrates the dashboard, the shorter version was already on the screen.
SIGNAL 03 / FTP
That FTP Jump Might Not Be Fitness
A Zwift rider's FTP moved from 77 W to more than 130 W after a connection problem was fixed. Elsewhere, athletes argued over whether a jump from 190 W to 274 W meant fitness, better test execution or a bad starting number. FTP is an estimate. Before changing every zone, ask whether the new test was comparable. Was the connection stable? Were the power source, calibration, cooling and pacing similar? If not, fix the setup and repeat the test.
SIGNAL 04 / FUELING
How Much Fuel Do You Actually Need?
A triathlete posted heart rate, intake, temperature and pacing after a failed 70.3. Experienced athletes still disagreed about the cause. One fueling number is never the whole plan. What works on a cool two-hour ride may fall apart four hours into a hot race - or your gut may reject it first. Start with credible guidance, practise under race-like conditions and record what you ate and drank. Then note your energy, stomach and pace. Automated estimates cannot replace individual advice from a qualified sports-nutrition professional.
SIGNAL 05 / ACTIVITY PROCESSING
Same Activity. Different Numbers.
One athlete opened the original activity file - the raw record saved by the device - after Garmin and Strava showed different moving times. It was one activity, but the platforms produced two versions of it. Strava says it may calculate moving time from GPS and speed thresholds, which can differ from the device's method. Start with the version on your device and ask which number matters. For pacing, stick with one device and method. If a best effort looks impossible, check the map before celebrating.
SOURCES & FURTHER READING
Company documentation and peer-reviewed reviews support the lead story. Reddit links document athlete experience and disagreement; they are not scientific proof.
LEAD STORY
Garmin Daily Suggested Workouts - Official inputs and multi-device behavior.
How to Use Adaptive Training - TrainerRoad performance, surveys and plan changes.
HRV-guided endurance training meta-analysis - Promising but mixed performance evidence.
Keeping Pace with Wearables - Umbrella review of consumer-wearable validity.
Monitoring the athlete training response - Subjective and objective monitoring review.
Does anyone actually do the daily suggested workout? - r/Garmin adherence and overrides.
11 months of following the daily suggestion - r/Garmin zone, sleep and parent context.
TRAINING STACK
Which training app are you using? - r/triathlon examples of overlapping tools and roles.
Triathlon training app - r/triathlon example of consolidating indoor training.
AI INSIGHTS
Connect+ isn't worth it - r/Garmin reports on shallow summaries.
Garmin Active Intelligence - r/Garmin requests for relevant, personal advice.
Connect+ AI insights so terrible I turned it off - r/Garmin repetition and a self-built Garmin-to-Claude workflow.
FTP
What is known about the FTP20 test related to cycling? - Peer-reviewed scoping review of reliability and comparability.
Zwift FTP Test - Official description of FTP tests as estimates used for workout targets.
FTP incredibly low - Newbie - r/Zwift connection issue and retest.
FTP 190 to 274 in 2 months - r/Zwift debate over fitness and test execution.
FUELING
Nutrition and Athletic Performance - Joint professional position on individualized food and fluid guidance.
Nutrition for Athletics - World Athletics consensus on practised, event-specific carbohydrate and hydration plans.
Practitioner guide to exercise-associated gastrointestinal symptoms - 2025 position statement on individual variability and gut training.
DNF'd my first 70.3 - post mortem - r/triathlon discussion of intake, pacing and conditions.
How do you fuel? - r/triathlon strategies and individual tolerance.
ACTIVITY PROCESSING
Moving Time, Speed, and Pace Calculations - Official Strava explanation of post-upload processing.
Ridiculous Best Efforts? - r/Strava impossible efforts and cleanup.
Garmin to Strava: Why is Moving Time different? - r/Strava analysis of an original FIT file.