Your Watch Is Lying to You

(And It's Costing You Race-Day Performance)

You trained hard. You've got the data to prove it. Your training calendar is full of green. Your long rides are logged, your threshold runs are ticked off, and you know your FTP to the nearest watt.

Then race day arrives — and you spend the whole bike leg staring at your wrist.

Sound familiar?

After 20-plus years of coaching age-group triathletes, I can tell you that watch dependency is one of the most widespread performance killers I see. And the frustrating thing? The athletes who suffer from it most are usually the ones who've done the most training. They've invested heavily in data — and on race day, they can't let go of it.

This article is for them. Maybe it's for you.

---

What Watch Dependency Actually Looks Like

It doesn't always look like obsession. It's usually subtle.

It's the athlete who sits up slightly on the bike because their power number crept 5 watts above target — even though they felt completely fine. It's the runner who backs off in the first mile of the run because their pace looks "too fast on paper," even though their legs are fresh and their breathing is controlled. It's the swimmer who ignores how good they feel off the wall because they glanced at their split and it didn't match the plan.

The watch has become the authority. Their own body — twenty weeks of training built into muscle and lungs and fitness — has become secondary.

That's watch dependency. And it's costing real time.

---

The Problem with Racing to Numbers

Here's the thing about pacing data: it tells you what's happening, not how you're coping with it.

A 4:45/km pace in mile one of a sprint run might be perfect for one athlete and reckless for another. 220 watts on the bike could be the ride of someone's life on a cool, flat course — or reckless overreach on a hot one. Context matters enormously. And your watch has no idea what context you're in.

Race day introduces variables your training numbers were never built to handle:

• Adrenaline — race-day adrenaline pushes your heart rate 5–10 beats above your training equivalent for the first 20–30 minutes. If you pace off heart rate early, you'll ride conservatively when you could be flying.
• Temperature and conditions — heat slows you; a tailwind inflates your numbers. Raw data lies in both directions.
• Competition — you can't programme in the effect of being surrounded by athletes working at 95% effort. It changes everything.
• Fitness peaks — your FTP from week 12 of your build isn't your FTP on race morning after a perfect taper. You are very likely fitter than your numbers suggest.

When you stare at the watch and react to every blip, you're reacting to incomplete information. When you race by feel — informed but not controlled by data — you're working with everything.

---

"But I'll Go Out Too Hard"

This is the objection I hear every time I raise this with an athlete. And it's valid. Going out too hard is a real risk — I've seen it destroy races more times than I can count.

But here's the distinction: I'm not telling you to ignore your watch entirely. I'm telling you to stop racing it.

There's a meaningful difference between checking your power every 30 seconds and adjusting your effort after every blip — and glancing at your average pace at mile 3 to confirm you're in the right ballpark before getting your head back in the race.

One is data-informed racing. The other is data-controlled racing. The first produces good performances. The second produces safe, average ones.

The goal on race day is to race the race in front of you. Use your watch as a sanity check — a brief reference point at defined intervals — not as a real-time instruction manual.

---

What Racing by Feel Actually Means

Racing by feel isn't guesswork. It's a skill — and like any skill, it's built in training.

The athletes who do this best have spent months learning what a sustainable effort feels like versus a blowup effort. They know what their legs feel like at 90% versus 95%. They know what their breathing sounds like when they're in the zone versus when they're creeping into the red.

That knowledge doesn't come from staring at a screen. It comes from training sessions where you deliberately practise effort awareness: tempo runs without a pace target, bike intervals where you lock in the effort before you look at the power, open-water sessions where you swim to feel and check the Garmin afterwards.

On the bike

Set your watch to show 30-second average power, not instant power. Then look at it less than you think you should — every 10–15 minutes is enough. In between, ride to feel. Notice what "comfortably hard" actually feels like at race pace, because that's the target.

On the run

Ignore the first kilometre's pace data entirely. It will always be faster than your target — adrenaline, crowd energy, fresh legs. Let it be fast. Settle into your effort from kilometre 2 onwards. Run to breathing effort first, pace data second. For Half IRONMAN (70.3) racing especially, your run should build — working hardest in the final third, not the first.

On the swim

Put the watch on, start it, and forget it exists. Your swim should be effort-controlled from the gun. The split at T1 is interesting data. It's not something you can meaningfully adjust in the water.

---

The Deeper Issue: What Are You Actually Afraid Of?

Watch dependency is usually about fear.

Fear of going too hard. Fear of blowing up in front of people you know. Fear of making a mistake after months of preparation. Fear of not being good enough — and having the data expose it.

The watch feels like protection. If you race to your target numbers and it goes wrong, at least you did everything right. If you back your own feel and it goes wrong, that's on you.

But here's what I've seen consistently across 20 years of coaching age-groupers: athletes who race with conviction — who trust their training and back themselves on the day — perform better than athletes who race carefully. Not always. Not in every race. But significantly, consistently, more often than not.

The watch doesn't give you conviction. Only you can do that.

---

A Simple Race-Day Pacing Framework

I'm not going to tell you to leave the watch at home. But try this in your next race:

Before the race: Set three effort targets — swim (hard but controlled), bike (comfortably hard — you should be able to produce short sentences if you had to), and run (build through the race, nothing left at the line). Write them down. Know them. They're your guide.

During the race: Look at your watch at defined checkpoints only. Once per discipline for sprint and Olympic distance. Every 20–30 minutes on the bike and run for Half IRONMAN (70.3). At each check, ask: "Does this match how I feel?" If yes, carry on. If you feel significantly better than the numbers suggest, don't dial back — trust your body. It built that fitness. Let it use it.

After the race: This is when data earns its place. Analyse everything. Understand what the numbers tell you about where you gained and where you left time on the course. That information feeds directly into your next training block — but on race day itself, it's irrelevant.

---

The Bottom Line

Your fitness is built. It's in there. Twenty, thirty, forty weeks of work have produced an athlete who knows how to race — if you let them.

The watch is a tool. A very good one. But a tool doesn't drive the car.

On race day, you drive. The watch just tells you how fast you're going.

---

Paul Jones is the founder and head coach at F4L Triathlon Coaching — British Triathlon Level 3 and IRONMAN Certified — based in Northumberland. He coaches age-group athletes across Sprint, Olympic and Half IRONMAN (70.3) distances, from first-timers to seasoned competitors, via personalised online coaching programmes.

Want to race with more conviction? Find out more about working with F4L →

---

Frequently Asked Questions

Should I use a GPS watch during a triathlon race?

Yes — but use it as a reference, not a controller. Check your data at defined intervals rather than reacting to every number. The goal is to race by feel and use your watch as a sanity check, not a real-time instruction manual. For sprint and Olympic distance, one check per discipline is enough. For Half IRONMAN (70.3), every 20–30 minutes on the bike and run.

How do I pace a triathlon without relying on my watch?

Build effort awareness in training by regularly practising sessions without pace targets: tempo runs to perceived exertion, bike intervals where you commit to the effort before looking at the power, open-water swims where you check the split afterwards rather than during. The more you train this skill, the more reliable your race-day feel becomes. It's not guesswork — it's a trained skill.

Why is my heart rate so high at the start of a triathlon even when I feel fine?

Race-day adrenaline pushes your heart rate 5–10 beats above your training equivalent for the first 20–30 minutes. This is completely normal and not a sign that you're going too hard. Pacing off heart rate in the early stages of a race will cause you to back off unnecessarily. Perceived effort is the more reliable guide during the opening portion of any race.

What is the best pacing strategy for age-group triathletes?

An effort-based strategy works best for most age-groupers. Set clear effort targets for each discipline before the race, use data periodically during the race as a sanity check, and structure your run so you're working hardest in the final third. The athletes who run through the field late in the race are almost always those who raced by feel rather than chasing numbers from the gun.

How do I stop going out too hard in a triathlon?

The answer isn't to watch your pace more closely — it's to develop a better sense of what a sustainable effort actually feels like. Practise effort awareness in training consistently. Set pre-race effort targets for each discipline. And deliberately ignore the first kilometre of run pace data on race day — it will always look fast due to adrenaline, and reacting to it early is one of the most common race-day mistakes I see.

Does watch dependency affect Half IRONMAN (70.3) athletes differently to sprint or Olympic distance athletes?

Yes. In longer races the consequences compound over time — a slightly overcautious bike leg costs much more at Half IRONMAN distance than at sprint. Athletes racing 70.3 who are overly data-dependent often leave significant time on the bike course when conditions or their fitness on the day would have supported a harder effort. The longer the race, the more important it is to be responsive to how you actually feel, not just what the numbers say.

What's the difference between data-informed and data-controlled racing?

Data-informed racing means using numbers as a periodic sanity check — confirming you're in the right ballpark before getting your focus back on the race. Data-controlled racing means reacting to every blip and adjusting effort constantly based on what the screen shows. The first helps you race well. The second gets in the way of it.