An appropriately titled post, since roughly two thirds of the way into this race I wanted to crawl into a hole and die.
It’s been exactly a month since my debacle in Oregon. In the intervening weeks I’ve had time to review my training log and diary, and discuss theories with Coach Kevin.
I’ve also had bloodwork to rule out anything there. And, although I suspect I could potentially feel better with higher iron-related numbers (and may start supplementing as an experiment), I don’t feel that the root cause is to be found there. No, I think it was simply a matter of too much for too long.
A couple of days after the race, I sat in my room in the Crater Lake Lodge (during a rare evening of relative sobriety) and penned (okay, typed) a document that I entitled “Training Theories.” Here it is verbatim, with some helpful links:
What went wrong?
Peaked too early?
I was running my best in mid-April. The workouts were going very well. I had that “magical run” on April 21 when I couldn’t hold back from running fast and had wished that were a race day. A few days later I flew around the track for those sub-6:20 mile repeats. I’m convinced that if I’d simply tapered for two weeks after around April 12 and run a marathon around April 26 I would have had a great run.
Couldn’t hold fitness?
I suspect that not only was it impossible to hold that peak for the following seven weeks, but I probably managed to degrade that fitness by foolishly pushing too hard through some exhausting runs. The ones that stand out are the two very hot runs in late April (20 miles in Central Park in 91 degree heat on April 26 and that awful track session two days later). Then I ran the NJ Half on May 3, which I thought would serve as a good training run (if a lousy race), but now I think it probably dug me in further in terms of creating a deficit in recovery.
“Up and down” schedule around tuneup half?
Then the next few weeks were so up and down due to the “interruption” of that race that I suspect the result may have been a staleness that settled in slowly. This was evident, although very subtle, in the remaining key workouts. I chalked up any issues with those to weather factors or just the regular ups and downs of not being quite recovered from day to day.
The run the day before the race should have been a red flag. I chose not to wear my HRM (although now I wish I had). But at one point I decided to run a fast quarter mile. I managed to get down to 7:00 pace but I was working very hard to do so. I decided it was just nerves and didn’t give it another thought.
Possible modifications
If left to my own devices, here’s what I would do differently next time around:
- Shorten the total training+taper cycle by about seven weeks.
- Shorten the taper, assuming the buildup has been invigorating rather than exhausting. Maybe two weeks rather than three?
- Introduce Mpace miles much earlier in the cycle, with a gradual buildup. More on this below.
- If I’m going to race during training, choose the races only so much as they support the specific marathon event (similar terrain, etc.), and allow adequate recovery from them. If that means fewer races (or none), so be it.
- Include a little bit of fast running early in the taper. I do wonder if those solid two weeks of recovery running somehow contributed to the extreme slowdown on race day.
- Do more Mpace running on the roads rather than the track.
As for Mpace running, I think I need to do more of it and a lot earlier. I never quite clicked with that pace in terms of matching pace to appropriate effort level. Although I can race a full at 88-89% MHR, I’d be a lot more comfortable getting to a point where I’m at more like 86-87%.
What we could try is having me do a few Mpace miles every week (or every other, if we started this during basebuilding), starting with just a few miles thrown into a longer run and working up to lengthy Mpace efforts toward the end. This method worked very well for me for my Spring 08 race, when I basically took one of Pete’s plans and modified it by adding in a few more of those faster miles every week. By the time I got to the 12 mile and 10 mile Mpace efforts during this cycle, I think I was already cooked. I’m not completely sure that I even needed those two workouts, and they may have further exhausted me.
So there you have — the best I can do with the data (and gut feelings) that I have.
I know I learned a lot from this experience, as has Kevin. When we were talking a few days after the race he said, “I have to remember that you’re a mortal.” By that he meant that between the 9 week basebuilding period (during which I got faster) and the following 22 weeks of training, it seemed like I had the capacity to absorb any amount of work and continue to flourish. That durability and work ethic, when coupled with a capacity for self-denial and dare I say irrational optimism, added up to our both missing some subtle yet insistent signs.
Looking back, I think the cracks were beginning to show at the tail end of April in that I was really struggling to hit times in workouts (and the NJ half wasn’t even close). It was easy to attribute those problems to other forces, but I’ll be a lot more attentive going forward to, as well as more communicative about, the qualitative aspects of the work. Heart rate data is valuable. But seeing and acknowledging that you’re working way too hard, regardless of what the stupid watch says, is more important than any data.
Hot weather training presents its own challenges, of course, but the plan I’m getting will allow for it. The timing looks to work out to around a 14 week training schedule, including the taper (which we discussed shortening). I’m hopeful that between a shorter training cycle and having learned some important lessons, I can look forward to a happier experience in Sacramento come December. (knock wood)
Filed under: basebuilding, coaching, physiology, racing, recovery, training, travel | Tagged: marathon, newport marathon, pete pfitzinger, post mortem | 18 Comments »
Races Like a Girl 