Wearables: What Data Matters (And What's Just Noise)

The Data Overload Problem

Last week, an athlete sent me a panicked message: "My recovery score is 32, my HRV dropped 15ms, my training load is red, and my VO2max estimate went down. Should I rest?"

He felt fine. His workout the day before was strong. But his watch told him he was broken.

This is the wearables paradox: we have more biometric data than ever, but less clarity about what to do with it. As both a coach and someone who races competitively in the 45-49 age group, I've learned which metrics drive decisions and which create unnecessary anxiety.

Let's cut through the noise.

Heart Rate Variability: The Gold Standard (With Caveats)

Heart Rate Variability (HRV) measures the variation in time between heartbeats. Higher variability generally indicates better autonomic nervous system balance and recovery capacity. Research consistently shows HRV responds to training stress, sleep quality, illness, and psychological stress (Plews et al., 2013).

What Makes HRV Useful

HRV shines when you track trends over time, not single-day snapshots. A study of elite runners found that tracking 7-day rolling HRV averages predicted optimal training readiness better than daily values (Plews et al., 2014). When your 7-day average drops 10-15% below your 2-month baseline, that's a signal worth noting.

The HRV Reality Check

Here's what undermines HRV's value:

• Measurement inconsistency: Time of day, body position, breathing pattern, and even room temperature affect readings
• Individual variability: Your "normal" might be 45ms while another athlete's is 95ms—neither is better
• Alcohol and late meals: A single glass of wine can tank HRV for 24-48 hours without meaningful training implications
• Nocturnal measurements: Wrist-based overnight HRV often shows artifacts from movement and measurement errors

My protocol: I have athletes measure HRV first thing in the morning, seated, same spot, 2-3 minutes of quiet breathing. We look at weekly trends, not daily swings. A single low reading means nothing. A declining trend over 5-7 days triggers a conversation.

Resting Heart Rate: Simple and Reliable

Resting Heart Rate (RHR) is underrated. It's less sexy than HRV but often more actionable. An elevated RHR—5-10 beats above your normal baseline—is a clear physiological red flag.

Research on overtraining syndrome consistently identifies elevated RHR as an early warning sign (Meeusen et al., 2013). It's particularly useful because it's harder to game than subjective wellness surveys.

When RHR Matters Most

• Illness detection: RHR often spikes 12-24 hours before you feel sick
• Heat adaptation tracking: RHR drops as you adapt to training in heat
• Overtraining monitoring: Persistent elevation (7+ days) signals accumulated fatigue

My protocol: Check RHR trend over 7 days. If it's up 5+ beats without explanation (heat, stress, illness), we modify intensity. I don't panic over a single elevated reading.

Training Load Metrics: Useful Framework, Flawed Execution

Garmin's Training Load, Polar's Cardio Load, and similar metrics attempt to quantify training stress using session RPE × duration or TRIMP (Training Impulse) models. The concept is sound—these models have research backing dating to Banister's fitness-fatigue model (Busso, 2003).

The Problems

1. They only know what your watch records: A stressful work presentation or poor sleep aren't factored in
2. Algorithm opacity: You can't verify or adjust the calculations
3. One-size-fits-all zones: Generic heart rate zones miss individual physiology
4. Lag time: They react to accumulated stress slowly, missing acute overload

My take: Use training load as a sanity check, not a prescription. If your watch says you've done three weeks of progressive load and you feel great, trust your body. If it's screaming red but you followed a sensible plan, investigate specific fatigue sources rather than blindly cutting volume.

Sleep Tracking: Directionally Helpful

Wrist-based sleep tracking isn't accurate enough for clinical sleep research, but it's good enough for pattern recognition (de Zambotti et al., 2019). I care less about whether you got exactly 7h 23m of sleep and more about:

• Consistency: Do you go to bed at wildly different times?
• Trends: Are you averaging 6 hours when you need 8?
• Wake episodes: Frequent nighttime waking suggests stress or environmental issues

The sleep stage trap: Your watch's REM vs. deep sleep breakdown isn't reliable enough to optimize. Focus on total sleep time and subjective sleep quality instead.

What I Actually Ignore

VO2max Estimates

Watch-based VO2max estimates use algorithms based on heart rate response to pace. They're directionally useful over months but wildly variable week-to-week. Factors like heat, fatigue, and heart rate drift skew readings.

If you want real VO2max data, get lab tested. Otherwise, track race performance—that's the VO2max proxy that actually matters.

Body Battery / Recovery Scores

These proprietary algorithms combine HRV, sleep, stress, and activity into a single number. The problem? You can't separate signal from noise. Is your low recovery score from hard training, poor sleep, or the algorithm having a bad day?

I'd rather look at the individual inputs—HRV trend, sleep duration, subjective energy—than trust a black-box composite score.

Acute Training Load Ratios

The "chronic training load / acute training load" ratio popularized by some platforms has weak predictive value for injury in recent research (Menaspà, 2017). It oversimplifies load-response relationships and ignores individual resilience factors.

The Metrics That Matter: My Hierarchy

Here's what I track with athletes, in order of importance:

1. Subjective feel: How do you feel? Rate your energy, motivation, and muscle soreness. This beats any algorithm.
2. 7-day HRV trend: Is your rolling average declining?
3. Resting heart rate trend: Any sustained elevation?
4. Sleep duration pattern: Are you consistently getting enough?
5. Workout execution: Did you hit your prescribed paces? Was it harder than expected?
6. Training load context: Does accumulated volume align with your capacity?

Notice what's missing: single-day recovery scores, VO2max estimates, sleep stages, body battery readings.

The Integration Problem

The biggest wearables issue isn't the data—it's that every platform uses proprietary metrics you can't compare or combine. Garmin's HRV isn't directly comparable to Whoop's. Training Stress Score doesn't translate to Polar's system.

This creates vendor lock-in and makes it difficult to find your own signal in the noise.

How to Actually Use Your Wearable

1. Establish Your Baseline

Track metrics for 4-6 weeks during normal training. Calculate your averages. That's your reference point.

2. Focus on Trends, Not Values

A 10% deviation from baseline over 5-7 days is meaningful. A single bad reading is noise.

3. Triangulate With Feel

If your watch says rest but you feel strong, investigate why. If your watch says go but you feel wrecked, trust your body.

4. Use Data to Confirm, Not Dictate

Wearables should validate your intuition, not replace it. You're training to improve performance, not optimize device metrics.

5. Take Regular Tech Breaks

Every 4-6 weeks, ignore your watch data for a week. Run by feel. You'll recalibrate your internal monitoring system—the most sophisticated biofeedback tool you have.

The Data I Track on Myself

As a competitive masters athlete, here's my personal dashboard:

• Morning HRV: 3x weekly (Monday, Wednesday, Friday), tracked manually with chest strap
• Resting HR: Daily, automatically from watch
• Sleep duration: Glance at total time, ignore stages
• Training log: Workout feel rating (1-10), notes on energy and execution
• Weekly volume: Total miles and intensity distribution

That's it. I check my "recovery score" approximately never.

This minimalist approach lets me train by athlete-feel informed by data, not dictated by it. When I'm preparing for a 3000m race, I need to know if I'm adapting to intervals, not what my VO2max estimate changed to.

The Bottom Line

Wearables are powerful tools when you know what to track and how to interpret it. But more data doesn't equal better training. Focus on metrics with research support (HRV trends, RHR, sleep duration), use them to validate your subjective experience, and ignore the proprietary scores designed to keep you checking your app.

Your body is the ultimate wearable. The watch is just a second opinion.

References

Busso, T. (2003). Variable dose-response relationship between exercise training and performance. Medicine & Science in Sports & Exercise, 35(7), 1188-1195.

de Zambotti, M., Cellini, N., Goldstone, A., Colrain, I. M., & Baker, F. C. (2019). Wearable sleep technology in clinical and research settings. Medicine and Science in Sports and Exercise, 51(7), 1538-1557.

Meeusen, R., Duclos, M., Foster, C., Fry, A., Gleeson, M., Nieman, D., ... & Urhausen, A. (2013). Prevention, diagnosis, and treatment of the overtraining syndrome: joint consensus statement of the European College of Sport Science and the American College of Sports Medicine. Medicine & Science in Sports & Exercise, 45(1), 186-205.

Menaspà, P. (2017). Are rolling averages a good way to assess training load for injury prevention? British Journal of Sports Medicine, 51(7), 618-619.

Plews, D. J., Laursen, P. B., Kilding, A. E., & Buchheit, M. (2013). Evaluating training adaptation with heart-rate measures: a methodological comparison. International Journal of Sports Physiology and Performance, 8(6), 688-691.

Plews, D. J., Laursen, P. B., Kilding, A. E., & Buchheit, M. (2014). Heart rate variability and training intensity distribution in elite rowers. International Journal of Sports Physiology and Performance, 9(6), 1026-1032.