Disclaimer: I chose this training program of my own accord. The folks who created Run Less, Run Faster have no idea I even exist. All thoughts and opinions are my own.
Now that I’ve completed a full training cycle using Run Less, Run Faster, I feel qualified to offer up some non-professional opinions about it.
To begin with, here are the reasons why I initially chose the Run Less, Run Faster program:
- Lots of cross-training: Great for a triathlete.
- Three runs a week: I don’t always like running all that much.
- Simple: Each week was structured the same way, and the paces were very easy to calculate.
- Free: I found a version online for free. Yes, please!
There is a book which offers a more recent version of the program, along with cross-training workouts and ways to customize the plan if needed. However, I just used the article I found on Runner’s World and put together a schedule using that.
The Run Less, Run Faster plan is actually quite polarizing. There are some great reviews online and some reviews that are very critical of its entire premise. I tried to offer a fair review here that acknowledged some of those criticisms. Overall, though, I had a very positive experience with Run Less, Run Faster. I don’t think it’s the right plan for everyone, but it was the right plan for me.
The Run Less aspect of the program is probably its biggest marketing point. And it was probably my favorite part. Now, “running less” does not necessarily mean working out less. The Run Less, Run Faster program is supposed to include 2-3 days of cross-training on top of the three days of running. I didn’t use the cross-training workouts provided by the book. I mostly went on 30-60 minute bike rides and did Masters Swim Team practices. A lot of the criticisms of the Run Less, Run Faster program revolve around this focus on cross-training. Essentially, the critique is that to run better, you have to run more. I think this criticism has validity to it, but when you are a triathlete (even an off-season one!), running more isn’t always better. The Run Less, Run Faster program allowed me to keep cross-training throughout the winter so that I wouldn’t have as much ground to make up in the spring. As an added bonus, I became a much better swimmer this winter as well as improving my running endurance and speed. Becoming a better swimmer might not matter to a pure runner, but it does matter to a triathlete. For this reason alone, I can’t see myself using any of the other common marathon training plans out there. At this point in my life, I am focusing enough on triathlons that I can’t afford to take a four month break from two of the three disciplines.
The other major part of this program is the Run Faster aspect. And, without a doubt, I became a much faster runner using this program. I’ve spent the past few years a little scared of running fast and just running long and slow (or, usually, short and slow) But the track workouts in this program helped me pick some of that speed back up. My ability to run faster over the short distances made the slower distances of my tempo and long runs feel much easier. When I was training for my half Ironman a few years ago, I typically ran my long runs around a 9:00/mile pace. My long runs during my marathon training were all under an 8:30/mile pace. Not only that, but I found myself actually enjoying the speed work. Because I’m often not a huge fan of running, I need some variety to make something as arduous as marathon training palatable. I’m hoping that the speed I developed carries over into my Ironman training. I know I will lose some speed as I focus more on the other two sports and more on just plain endurance, but I’m confident I’ll be faster than I would have been had I not worked on increasing my speed this winter.
Another touted benefit of the Run Less, Run Faster program is injury-prevention. According to the program, running only three days a week helps you avoid overuse injuries. However, according to criticisms of the program, only ever running fast (like this program calls for—even the long runs are faster than with most programs) is more likely to lead to injuries than volume. Honestly, I’m a bit on the fence about this. Note that I did spend the last week of this training cycle not running because of IT band pain. However, I don’t believe that is due to the Run Less, Run Faster program. After doing some very official Internet Research™, I’ve come to the conclusion that my focus on cycling the past few years is what has made my IT band a problem when it never was before. From what I read, triathletes who run a lot (me this winter!) often suffer from IT band pain because, with the amount of cycling they do, developing quads at the expense of glutes is pretty much inevitable. It wasn’t the cross-training within the Run Less, Run Faster program that caused this. It was the long rides up Big Cottonwood and the frequent rides up Emigration Canyon that were the culprits. In fact, I think I would have started suffering from intense IT band pain much earlier in my training if I had been using a traditional program. IT band pain tends to be worse on slower runs. I noticed this myself. I barely felt it at all during my intervals. It was my longer runs that gave me trouble. Doing cross-training on the days where I was not running hard gave my IT band a chance to recover a bit instead of going from hard run to slow run and constantly creating opportunity for it to get more and more irritated.
That being said, I do think there can be a risk of injury from the “run fast” part of the program for certain runners. I ran track for eight years. My body, despite the long break I took, understands running fast(ish). And, in the grand scheme of things, “running fast” in a marathon training program still wasn’t fast compared to what I ran in college, especially because I was a hurdler. Lots of short events. So, while the speed work was a strain on my body, it was a good strain—the kind the challenges you and makes you better. If you’ve never done speed work before, the intervals in the Run Less, Run Faster might overwhelm your body. If you are just getting into speed work, it might be better to focus on longer intervals like mile repeats instead of 400s that are about :45/mile faster than your 5k pace.
The other major criticism of the Run Less, Run Faster plan is that the fast long runs and lack of longer, slow distances limit your aerobic development. And during my marathon, I crashed hard. I don’t think the training plan can be blamed for the entirety of that. After all, I performed better on all my long runs than I did for the first 15-20 miles of my marathon. I was failing just fine on my own before the plan even had the chance to fail me. However, it’s possible that if I had stronger base aerobic fitness for running, the stress of life or my carefulness of with my knee or a bad day wouldn’t have been quote so devastating for my performance. Obviously, there’s no way to know.
So, would I use the Run Less, Run Faster program again? I absolutely would. As I said above, as a triathlete, it seems like the best option for me. Even if I weren’t a triathlete, I loved the training (as much as I could possibly love training for a marathon). I liked getting faster and seeing my progress. I don’t enjoy recovery runs. Because I don’t enjoy running as much as I do swimming or cycling, I have a hard time going on runs that are “just cardio” and aren’t actual, defined workouts. The focus on cross-training kept me from burning out mentally.
If I did the program again, though, I think I would make some changes:
- Get the actual book. This way, I’d understand the plan better and be more equipped to make changes if necessary.
- More warming up and cooling down. I was not great at warming up and cooling down with my speed work and tempo runs. If I use this plan again, I will make sure that my warm-up/cool down for these faster workouts is much more significant. Like, running a mile or two before a five mile tempo run and cooling down for at least a mile. This would help me get in some of that slow running that the plan doesn’t include.
- Longer bike rides. Because it was winter, my bike rides suffered. I should have been getting out on some rides that were 90 minutes or longer. That would have helped my general aerobic fitness and perhaps given me some of the same benefits as a long, slow run would.
- Strength training. Knowing what I know now about the IT band, I would make sure to include glute strengthening in any marathon training program from the get-go. An ounce of prevention is worth a pound of cure!
- One more run a week. Maybe I would do this, maybe I wouldn’t. But I would consider adding in one extra easy run a week, perhaps as part of a bike-run brick.
As I said at the beginning, overall, I had a great experience with the Run Less, Run Faster training plan itself. The race that I trained for, however, didn’t go nearly as well. How much of that is the fault of the plan is impossible to say. I would eventually like to get some redemption for that shoddy marathon of mine, and when that time comes, I’ll be using this training plan with some of the modifications noted above. Hopefully, the next time around, I’ll be able to write a review without the caveat of a bad race.