The Best Data Point We Have

Garmin on the wrist. Power meter on the pedals. Pace alerts buzzing every quarter mile. Heart rate trending on a graph we'll analyze for twenty minutes tonight. The data is everywhere - and for many of you, it might be quietly becoming a crutch.

I'm not anti-data. I've built training systems around it. Zones exist for a reason. They give us a shared language for effort, a repeatable target, a way to build fitness systematically. But there's a growing issue I see across athletes in most sports: they're disregarding how they feel and instead focusing just on the numbers. They treat missing a power target as a failed workout. And, of course, It isn't.

Data helps us set the target, our body runs the session. Take a set for the bike like this:

5 x (6 min at (Zone 4 / Threshold / RPE 7-8), 3 min Easy)

The power range gives us a ceiling and a floor. But what happens on the day our legs are carrying last week's fatigue, we slept poorly, or the heat index is ten degrees higher than Tuesday? The wattage won't come. If we are overly data-dependent, we'll either blow up chasing the number or mentally abandon the session.

The answer? If we cannot maintain the prescribed power range, we can default to RPE 7-8 out of 10. Hard, controlled, sustainable - without the number attached. The physiological stimulus we're after is still accessible. We're still doing the work. We're just using the body we have today, not the body we had last Thursday.

That's not a compromise. That's smart training.

Ask an athlete how their ride felt and they'll tell you what their power file said. The perceived exertion conversation - the one that used to happen between a brain and a body - now routes through a device first.

On race day, when our GPS drifts, our power meter battery dies at mile 30, or our watch loses signal mid-open water swim - our data goes dark. Quite a few of us may go with it!

Racing is a feel-based sport. Data helps us execute pre-planned strategy - even more so in longer events. But if it's an off day, or the data isn't working, we've got to adjust and go to RPE. Additionally, if we feel better than expected, we may opt to adjust the plan by taking some risks. Regardless, RPE only works as a reliable tool if we've trained it like one.

So when an athlete isn't hitting the "numbers" in that swim, bike or run, we have the conversation on what to do. Once I get that buy-in, athletes learn that successful session aren't always about hitting the pre-planned numbers.

This is the skill. And it's the same skill that lets us execute the RPE fallback in a structured set without guessing. Self-awareness isn't soft. It's the mechanism that keeps our training productive on bad days and your racing intact when the tech fails or we feel fantastic.

Noticing how breathing changes across effort zones, recognizing when fatigue is accumulating versus when legs are simply warming up, distinguishing discomfort that signals adaptation from discomfort that signals breakdown - all of it sharpens the internal calibration we rely on when the data isn't enough.

And the data will still be there.

And the data will still be there. The power meter isn't going anywhere. Zones remain the framework. But the athlete who can hit the intent of a threshold set on a bad day - using nothing but internal calibration - is the athlete who races consistently, not just when conditions cooperate. And it may just be the athlete who accurately assesses feeling great in a race, takes a chance and has a breakout day.

The best data point we have is the one we were born with.

Gratefully,

Mark

Team MPI