Photo by Peter Kambey on Pexels
You check your watch mid-run more than you used to. You know your average pace for the last six weeks off the top of your head. You’ve started feeling a small drop in your stomach when a run doesn’t sync properly to Strava, like the run didn’t really count if nobody can see it. If any of that sounds familiar, you’re not broken and you’re not alone — you’ve just slid from using data to help you run better, into using it to tell you whether you’re allowed to feel good about yourself today.
Tracking progress is genuinely useful. It’s how you know your easy pace has dropped from 6:40/km to 6:15/km over four months, or that your weekly mileage has crept up safely rather than dangerously. The problem isn’t the tracking. It’s when the numbers stop informing your training and start running your mood. This article is about keeping the first part and losing the second.
Why obsessive tracking backfires (and it’s not just “vanity”)
Checking your pace every 30 seconds or re-reading last week’s splits before bed isn’t a character flaw — it’s usually a sign the data has become your main source of reassurance that training is “working.” The trouble is that running fitness doesn’t move in a straight line. You’ll have faster days and slower days for reasons that have nothing to do with your training: poor sleep, a stressful day at work, heat, hydration, even what you ate at lunch. If you’re measuring success run-by-run, you’re measuring noise, not signal.
Over time, this tends to do two things. First, it makes easy runs harder than they should be, because you’re racing the watch instead of running by feel — which undermines the entire point of an easy run (more on that below). Second, it makes a missed run or a bad week feel like failure, which is exactly the kind of thinking that makes people quit running altogether. The runners who stick with this for years are, almost without exception, the ones who’ve learned to hold their data loosely.
Track trends, not sessions
The single most useful shift you can make is to stop judging any individual run and start judging four-to-six week blocks. One slow Tuesday run tells you almost nothing. Your average easy pace over six weeks tells you a lot.
Here’s a simple way to do it without turning your life into a spreadsheet:
| What to track | How often to check it | What it tells you |
|---|---|---|
| Weekly mileage total | Weekly | Whether you’re building gradually or ramping too fast |
| Average easy pace | Monthly | Aerobic fitness improvement (should trend down over months) |
| Resting heart rate | Weekly (same time of day) | General recovery and fatigue trend |
| Long run distance | Weekly | Progression toward race distance |
| How runs felt (1–10 effort) | After every run, 10 seconds | Whether effort matches intended session |
Notice what’s missing: daily pace comparisons, calories burned, “streaks,” and anything that updates in real time while you’re running. Those are the metrics that hijack your attention mid-run and turn a recovery jog into a performance review.
Set one review day a week — not every day
Pick a fixed time, say Sunday evening, and that’s when you look at the week as a whole. Not during the run, not immediately after, not at 11pm scrolling your watch app for no particular reason. Once a week is plenty to spot real trends; daily checking mostly just feeds anxiety.
When you do your weekly review, ask three questions:
- Did I run roughly what I planned (within 10–15%)?
- Did my easy runs feel easy — conversational, nose-breathing-ish effort — or did I grind through them?
- Am I more tired than last week, less, or about the same?
That’s it. You don’t need to analyse cadence, vertical oscillation, or ground contact time unless you’re chasing a specific technical goal with a coach. For 95% of runners training for a 5K, 10K, half marathon or first marathon, those three questions capture what actually matters.
Use effort-based cues alongside the numbers
One reason GPS data becomes obsessive is that it’s the only feedback loop people trust. But your body gives you better information than your watch does, most of the time — you just have to practise listening to it.
The conversational test still holds up: on an easy run, you should be able to speak in full sentences. If you’re gasping single words, you’re running too hard for an easy day, regardless of what pace your watch says is “your easy pace.” Heart rate zones can help here too, particularly if you’re prone to running everything at the same medium-hard effort (a very common habit) — our guide to heart rate training zones for runners breaks down how to find your zones without needing a lab test.
Using effort as your primary dial and pace as a secondary check — rather than the other way round — takes pressure off the number on your wrist. Some days 6:30/km will feel like your easy effort. Other days, after a bad night’s sleep or in 24°C heat, that same effort might be 7:10/km. Both are correct. The watch pace is downstream of effort, not the other way around.
Pick 2–3 metrics that matter for your actual goal, ignore the rest
Modern running apps throw a lot of numbers at you — training load, recovery score, VO2 max estimate, “fitness age,” running power. Most of these are either unreliable estimates or simply irrelevant to what you’re training for. Decide what actually matters for your goal, and let the rest sit unopened.
- Training for your first 5K or 10K without stopping: track total minutes run and how many of them were walk-free. Pace is almost irrelevant at this stage.
- Training for a half marathon time goal: track long run distance progression and whether your goal-pace reps feel sustainable, not just whether you hit the number once.
- Training for a sub-4 marathon: track weekly mileage consistency and your pace at a fixed, repeatable effort (e.g. a monthly 5K time trial), rather than daily pace swings.
If you’re newer to structured plans, a good running app for beginners can automate most of this tracking for you, which honestly removes a lot of the temptation to manually re-check your own numbers all day.
What to do when the numbers disappoint you
They will, at some point — a slower-than-expected run, a week where mileage dropped because work got in the way, a race that didn’t go to plan. This is where obsessive tracking does the most damage, because it’s easy to let one data point define your whole sense of progress.
The useful response is to zoom out, not in. Compare this month to three months ago, not this run to last run. If you had a genuinely rough run, it’s worth reading through how to bounce back from a bad run rather than spiralling into re-checking your splits for an explanation. Most of the time there isn’t one — it was just a bad day, and bad days don’t erase four months of consistent training.
A simple weekly tracking habit that won’t eat your evenings
If you want something concrete to start tomorrow, here’s a five-minute version:
- During the run: glance at your watch at most once or twice, ideally only to pace a specific workout (intervals, tempo). Leave it alone on easy days.
- Right after: log distance and effort (1–10) in your app. Nothing else.
- Once a week: total your mileage, note your average easy pace, and ask the three review questions above.
- Once a month: compare this month’s totals to last month’s. Look for a gentle upward trend in mileage and a gentle downward trend in easy pace. That’s progress — it doesn’t need to look dramatic.
According to the NHS guidance on physical activity, consistency over time matters far more than any single session — which is really the whole argument here in one sentence. And building that consistency gradually, rather than chasing week-on-week gains, is also the single best way to stay injury-free, something covered well in general guidance from the British Heart Foundation on steady, sustainable exercise habits.
The Honest Takeaway
- Review your training weekly or monthly, not run-by-run — a single bad or great session tells you almost nothing on its own.
- Pick 2–3 metrics tied to your actual goal (mileage, easy pace, long run distance) and ignore the rest of what your app shows you.
- Use effort and conversational pace as your primary guide on easy days; let your watch pace be a secondary check, not the boss of the run.
- When a number disappoints you, zoom out to a three-month view before deciding anything’s wrong.
- If checking your stats is adding stress rather than information, that’s the signal to check less often — not to find a better app.
Next read: From jogger to runner: the mindset shift explained