No, that doesn’t mean that I just need to tweak the code, swap a few digits out, and cheat my way to a fast prediction. It means that, if I want to have a shot at running a good marathon, I have to get myself into shape to run good times at the shorter distances.

That might seem obvious—in fact, it does seem obvious to me now—but for some reason, I had separated my poor performances at the shorter distances from my poor performances at the marathon.

Now that I’ve corrected that flaw in my thinking, I’m able to tackle the marathon goal from a different angle. Rather than just saying I want to get back into sub-3-hour marathon shape—a fairly abstract goal because it’s so far removed from what a typical training run looks like—I can say that I need to get back to an X-minute 10K in order to be in good enough to shape to run sub-3 in the marathon. And, thanks to the Predictor, Robert James Reese.

That’s when the lightbulb went off. I’m running slow marathons because I’m running slow 10Ks (and because I’m not running enough weekly mileage).

Playing around with the Predictor a bit, I found that a 37:00 10K and 60 miles per week should be enough to get me back under three hours. Those goals seem much more straightforward.

Obviously, it’s a little too late for this fall—I’m running Chicago on Sunday—but I’m going to use this new way of thinking to get back into shape for a good 26.2 in the spring.

* * *

I Did 30 Burpees For 15 Days, Here’s What Happened Runner’s World VIP.

Headshot of London Marathon Results

Robert is the former Executive Producer for Runner’s World Online. He has run over 60 marathons with a personal best of 2:52:11.