Stop Checking Your Pace Every 30 Seconds

Flotti's rant: that obsessive glancing at your watch mid-run is making you slower, more anxious, and less in tune with your body.

Flotti

I need to talk about something I see constantly. You're 2km into an easy run. You look at your wrist. 5:12/km. Too slow? Too fast? You speed up a little. Check again at 2.5km. 4:58/km. OK, that's better? No, wait, that's too fast for easy. Slow down. Check again. 5:21/km. Ugh.

You're not running. You're doing maths homework with heavy breathing.

The pace-checking habit

Be honest. How often do you look at your watch during a run? Every kilometre? Every 500 metres? Every time the screen flashes?

47x

Average watch checks per 10K run*

Times it changed the outcome

OK, I made that number up. But you know it’s not far off.

The problem isn’t caring about pace. Pace is a useful metric — after the run, when you review it. The problem is micro-managing your pace in real time, turning every run into a stressful negotiation with a number on a screen.

warning GPS pace is noisy

Your watch's instant pace fluctuates wildly — trees, buildings, clouds, wrist angle, even which satellites are overhead. That "5:12" could be anywhere from 4:50 to 5:30 in reality. You're reacting to noise, not signal.

What it does to your running

Constant pace-checking creates a feedback loop that makes your running worse:

You stop listening to your body. Instead of feeling the effort, you’re reading a number. Your legs know what “easy” feels like. Your watch doesn’t.
You run uneven splits. Speed up, slow down, speed up, slow down. Accordion pacing is less efficient than holding steady — and the constant adjustment costs mental energy.
You turn easy runs into tempo runs. Because 5:15/km feels slow when you know you can do 4:50. So you push. And now your easy run isn’t easy.

Flotti — straight talk

I've analyzed your runs. On the days you hold a steady effort, your average heart rate is lower, your pace is more consistent, and your training load is appropriate. On the days you pace-watch, everything's choppy and you finish more fatigued for the same distance. The data doesn't lie.

When pace actually matters

I’m not saying pace is useless. There are exactly two situations where checking pace mid-run makes sense:

1. Interval reps. You’re doing 5×1km at a target pace. Yes, check the pace. That’s the whole point — you’re hitting a specific stimulus.

2. Race day. Going out too fast in a 10K is a real risk. A pace check at km 1-2 to make sure you’re not in the red? Smart.

That’s it. Two scenarios. Everything else? Run by feel and review the data later.

directions_run Illustration: runner looking at the road, not the watch

The experiment

Next week, try this: set your watch to show only time of day. No pace. No distance. No heart rate. Just a clock.

Run your usual easy route. Don’t look at stats until you’re home, showered, and sitting down.

tips_and_updates What you'll notice

You'll probably run slightly slower than usual. That's fine — it means your "easy" was too fast before. You'll also enjoy the run more. Your brain gets to actually be present instead of doing arithmetic.

Then open Flott, sync the run, and let me break it down for you. I’ll tell you the pace, the zones, the training effect — all the stuff you were anxiously checking mid-run, but without the anxiety.

I’m here for the debrief, not the play-by-play

That’s the whole point of having an AI training companion. You don’t need a number shouting at you from your wrist every 30 seconds. You need someone to look at the full picture afterwards and say: “That was a great easy run. Exactly what you needed.”

Or: “That was supposed to be easy and it wasn’t. Let’s talk about why.”

Either way, the analysis is better with complete data, not panicked mid-run adjustments.

Flotti

Run the run. I'll handle the numbers.

— Flotti

Wants you to look at trees, not screens