Running by Effort Instead of Pace Unlocked Speed for One Back-of-the-Pack Runner
For years, my running had two gears: run and walk. Pace targets from training plans felt like a language I couldn't speak. Then a short guided session in the Nike Run Club app showed me that the problem wasn't my fitness. It was what I was aiming at. If you've ever stared at a target pace on a plan and felt your legs refuse before you'd even started, you'll recognize the feeling. It isn't quite a motivation problem, and it isn't really a fitness problem either. It's a mismatch between the instruction and the tool you're using to follow it.
The run that broke the pattern
I had just finished the "First Speed Run," eight one-minute intervals separated by one minute of recovery on a hot afternoon. The virtual coach called out three targets: a mile pace he labeled "fast," a 10K pace he described as "faster, but slower than a mile pace," and marathon pace, the slowest of the three. I struggled through all of it. Frustrated, I went looking for the next workout, hoping it wouldn't ask me to chase numbers I couldn't hit. It was called "Find Your Pace," and I started it almost out of spite. That's a common reaction for runners who've been handed the same kind of targets for months. When a number on a screen keeps winning, you stop trusting your own read of how you feel, and that habit doesn't dissolve in one afternoon.
Coach Cory, who led that session, never asked me to check my Fitbit for metrics or pace. He talked about Rate of Perceived Exertion instead, a scale that has been around for decades and that I had, honestly, ignored the whole time. RPE runs from 1 to 10 and is entirely subjective. A 1 is sitting on the couch. A 3 is a warmup. A 10 is an all-out sprint you can hold for no more than about thirty seconds. "Subjective" sounds like a weakness, and in a way it is, since two people can disagree about what a 7 feels like. But that's also why the scale works. It measures what your body is doing today, not what a formula says it should be doing. It's survived for decades for a reason.
Effort first, numbers second
Cory tied effort to distance. A 10K should feel like a 6, a 5K like a 7, and a mile like a 9. He also suggested attaching a word to each level, such as "strong" for a 6. My own vocabulary was less polished. At a 6, I thought, this is hard. At a 7, I thought, I can't do this. By the time I reached a 9, my only thought was I have to stop. Cory picked "epic" for his fastest effort. He's clearly an optimist. I think the word trick is underrated, though. "Strong" is a different instruction than "hard," and the first one keeps you from spiraling into "I can't" halfway through a rep.
The intervals were short, and my breathing and heart rate barely climbed. That's a strange thing to notice mid-workout, and it's worth pausing on. Usually a hard effort lights up every gauge you have, so a flat readout alongside a hard feeling suggests you're learning to separate the two. What struck me was the effort itself. I was pushing harder than I ever had in a training run, and I never once glanced at the watch to see whether I was on target. In every previous session, that glance had been the whole point. The entire workout lasted 10 minutes, which is short enough that it felt more like a demo than a session.
The numbers were the surprise
So did I actually run at different paces? Yes, and faster than I expected. My mile pace came in at 9:21, my 5K at 10:30, and my 10K at 10:54. Those are the fastest splits I've logged in training or racing. I'll admit I looked at them twice, mostly because they didn't match the sensation I'd had. I'd been working hard, but I'd assumed I was operating well inside my limits, so the numbers felt almost unfair. I hadn't been chasing them. I had been chasing effort levels, and the pace followed.
That distinction matters more than it sounds. Finding a pace assumes it exists somewhere outside you, waiting to be hit. Creating one means you control the variable. When training plans handed me goal paces, I kept missing them, and every miss chipped at my confidence. When I ran by RPE, I could tell a 6 from a 9, and those levels mapped onto distinct race speeds without my having to calculate anything. Anyone who's been stuck at one speed knows the trap: you chase a number, miss, feel like a failure, and then tighten up on the next run. Effort breaks that loop because it gives you something to succeed at on the day, even when the splits are off.
The session gave me something beyond the splits, too. It showed me what was possible if I kept training, and it made me less willing to write myself off as a two-speed runner. Two runs don't make a training block, and I'm wary of anyone who says otherwise. Still, it changed how I think about the watch. Now, when a plan calls for 5K or 10K pace, I skip the screen and aim for the effort. My guess is that many runners who feel stuck at one speed are fighting the metric rather than the workout. Start with the feel, and the numbers may show up on their own.
What this means if you're stuck
If you're working through a plan that keeps handing you paces you can't hit, the practical takeaway isn't to throw out your watch. It's to change the order. Start with effort, check how the run feels, and then use the watch to confirm what you noticed rather than to tell you what to feel. That sequence sounds small, but it reverses the relationship most of us have with our data.
There are real limits here, and I don't want to oversell the approach. RPE depends on honesty, and it's easy to call a hard run easy when you're tired or itching to go faster. It also doesn't tell you much about the precise pacing a race demands, where a specific split can matter a lot. And a single session can't replace structured progression over weeks. If you're training for an event with a fixed target, you'll likely still need some measurement somewhere in the plan.
Where this goes next is worth watching. Effort-based coaching is cheap to deliver inside an app, so I'd expect more platforms to lean on it. Some will do it well, with real coaching behind the cues. Others will use it as a marketing hook and leave the user with a vague instruction and no follow-through. That's the part I'd keep an eye on, and it's the difference between a tool that changes how you run and one that just sounds friendlier than the watch.
