The essence of the training principle of specificity is that one’s training should simulate one’s target races. When I’m preparing for an ultramarathon, long runs at race pace are my top priority, since they are reasonable approximations of the race itself; tempo runs of 4 to 6 miles are a secondary priority, since they’re much shorter and faster than the race; and interval workouts are a relatively low priority, since those involve running even shorter distances at even faster paces.
I think this general approach makes a lot of sense, but there’s a catch: the way I rank these workouts in terms of their presumed importance is also the way I rank them in terms of the amount of damage they do to my body and the length of time needed to recover from them. After a long and fast run, it might be a full week before I feel normal again.
Thus, as a race approaches, I invariably find myself choosing between (A) squeezing in one final long/hard effort and (B) skipping the long one in order to start the race with fresh legs.
Up to now I’ve tended to favor the former strategy, but it doesn’t seem to be working for me. In two of my last four ultras — the Miwok 100K and the World Cup 100K — I’ve sensed a bit of muscle fatigue as early as 8-9 miles into the race and had to slow down to keep further fatigue at bay. In the other two — Mad City and Western States — my quads simply shut down long before the finish line.
Time to try something new? I think so. In my final 4-5 weeks before the JFK 50-miler (on November 17th), I’m not doing any runs longer than 21 miles. My training is on a three-day cycle: a speed workout or short tempo run followed by two easy days.
It’s the kind of nonspecific regimen that my brain disapproves of, but maybe my legs will like it.
Leave a reply to crowther Cancel reply