What Happens When You Ditch GPS for Running
You lace up, step outside, and immediately glance at your watch to confirm your GPS has locked on. The run starts. Every half mile, a buzz. Every kilometer, a split. By mile two, you're adjusting your pace not because your body is asking you to, but because a number told you to. Sound familiar?
More runners are quietly experimenting with something that feels almost radical in 2025: leaving the GPS watch at home. Not permanently, not out of some anti-technology ideology, but as a deliberate reset. The results, both anecdotal and supported by exercise science, are worth paying attention to.
The Problem With Always Knowing Your Pace
GPS running watches are genuinely useful tools. They track volume, monitor trends, flag overtraining patterns, and give coaches hard data to work with. Nobody serious is arguing they're useless. But there's a growing body of evidence suggesting that constant real-time feedback can actively interfere with how you learn to run.
The core issue is what sports psychologists call external focus override. When you're watching your pace tick up on a screen, you're pulling attention away from internal signals: breathing rate, leg fatigue, perceived effort. Over time, runners who rely heavily on real-time data can lose the ability to self-regulate without it. They become dependent on external cues to tell them what their own body is doing.
Research in the Journal of Sports Sciences found that athletes who trained using perceived effort alongside objective metrics developed stronger long-term pacing strategies than those who relied on external feedback alone. The reasoning is straightforward: learning to interpret your own physiological signals builds a deeper, more adaptable sense of effort that holds up in races, on unfamiliar terrain, and when your watch dies at mile 18.
How Data Feedback Creates Anxiety Loops
Here's a scenario that plays out constantly in training groups. A runner sets out for an easy aerobic run, the kind that should feel genuinely comfortable. They're supposed to be in zone 2. But within the first mile, the watch shows their pace is slower than usual. The runner speeds up slightly, not because they feel like speeding up, but because the number feels wrong. The heart rate ticks up. Now the watch is showing zone 3. The runner backs off. The pace drops. It feels slow. The anxiety ratchets up.
What was supposed to be a recovery run has become a negotiation with a device.
This feedback loop is particularly damaging on easy days. Recovery runs are only effective if they're genuinely easy, meaning your body has to actually downregulate its effort, not just approximate it while quietly stressed. When your focus is split between your legs and your screen, it's hard to fully relax into the run. Cortisol stays slightly elevated. The recovery benefit is partially lost.
That anxiety can compound over weeks. Some runners report dreading runs because they know the data will stress them out. That's a significant problem, because enjoyment and intrinsic motivation are among the strongest predictors of long-term running consistency.
Rate of Perceived Exertion: The Science Behind Running by Feel
Rate of perceived exertion, or RPE, is a well-validated scale used in exercise physiology to measure how hard someone feels they're working. The classic version runs from 6 to 20, though most coaches use a simplified 1-to-10 scale. At RPE 3 or 4, you're running easy. At RPE 7 or 8, you're working hard but sustainable. At RPE 9 or 10, you're near maximum effort.
RPE isn't a soft, fuzzy alternative to data. It's a legitimate physiological measurement. Studies have consistently shown that trained athletes' perceived exertion correlates closely with objective markers like lactate threshold and VO2 max. Your body actually knows what it's doing. The problem is that most recreational runners never develop the internal awareness to trust it.
Dropping GPS forces you to develop that awareness. Without a number to chase, you have to ask yourself: how does this actually feel? Is my breathing controlled? Can I hold a conversation? Do my legs feel heavy or springy? These are trainable perceptions, and training them makes you a better, more adaptable runner.
Elite trail runners, including many competing in events covered in pieces like Zegama, Snowdonia, Tahoe 200: Trail's Biggest Weekend, often describe pace as largely irrelevant on technical terrain. What matters is effort management over hours and thousands of feet of elevation. That skill doesn't come from watching a screen.
The 2-to-4 Week GPS-Free Experiment
You don't need to abandon your data forever to get these benefits. A structured two-to-four week experiment can recalibrate your relationship with effort and remind you what running actually feels like when you're not managing a dashboard.
Here's how to do it without losing training progress:
- Keep a time-based structure. You don't need distance or pace data to maintain aerobic volume. Run by time instead. A 45-minute easy run is still a 45-minute easy run whether you know the mileage or not. Your cardiovascular system doesn't care about the number.
- Use a basic heart rate monitor if you're nervous. This is a compromise, but it keeps one objective anchor without the pace feedback that causes most of the anxiety. You can see that your heart rate is in an appropriate zone without obsessing over splits.
- Run familiar routes. Remove as many unknowns as possible. If you know the terrain, you can gauge effort without needing data as a reference point.
- Log subjective notes after every run. Energy level, perceived effort, mood, how your legs felt. This builds a qualitative training log that's often more useful than raw pace data in identifying patterns.
- Start with easy runs only. Don't ditch GPS on a speed session in week one. Begin with your lowest-intensity days, where the feedback loop problem is worst anyway.
Most runners who try this report two distinct phases. The first week feels uncomfortable, sometimes frustrating. Without data, runs can feel formless. By week two or three, something shifts. Runs start feeling like runs again rather than performance tests. Easy days start feeling genuinely easy. Many runners describe rediscovering the reason they started running in the first place.
What to Watch For During the Experiment
A few things tend to happen when you pull back the data layer, and it's worth knowing what to expect.
First, your easy runs will probably feel slower than you expect, and that's fine. Most recreational runners chronically over-pace their easy days because they're unconsciously chasing numbers. When you remove that pressure, your natural easy pace often drops. This is correct. It means you're actually running easy.
Second, hard efforts often feel more honest. Without pace targets to hit, you run hard efforts by how hard they feel, which tends to calibrate them more accurately to your current fitness than a goal number from six months ago.
Third, you'll likely enjoy running more. This isn't a minor side effect. Enjoyment is load management. Runners who enjoy their training are less likely to skip sessions, more likely to run consistently over years, and better at managing injury risk because they're not grinding through sessions that feel miserable.
For runners who incorporate strength or hybrid work alongside their running, the same principle applies. Perceived effort as a primary training cue, with data used to confirm rather than dictate, tends to produce more sustainable progress across all formats.
Bringing Data Back Intentionally
After your experiment, you don't have to choose between GPS and no GPS. The goal is to reach a point where data informs your training rather than controls it.
Practically, this means using GPS and pace data for specific purposes: tracking weekly volume trends, reviewing a race effort, confirming that your easy pace is genuinely easy over time. It means not checking your watch mid-run on recovery days. It means trusting a strong effort in a workout even when the pace number looks off.
The runners who use data most effectively treat it the way a pilot treats instruments: useful for confirmation, not as the primary interface with reality. Your legs, lungs, and perceived effort are the primary interface. The watch is backup.
This approach also translates directly to race day, where conditions, terrain, and competitive pressure can make pre-set pace targets actively harmful. Runners who know how to manage effort by feel can adapt in real time in a way that GPS-dependent runners often can't. That's a competitive edge worth developing, whether you're chasing a personal best on the roads or exploring what race day actually looks like at Run The Rocks Moab.
The Bigger Picture
Running culture has leaned hard into data over the past decade, and that has produced real benefits. Training loads are better managed. Overtraining is easier to spot. Physiological trends are trackable in ways that weren't accessible to recreational athletes a generation ago.
But the pendulum has swung far enough that a lot of runners have outsourced their internal awareness entirely. They know their VO2 max estimate but don't know what an easy effort feels like. They know their weekly mileage down to the decimal but can't tell you if they're tired or fresh.
Rebuilding that internal awareness doesn't require rejecting technology. It requires remembering that the technology is there to serve the running, not the other way around. A few weeks without GPS is a small investment for a significant recalibration. Most runners who try it come back to their watches with a different relationship: in charge of the data, rather than managed by it.
That shift tends to make everything else better. Including, usually, the times.