Tag Archives: speedwork

The Best Running Technique for Speed

So you want to run fast? Can’t blame you. We all do. I’ve talked about this before but I’ll make a point of it again:

The mistake most people make when they try to run faster than usual, such as in speedwork and in races, is to a) run physically harder, as in put forth more effort, and b) to reach farther with their steps and try to cover more ground with each step.

All the above serves to do is tire you out more quickly, and while this may be great for sprinters who need only maintain this effort for a few seconds… this is not a good way to run a race farther than, say, 400 meters. And pretty much every race you pay to run is a lot farther than 400 meters.

What you want is to maintain efficiency, while repeating your most efficient running motion faster than usual.

Continue reading

Tagged , , ,

Volume: The key to base training

Most training plans, whether or not they map it out, follow at least three general phases.

  1. There is a base training phase, where you establish the volume and habits you will generally follow throughout the training cycle.
  2. There is a fundamental phase, where you develop speed and aerobic endurance.
  3. And then there is the final sharpening phase, where you work more specifically on preparing for your goal race as well as taper to heal up in the days/weeks before that race.

(Some split that 2nd phase into separate development phases, one where the 1st part is speedwork-centered, and the 2nd is built around tempo and endurance with that tempo.)

Most people follow a pre-written training plan, which usually starts with a minimal weekly mileage that gradually builds throughout the plan. The base training may establish an initial pattern of speed/tempo workouts, but the volume typically is low and increases during the life of the training plan.

I do think we get it backwards.

Continue reading

Tagged , , , , , , , , , , ,

Chops: A personal statistic for tracking training volume

Chops

A snapshot of my Google Docs training log, which outlines mileage, time spent in “hard running”, time spent doing hard exercise or similar labor, estimated walking distance, lifetime training miles since 2016, and my personal stat “Chops”, described below.

I keep a Google Doc spreadsheet log of all my training sessions: Mileage, any speedwork mileage, time spent in strength training plus other active/intentional physical effort, and estimated distance walking.

I also track known lifetime training mileage, and a self-created stat called Chops.

Chops is named after the musician term chops, which describes a performer’s current musical skill. Similarly, my Chops number provides an estimate of how many miles I can comfortably run at full strength over the following week.

Continue reading

Tagged , , , , , , , ,

An 8-12 week McMillan-Style 8K training plan that will get you ready

The following is admittedly a variation of a plan Greg McMillan has recommended for 10K training. The plan below is a bit more specific about mileage and off-week workouts, but does allow flexibility.

  • This plan lasts a minimum of 8 weeks and presumes you already run at least 15 miles a week, at least 3-4 days a week, and at least two of your runs are 5 miles or more. It’s ideal if you run at least 40 miles per week, but that’s not necessary.
  • If not, spend 2-4 weeks running at least 15 miles per week, at least 3 days a week, at an easy pace… before beginning this plan. The less running you currently do, the longer you need to work on that before beginning this plan.
  • Don’t begin the workouts below until you’ve run 15+ miles 3+ days each week, without trouble, for at least a couple weeks. Week 1 of the below plan only begins the week after you’re able to do so.
  • Pick a goal 8K pace that is attainable, whether you attained it before or it’s within 15-20 seconds per mile (9-12 seconds per kilometer) of a pace you’ve run at this distance or longer. Don’t pick a pace you can’t hold for at least a couple miles uninterrupted.

Starting in week 1, do the below workout once during each designated week. Ideally, do the workout in the middle of the week, but you can pick any day of the week that works best for you:

Wk 1 – 5 x 1 mile (1600m) repeats, at goal pace.

Wk 2 – 5×400, comfortably hard pace, rest 2min between.

Wk 3 – 4 x 1.25 mile (2000m) repeats, at goal pace.

Wk 4 – 5×400, comfortably hard pace, rest 2min between.

Wk 5 – 3 x 1.67 mile (2700m) repeats, at goal pace.

Wk 6 – 5×400, comfortably hard pace, rest 2min between.

Wk 7 – 2 x 2.5 mile (4000m) repeats, at goal pace.

Wk 8 – No speed workout! All easy running.

If you can nail goal pace in the Week 7 workout, you absolutely will nail your goal time.


  • It’s okay for the mile+ repeat distance to be a little long or a little short. If you can run them on a track, measuring the repeats is very easy (one reason I mention the metric distances!) because every lap in lane 1 is 400 meters, and many competition tracks will mark off start lines in each lane for the correct distances.
  • Obviously, trying to do these repeats on a road or trail doesn’t make measuring the right distance easy. The goal is to sustain your pace for each one, so just pick a stretch of path that’s close to the needed distance.
  • If you find yourself falling more than 10 seconds per mile (6 seconds per kilometer) short of your goal pace during the workouts in weeks 1 and 3, you need to dial back your pace expectations.
  • Don’t do the 5×400 reps at max effort, but definitely give a stride-fast effort. Go fast enough that finishing is tough, but hold back enough that you could keep going another 400 meters after the finish if you had to. Let feel be your guide on these repeats. And yes, 5×400 may not be a lot for many of you. This should be a quick and easy speed workout.
  • Aside from the key workouts, you want to do some easy running at least a couple other days per week, probably more like 3-5 other days per week. The fewer days you run, the longer those easy runs need to be. If nothing else, do an easy run 2 days before the speed workout and 2 days after the speed workout. Otherwise, do whatever easy running you want.
  • Don’t skip workouts unless you’re rather sick, or you’re injured. If you’re not going to do a workout, at least run a couple miles that day.

As always: Eat well, sleep well, every day during this training plan. You are the sum of your habits. Take care of yourself.

Tagged , , , ,

The Yasso 800’s marathon predictor workout: An idea for a simple (and not so simple) improvement on the workout

The Yasso 800’s are a classic marathon predictor workout, where the average/median/whatever of your ten 800 meter reps should correspond to your likely marathon time, e.g. averaging 3:45 per rep indicates you’ll run the marathon in 3 hours 45 minutes. (I’ve previously written some tips and thoughts on handling the workout.)

The workout’s accuracy can depend on a lot of things…

  • How easy the reps are
  • How much rest you’re taking between reps
  • How closely your reps are to your average rep time, whether all your reps are the same or if they’re all over the place
  • Whether you hold steady throughout the workout or get slower as it progresses
  • And of course how adequately trained you are to run the marathon distance

Of course, it’s a bit crude as a predictor. From common sense, how can a series of 800 meter repeats predict how you will run for 42,195 uninterrupted meters, 3-4 weeks later? The workout doesn’t match the race in any way. You certainly won’t run the 800’s at the same pace you plan to run the marathon (BTW if you did, and manage to match your prediction at the marathon… then you certainly could have run the marathon faster). You will likely run the Yasso 800’s at something close to 5K pace, while your marathon pace will be closer to a sustained moderate effort.

But let’s be real: It’s very difficult to predict how your training has prepared you to run your upcoming marathon. There’s no real adequate predictor workout for the distance, because the distance itself is beyond most human capabilities. You can easily run the distance of a 5K in a workout. You can’t reasonably run a 26 mile workout unless it’s a long run, and few will run that far in their longest runs. It’s very hard to do.

Bart Yasso‘s workout is a somewhat reliable approximation of what runners can do. It’s based on his vast experience, and how the relative effort in the 800’s indicates the corresponding pace at which you can run a marathon when adequately trained. His workout came about from finding a clear correlation that proved largely true for most trained marathoners who successfully attempted the workout. It does match up for many, even when for various reasons it doesn’t match up for others.


I think there’s a better, more accurate form of this predictor workout. But it requires more discipline and is of course more difficult… even though the format is a lot simpler:

  • Run an 8K with your best even-paced effort.
  • Divide the time by 10.

That’s the marathon prediction.

The premise: The Yasso 800 workout consists of 10 reps of 800 meters. 10 multiplied by 800 is 8000 meters, aka the exact distance of an 8K.

The key difference in this 8K workout is that you’re removing all of the rest breaks, and running every inch in one uninterrupted go.

The hard part of course is that maintaining a steady pace in an 8K becomes a lot harder. It’s important that, like running a good workout rep, you don’t necessarily race the 8K as you normally would. You focus on maintaining a steady effort that at the finish line you could theoretically continue running for a few more miles.

In effect, it’s like an 8K run at 10K pace. Or, to brutally simplify it, it’s one 8000 meter rep at 10K pace.

The Yassos are broken into 10 more easily manageable reps. It’s a lot easier to maintain your pace for 3-5 minute bursts than to figure out and hold a suitable pace for 30-50 minutes. You have to know how fast you intend to go, start at that pace, and then ensure you hold it until you cross the finish.

But you’re already planning to do that at the marathon, right? Ideally (though many best laid plans get laid to waste on a marathon race day), your plan is to run at your chosen pace for all 26.2 miles. If you can hold a pace for 26.2 miles, why should a slightly faster pace over 4.971 miles be all that tough?

 


I realize 8K pace is substantially tougher than marathon pace, and that’s one reason I suggest running an 8K test at something closer to 10K pace… along with bearing in mind that you may have a tune-up coming up or having just passed, and that you are after all in the final phase of training for a marathon. You don’t want to kill yourself trying to run a baller 8K that’s not your goal race.

I realize a key element to the Yassos is that you get to stop and rest, minimizing the strain of running those 8000 meters at a fast pace. I realize that if you run an 8K, you’re possibly going to run a slower pace than you ideally would for Yasso’s, which typically can be done at 5K pace.

But here’s the key, stated as a rhetorical question: Wouldn’t that make an 8K time divided by 10 a more accurate prediction? Many say that Yassos tend to predict about 5-10 minutes fast. Many say the Yasso prediction tends to be too optimistic. If you are forced to maintain a slightly slower pace for 5 straight miles… won’t that offer a more possible prediction for your race?

Also, even though it’s not a race specific workout to run an 8K at 8K pace… neither is running 10 reps of 800 meters at 5K-10K pace. What does that have to do with finding and sustaining marathon pace? At least an 8K’s uninterrupted effort is more specific to what you need to do in a marathon (run somewhat hard, without stopping).

And in the Yasso’s, with those shorter reps, it falls into the same trap as most interval speedwork: It’s easy to outrun the workout, and run the reps harder than you would run in a longer race. Give yourself enough rest, or take in enough energy, and you could race 10 really good reps that aren’t at all indicative of what you could do in a 5K, let alone predict how you’d run the marathon.

It’s no wonder so many people find Yasso 800 predictions fast.


I would recommend trying an 8K Divided By 10 (8K/10) test in lieu of Yasso 800’s. In fact, I wish I had thought to do it in past training cycles. I definitely will do it next time.

If you’re doing speedwork, an 8K/10 can replace a speed session for that week, which would still allow you to do a tune-up half marathon the week before or after if desired.

8K races are not easy to find, I realize, like 5K’s, 10K’s and Half Marathons. While reasonably popular, it’s a somewhat odd distance. They come and they go.

Those in Chicago running a spring marathon (like Boston!) could use the Shamrock Shuffle for this. Barring that, a late August or early September 8K could work for the peak fall marathon season (some Illinois towns outside of Chicagoland do offer late September 8K’s).

Outside of that, scour Running In The USA and see if any are available nearby within 3-5 weeks of your goal race. If not, I challenge the RAM Racings of the world to put one up if there isn’t one available in a given area.

Of course, the easiest way to make an 8K test happen is the hardest one to find the discipline to do: Map out 5 miles, and run it out yourself… or go find a full size track and knock out 20 laps in one go. I’ll be frank: If you have the discipline to train for and run a marathon, you should be able to find the discipline to make yourself run an 8K on your own at 10Kish pace. If that’s what it takes and you want to try this, I have faith in you.

No matter how you do it if you dare… run at 8K, divide your finish time by 10, and that’s probably as good a prediction of your marathon time as any Yasso 800’s workout could give you.

Tagged , , , ,

Some Keys to the Yasso 800’s

The basics of the Yasso 800’s:

The Yasso 800’s is used as a marathon predictor workout, about 3-4 weeks before your goal marathon.

You run 10 reps of 800 meters all as close to the same pace as possible. The average pace of the reps should correspond with your potential marathon time.

For example, if you can consistently run the 800 meter reps in 4:05, that indicates you can run the marathon in about 4 hours 5 minutes max.

Some experienced marathoners find this estimate is fast by a few minutes, which is why I refer to the estimate as a max.

The standard caveat regarding runner ability:

A lot of what I’m about to say below assumes you’re not a hardcore runner logging elite-like volume (70+ miles per week).

When you’re pumping out 70+ miles a week, you probably already run high-volume speed workouts like this on a regular basis, and can probably run the Yasso’s at a strong pace, such as your 5K pace or better.

For experienced runners relatively new to the marathon:

The more volume you run per week, and/or the fewer marathons you’ve done, the more you should scale back the Yasso projection.

e.g. if you run 100 miles a week and can run 800’s in 3:05, maybe estimate something closer to 3:20 for your marathon. Or if your 20 mile long run is the first time you’ve ever run 20+ miles, scale those 4:15 Yassos back to a 4:30 projection.

You should already be running a lot of miles.

If you’re training for marathon, you should be logging more than 20-30 miles a week during training. Probably way more.

40-50 miles is probably the minimum during marathon training that will produce a good marathon effort, assuming you don’t already do several marathons a year.

Personally, I feel a lot of self doubt having run 30-50 miles per week, even though many would say I’m in pretty good shape to run my next marathon (while many experienced runners would say I’m not even close).

Speedwork is not a race. Don’t run the reps like a race.

As with any interval workout, you should not race these reps: Don’t do them hard. Don’t pick up the pace and “kick” at the end of the rep.

Run every rep with a steady effort wire to wire, where once you finish you could run another few miles at that exact pace if you had to.

The reps in the Yasso workout are supposed to be a barometer of your capabilities. Running closer to your max effort will not give an accurate picture of those capabilities.

These Yasso paces should be easier than running a 5K

According to most reliable pace charts (Daniels, McMillan, etc)… you should be able to hit a desired Yasso goal at about your 10K pace or slower.

If you give more like an 8K or 5K effort to hit your pace on these reps, not only may the workout be inaccurate, but (unless you run 100+ miles a week and do workouts like this all the time) you probably won’t maintain the stamina to nail that Yasso 800 pace consistently for all 10 reps.

The fewer miles you run per week, the longer your rest breaks should be

If you don’t run 60+ miles per week, you probably shouldn’t run these like VO2max intervals, where you take a shorter 1-2 minute break between reps. In fact, many go wrong with this workout by following a semi-bastardized version of this workout where they take more typical weekly-track-group-style 1 minute, 90 second or 2 minute breaks between the reps.

Two problems with this:

  1. The original workout was meant to be fully run, meaning that during the recovery periods you were to jog… not to come to a complete stop. By stopping, you give yourself enough ATP recovery to run the reps harder… which can throw off your final times and subsequent estimate (this is a key reason many find their Yasso result was too fast).
  2. Whether or not you jog the recovery intervals, the recovery periods are too short for most people. It makes the subsequent reps more difficult than they were designed to be, which creates inconsistent rep times and in turn an erratic estimate.

Instead, you should follow Bart Yasso’s original rule and take a rest break equal to the amount of time it took you to run the last rep. This should often exceed 2-3 minutes and reflect the kind of rest you’d take after a harder, closer to all-out rep.

Obviously, with longer rest breaks, you will want to make sure you block off a lot of time to do the full Yasso 800 workout, since between your warm-up, the repeats themselves and the longer rest breaks, followed by a smart cool-down… this workout could take at least 90 minutes, if not longer.

If you run 60+ miles every week, however, you most likely do 8K worth of speedwork reps all the time. It’s probably the reason you even thought to do this workout in the first place. Then, by all means, take shorter rest intervals of 1-2 minutes. Do what you’ve typically done in past workouts. But for most, following Yasso’s original advice is sound.

How easy is your active recovery period between reps? That matters.

If your inter-rep recovery is a jog instead of a full rest, the following is a good barometer of whether or not you’re going too hard: If you need to walk or stop, you went too fast.

If your version of the workout allows a full stop to rest, then a good barometer of whether you went out too hard: You cross the line not feeling like you could have kept going another 800+ meters at your pace.

Again, you never want to race to the finish of these reps, reaching the line needing to stop for a total rest. Run wire to wire at a pace you’d expect to maintain in a race, meaning you should cross the line able to keep running at that pace if you had to.

If at first you can jog your recoveries… but then you need to walk or stop at later recovery intervals, it’s not only possible your intervals are too fast… but also possible that your recovery jog was too fast.

Many runners mistakenly pace their recovery jogs at more of a normal running pace. This is too fast. These recovery jogs should be super easy and casual. Imagine you’re working yourself back from a leg injury and you’re doing a test run just to get back in the swing of things. That’s the pace and effort you should put into recovery jogs.

Another analogy I find accurate is to observe a baseball hitter’s home run trot: That’s the effort you want to be putting into a recovery jog.

The key reps are the reps BEFORE the last one.

Pay close attention to the results of reps 7, 8 and 9. In fact, you could average just those three reps and may get a more accurate Yasso 800 estimate than estimating the average of all your reps.

It’s your performance while tired in the later reps that paints the most accurate picture of your capability. Bear in mind the tendency many runners have to do the final rep hard in an effort to finish the workout strong. Rep 10 will probably look stronger than the other later reps.

Pay closer attention to how reps 7, 8 and 9 look, where you’re tired but not emptying the tank with a final flourish because you know you still have more reps to do.

Another effective estimate: Take the average of your 5 slowest reps.

Few can fake 6-10 good, accurate reps.

If the pace of your individual reps varies substantially:

(let’s say by more than 15 seconds between your fastest and slowest rep):

1. Most likely, you went out too hard. For most runners their reps in a speed workout typically vary like this: The first reps are very fast, then later reps are much slower.

2. In some cases you may start your reps super easy, realize you have more in the tank than expected, then pick up the pace in later reps (like a negative split in a race). Along with being a psychological tendency among runners… this can indicate you didn’t warm up effectively beforehand.

3. If your rep times consistently bounce back and forth by 12+ seconds per rep, you are either trying (at least on some reps) to hit a pace you’re not totally capable of running in a race… or you’re not taking full rest periods. If you’re in the middle of a Yasso workout and you see your times bouncing around, focus going forward on running a comfortably brisk pace that’s a tick slower than you want to run (whatever that means to you), and try to hit the same pace on the remaining reps.

Tagged , , , , , ,