Aug
31
Lessons From a 255-Mile Month
Photo credit: Tired Runner by Flickr user Rennett Stowe, used under a Creative Commons Attribution-Share Alike 2.0 license.
Today, I hit a new milestone in my training – with a 10 mile run (plus strength and core training mixed in the middle), I reached 255 miles of running for August. I think my previous high was in July, at 221 miles, so this was a significant (15%) step up from that. It wasn’t my intent heading into the month; I knew I would probably have at least 225 miles, but throughout the month I started stretching out some runs, threw in a few extra lunch runs here and there, and before I knew it, 250 miles was well in sight. Obviously, current circumstances make finding the time to put in extra miles easier, so I’m not sure I would have been able to do this otherwise, but I am considering this a once-in-a-lifetime opportunity to test how well the body reacts to increased mileage.
At the same time, I have started picking up my “easy” pace and pushing things a little bit on long runs as well, including a half-marathon PR on a training run last week. I’ve decided that if I want to be a sub-3:00 marathoner, I need to start thinking like one, and convincing myself that 7:00 / mile is “easy” (for mid-length runs, at least). I was worried that if I didn’t shift my mindset, it’d be far too easy to fall back to a 7:30 pace when the going gets tough in the late stages of the Akron Marathon next month.
I recognize that a lot of what I’m doing goes against conventional wisdom. You see advice like “easy runs should be at marathon pace + 20%,” or “if you continually put in over 50 miles a week, your risk of injury and fatigue skyrocket,” or “don’t go beyond what your training plan calls for.” I’m not suggesting that this is bad advice. At this point in time, I am feeling no signs of any injury, and while I am more tired than normal in general, my recoveries from all but the longest runs have been good, leaving me able to put in quality workouts up to 5 times per week.
I’ve stated before (in The Running Manifesto) that you sometimes need to “sacrifice to learn.” Given how I have felt, and the bit of a roll I have been on (keeping in mind that this is just training – the proof will have to come from race results), I decided it was the right time to put myself out there a bit and see what this aging (but still sub-40, for those who may have wondered) body is capable of. Ironically, the question-of-the-day on Dailymile yesterday (8/30/10) was, “What’s the most valuable lesson you’ve learned about training/pushing the limits of your body?” The expected answer was probably involved taking rest days when needed, listening to your body at the first sign of injury, or something of the sort. My answer is that I have learned you don’t know what you are capable of until you take some risks, set higher expectations, and push yourself to achieve them.
I’m not advocating that everyone should go out and try this approach. What works for one runner may not work for another. Maybe I had a particularly strong base going into these past two months. Maybe I have the luxury of an efficient running style that puts less stress than normal on my joints. I’m not going to take for granted that this momentum and luck will last forever either, so I’m going to take advantage of the situation while I can. With one exception – just as I have trained hard for Akron, I’m going to taper hard too, to be as refreshed as possible for the race.
I don’t know what this all means for upcoming race results and beyond. I had not intended to go for 3:00 at Akron as I was thinking that was a bit of a stretch on the back-end hills of the course. However, with the amount of work I have put into training in July and August, I shudder to think that even more may be required to break 3:00 at Boston next year. Therefore, we are going to give it a rip at Akron, knowing that there is the risk of the “bonk” and a resulting failure to even set a PR. However, since I’ve learned you don’t know what you are capable of until you take some risks, it is time to lay it all on the line for a race, and find out exactly what that means. My fast recovery from Cleveland suggested that I didn’t push myself as hard as I could at the end – I probably cruised a bit once I knew a BQ and PR were firmly in reach. I don’t want to recover quickly after Akron.






