Time Trial

A study just published in the International Journal of Sports Physiology caught my attention, and I’d like to tell you about it. Conducted by researchers at the University of Worcester, it compared performance, pacing strategy, perceived exertion, and affect in a 10K solo time trial and a 10K race in a group of 14 male runners.

Half of the runners performed the time trial before the race (on a separate day) and the other half performed the time trial after the race (also on a separate day) to ensure that the order of the two events did not skew the results. As you might expect, most of the runners covered the 10K distance faster in the race context than they did in the solo time trial. The average time in the latter was 40:28, compared to 39:32 in the former—that’s a 2.3 percent difference.

Pacing strategies did not differ between the two events. Most of the runners started and finished both the time trial and the race faster than they ran the middle part. Nor was perceived exertion different. By and large, the runners felt they ran equally hard in the race and the time trial. But there was a significant difference in reported positive affect. Simply put, the runners enjoyed the race more, and the authors of the study believe it was this bump in positive affect that the runners got from the competitive environment that accounted for their superior performance.

There’s nothing new in the finding that runners run faster in competition than they do against the clock. One important implication of this fact is that, if I were to ask you to run a solo time trial as a way to gauge your current fitness level so that I could assign appropriate pace targets for your training, I would get a somewhat inexact picture of your current fitness level. The result wouldn’t be completely worthless, as it would know it was about 2.3 percent slower than you could have gone in a race, but still a race would be better.

Time-based time trials (e.g. 30 minutes rather than 10K) I trust even less. They work well enough in cycling, where fitness testing is done mainly indoors, but runners aren’t accustomed to thinking in terms of duration when trying to pace all-out efforts. The typical competitive recreational runner is simply more likely to botch the pacing of a time-based trial than of a distance-based time trial or race.

Lab-based physiological tests such as lactate threshold tests and VO2max tests I trust even less. They look so scientific, what with the breathing mask and the blood draws and all, but studies have shown that small adjustments to the design of these tests yield significantly different results. For example, a traditional VO2max test features an open-loop design, meaning it continues until the subject quits voluntarily. But a closed-loop alternative created by Lex Mauger and Nick Sculthorpe at the University of Bedfordshire results in far greater VO2max scores in most subjects. (It bears noting that a race itself is a closed loop.)

For all of these reasons, when I want to know how fit a runner is, I either ask the runner for a recent race result or I request that the runner complete a race. In the latter scenario, I specifically ask the runner to do a 5K race. 

The 5K distance is preferable to other standard race distance in a number of ways. For starters, it’s by far the most popular race distance, so it’s usually no trouble to find a local event to do. Additionally, a 5K race is more doable for runners at all levels of fitness. Many beginners can’t even run 10K, let alone race that distance. Even advanced runners, meanwhile, need less recovery time after a 5K than they do after a longer race, so jumping into a 5K for testing purpose is less disruptive to the flow of training.

Finally, I find that a 5K race result generally offers a more reliable basis for prescribing appropriate target training paces than do results from longer events. That’s because both aerobic and anaerobic fitness factors contribute to 5K performance, whereas anaerobic factors make very little contribution to performance at 10K and up. A 5K performance typically gives me a good sense of where to start with an athlete pace-wise with everything from short repeats at 1500-meter race pace to sustained steady-state efforts.

So, if you want me to create a training plan for you, be prepared to give me a recent 5K time—or to jump into your next local 5K!

Exercise scientists have two basic ways of measuring performance in their studies. One is a time trial, where subjects are asked to cover a specified distance in as little time as possible (or cover as much distance as possible in a specified amount of time). The other is a time to exhaustion test, where subjects are required to sustain a fixed work rate (speed or power output) as long as possible.

In the real world, most runners approach most marathons as time trials. In my coaching role, I generally advise runners to take this approach because it offers the best odds of a satisfying outcome. The idea is to choose a time/pace goal that is challenging but realistic, start the race at this pace, and then make adjustments along the way based on how you’re feeling. The advantage of this strategy is that it limits the risk of hitting the wall. When a runner is even slightly too aggressive in the early part of a marathon, he is likely to slow down precipitously in the later part and consequently fall not seconds but minutes short of finishing the race in the least time possible—if he finishes at all. To avoid “wasting” a marathon (not to mention the months of preparation leading up to it), a runner must be a little conservative, choosing a target pace that he’s very confident of being able to sustain for the full distance and relying on a fast finish to avoid leaving time on the table if it turns out that the target pace is a tad too conservative.

This fall, Eliud Kipchoge will make a second attempt to break the hallowed two-hour marathon barrier. He got very close in his first attempt, covering 26 miles, 385 yards in a time of 2:00:25 in Italy in 2017. Of necessity, Kipchoge approached this bid to make history not as a time trial but as a time to exhaustion test. Aided by a phalanx of pacers, he set out at 4:34.5 per mile (1:59:59 pace) and held on as long as he could, which turned out to be about 18 miles, at which point he began to slow involuntarily, despite his best efforts to hold the required tempo.

In his second sub-two bid, which will take place in late September or early October, Kipchoge will take the same approach, as indeed he must, for such an ambitious goal cannot be achieved in any other way. Avoiding the wall is not a concern, because anything short of sub-two is failure. Whether Kipchoge hangs on almost all the way and ends up clocking an excruciating 2:00:01 or blows up at 35K and literally crawls to the finish line, the two-hour barrier will remain in the realm of the impossible for the time being. Thus it makes no sense for Kipchoge to adjust his pace as he goes based on how he feels. If 1:59:59 (or better) is indeed possible for him, he will only get there by forcing himself to hold that 4:34.5/mile pace no matter what.

My (possibly politically incorrect) term for a marathon that is run as a time to exhaustion test is kamikaze marathon. Inspired by Eliud Kipchoge, I have decided to run a kamikaze marathon of my own this fall. A sub-two-hour marathon being slightly out of my reach, I will attempt to sustain a pace of 6:04 per mile as long as I can in the context of the Pacific Northwest Marathon on September 21. The fastest pace I’ve ever sustained for the full marathon distance is 6:05 per mile, at the 2017 Chicago Marathon. I was 46 years old then and am 48 now, a difference that is far more consequential as it relates to performance decline than is, say, the difference between 36 and 38. What’s more, I spent the summer of 2017 living in Flagstaff and training with Northern Arizona Elite, a huge advantage that I will be lacking this time around. In consideration of these facts, I think I’ve got about as much chance of achieving my goal as Kipchoge has of achieving his, which is to say close to none. But that’s the whole point of a kamikaze marathon. You choose a goal time that you think is probably-not-definitely impossible for you and go for it! If you plan and execute appropriately, there’s about a 90 percent chance you will implode painfully in the late miles of your chosen race and a 10 percent chance, give or take, that you’ll achieve something special that you would not have been able to achieve with the usual time-trial approach.

So, what do you say—are you in? Before you blurt, “Hell, yeah!”, understand that Kamikaze marathons are appropriate only for seasoned marathoners who don’t mind possibly “wasting” a marathon. But if you fit this description, do consider joining Eliud Kipchoge and me in running a kamikaze marathon this fall. Put some thought into coming up with a time/pace that is probably-not-definitely impossible for you and then find an appropriate event. (I chose Pacific Northwest because the course is net downhill and mostly flat and the weather is reliably perfect every year—oh, and because my brother Josh is running it). Also consider recruiting a pacer who can easily run the time you’re hoping to run. Tommy Rivers Puzey, a 2:16 marathoner, has agreed to serve as my pacer (though there’s a chance he’ll have to bail out at the last minute due to sponsor obligations).

If you accept the kamikaze marathon challenge—and I hope you do—be sure to share the journey (Strava, Twitter, etc.) as I will be doing in the months ahead. Let’s make this a thing!

Most runners target a single intensity in all of their workouts. Either it’s an easy run or long run at a slow and steady pace or a tempo run with an effort at lactate threshold intensity sandwiched between a warm-up and a cool-down or an interval session featuring a set of a certain number of repetitions of uniform length or duration all done at the same high intensity or—you get the idea. But there is something to be said for doing the occasional workout that includes a range of different intensities.

First of all, multi-pace workouts are a literal change of pace, and as such they’re an effective way to keep your training fun and interesting. Multi-pace workouts are also a good way to get appropriate doses of different intensities. For example, if you’re at a point in your training where you can benefit from a little work at VO2max intensity—but only a little—why set aside an entire workout for it when you can incorporate that work into a session focused on an intensity you need more of—say, lactate threshold intensity?

Yet another benefit of multi-pace workouts is that they help teach effective pacing. Can you shift accurately from half-marathon pace to 10K pace to 5K pace by feel? Most runners can’t, but runners who do workouts that include efforts at all three of these paces can. Finally, multi-pace workouts that put the fastest work at the end develop the capacity to dig deep and finish strong in races.

Here are three multi-pace workouts to try:

3 Multi-pace workouts to try

Intervals + Time Trial

This type of workout serves most of the purposes mentioned above. The interval segment provides the primary training stimulus and it should target a high aerobic intensity close to the lactate threshold. The closing time trial should be fairly short in order to serve the purpose of providing a modest exposure to VO2max and to get you suffering a bit. As a whole, an Intervals + Time Trial workout is very taxing and you shouldn’t attempt them very often. The specific session described below is one I did with NAZ Elite during my time in Flagstaff.

1-3 miles of easy jogging

Drills and strides

7 x 1 km @ lactate threshold pace with 1:00 standing recoveries (2:00 after the last rep)

1500-meter time trial

1-3 miles of easy jogging

30-20-10 Run

A few years ago, a team of Danish researchers led by Jens Bangsbo set out to see if they could come up with a high-intensity interval workout that was more enjoyable than standard formats without being less effective. They tested a variety of designs before settling on one that fulfilled their hopes: the 30-20-10 Run. After learning about it, I gave it a try, made a couple of tweaks, and started incorporating the workout into the training plans I create for my clients. I like to schedule 30-20-10 runs during recovery weeks and during the final weeks of preparation for longer races as a way to expose athletes to a range of intensities without making them go to the well. This workout is also a great way to teach better pacing. Here’s the basic format:

1-3 miles of easy jogging

5 x 1:00 with the 30 seconds at marathon pace, the next 20 seconds at lactate threshold pace (i.e., the fastest pace you could hold for one hour), and the last 10 seconds at a relaxed sprint. No recovery—just cycle right into the next interval until you’ve completed all five.

Complete three cycles of five 30-20-10 intervals with 5 minutes of jogging after each.

1-3 miles of easy jogging

Tempo + Sprints

As a long-distance runner, you should sprint, but not a lot. Because any sprinting you do in a race is likely (one hopes) to occur at the very end of a race when you’re tired, it makes sense to sprint on tired legs in training. In the Tempo + Sprints workout, you will do just that.

1-3 miles of easy jogging

Drills and strides

20:00 at lactate threshold pace

2:00 standing recovery

8 x 200-meter relaxed sprints with recovery by feel (i.e., go again when you’re ready)

1-3 miles of easy jogging

$ubscribe and $ave!

  • Access to over 600 plans
  • Library of 5,000+ workouts
  • TrainingPeaks Premium
  • An 80/20 Endurance Book

 

30 day money back guarentee

For as little as $2.32 USD per week, 80/20 Endurance Subscribers receive:

  • 30-day Money Back Guarantee