Training (mostly) slow to race (kind of) fast

Physiological adaptations to 80/20 running: the data

DISCLAIMER: This post is a short case study on my personal data. I wasn’t blessed with much athletic talent, but I am really passionate about running and data science, which is what motivated me in the first place to build HRV4Training, a platform to measure and interpret physiological data. You will not read about any world record, but decent improvements backed up by solid data, and hopefully it will be useful to some.
10 km PR and 5th place at the Fort to Fort 10 km run organized by the DSE running group. Special thanks to all the good runners for not showing up, so I could get my ribbon. If you are in the bay area, check out this running group, they organize 5 to 10 km runs weekly, for only 5 USD.

The research

Training slow to run fast(er) might seem counter-intuitive, however quite some research in the past 15 years showed how elite runners (and not only runners) spend much of their time training at low intensities (see Stephen Seiler’s work). Following early research, interventions have been carried out to randomize runners in groups including a greater amount of low intensity training, and groups including more moderate intensity training. Results showed consistently improvements in running performance for groups training at lower intensities for most of the time, typically 80% of the overall training load. Many runners, coaches and authors have been preaching low intensity training for years, under slightly different guidelines, but all following the same core principles (see for example most of Phil Maffetone’s work — the 180 formula, MAF test, etc. — and more recently 80/20 running by Matt Fitzgerald, who also wrote this nice piece on the topic on RunnersWorld). We also ran an analysis of HRV4Training users generated data highlighting how faster runners tend to train at lower intensities, check out this blog post for the full story.

The problem with the average recreational runner is that we tend to get stuck into too much moderate training, having hard time recovering and increasing training volume as well as being more prone to injuries.

I was exactly that kind of runner. After some initial progress mainly due to basic adaptations to running as a sport, I’ve spent the past five years stuck with zero progress in running performance (sometimes inevitably as life got in the way). Last summer I’ve started reading more on running and I eventually decided to give this different type of training a try. Surely I was running slow trainings before as well, or at least I thought I did, but things changed a lot when I started with 80/20 running.

Below I’ll go through my data and provide a few tips on tracking adherence and progress as well as show physiological adaptations in both resting measurements (heart rate and HRV) and heart rate during workouts.

Trying it out

To get started with low intensity (or 80/20) running you really need a heart rate monitor. Our perception of what is low intensity in terms of pace is most likely too intense physiologically speaking (see first plot below). Once you have a heart rate monitor, defining what is low intensity for you can be done in many different ways, a simple one is Maffetone’s 180 formula, or you can do 70% of your heart rate reserve added to your resting heart rate (so your threshold would be 0.7*(HR max — HR at rest) + HR at rest, in my case 0.7*(194–50)+50 = 150 beats per minute). Different methods will give you similar results, the point being, that’s the low intensity threshold for your runs.

Here is how it went for my first few runs since I switched, about 6 months ago (August 3rd, 2016):

What you can see above is pace over time. Light blue dots indicate trainings after I started with 80/20 running, the dot size is my average heart rate for the run, so you can see it gets smaller as I start 80/20 running, as I was trying to stay below threshold. The circle indicates my first 80/20 training, a.k.a. the slowest training in my life. There are still bigger dots at faster (smaller numerically) pace, as quality work (tempo, intervals) is still present.
The first run was so slow, that it ended up being my slowest training in 7 years since I started running.

It definitely took some patience and commitment at the beginning.

Tracking adherence

I made a couple of plots to track my adherence to this training program. As you can see below, there is much more low intensity work in the second part of the year, which confirms that before I was basically always going too fast/intense (very few light blue dots on the left):

Same data as above (pace over time, dot size this time is the inverse, so bigger = lower heart rate) but for the entire year. The dot color this time is determined based on my average heart rate for a workout being either below or above the pre-defined threshold of 150 beats per minute.

Similarly, we can look at the heart rate distribution for my data before and after August, showing again a much lower intensity (lower heart rate) for my trainings after starting 80/20 running:

Running below threshold often turns out as running at threshold, as we can see from the second distribution peaking at 150 bpm, but that’s good enough for me :)

Even more revealing is the maximal heart rate plot. In this one I plotted my heart rate max for any given training, before and after starting 80/20 running:

Apart from potential outliers (HR max >200 bpm), in this plot we can see that 1) I was getting close to my maximal HR basically in each training before I started training at low intensities — i.e. always too intense 2) after starting low intensity training the distribution gets bimodal, we have two main peaks, which quite clearly separate low intensity trainings and quality work (tempo, intervals).

The plots above show you how you can keep track of your trainings and making sure you follow the 80/20 or mostly low intensity training. The main question I had however was another one, as I knew I was sticking to the plan, was I making any progress?

Making any progress?

Low intensity training, especially at the beginning, can get frustrating (and boring) as you force yourself to run very slowly. Be patient. Physiological adaptations such as increasing your aerobic fitness take time in the order of months, not days, especially if you are already used to training/running.

Racing short distances regularly to track progress is an option, but also can be a big disruption in training and stress on the body. The end game is improving racing performance, however there are other simple ways to track progress as we go.

In my opinion a good approach is the MAF test, which consists in running at your threshold heart rate (same you picked for your low intensity trainings) for 1 mile, check the time it takes, repeat every month or so. By keeping two parameters constant (your heart rate and the distance you run) you will be able to track progress as it will take less time to cover the same distance at the same intensity. I do this for 1 km before my interval sessions as I am rested (I take the day before off) and I function on the metric system, but it’s pretty much the same thing.

Alternatively you can simply check your typical low intensity run. As creatures of habit all runners tend to often run the same routes, so pick the one you run the most often, and check if your pace gets better over time, at the same threshold heart rate. Here are my pace and heart rate for my most typical training, a 10 km, 110 meters elevation gain “recovery loop”:

A couple of points from the plot above: pace decreased (higher values in the plot) dramatically when I started the 80/20 running. However, as aerobic fitness improves and your body adapts, pace started increasing again (lower values at the right end side of the plot), highlighting improved fitness. There is a gap in the data as I was in Europe in September/October and I couldn’t run this route.

It’s important to use always the same route as you want most parameters to remain unchanged (elevation gain for example). Clearly other factors will also have an impact over long periods of time, for example temperature, yet this is the most practical way I found to track my progress. As heart rate on a daily basis can be affected also by many other parameters (training, stress, etc.), I would recommend using a route that you run weekly, so that you can have more data points and can spot trends instead of just noise in the data.

Without the need to go through the trouble of creating the plot above, an easy way to track progress on your most common route is simply to go on Strava, and check your pace and heart rate columns, as they already match all your runs on the same route for you:

Here the pace plot is the other way around with respect to mine, however you see the same, which is a much slower pace the day I started 80/20 running, highlighted in the plot, and then slow improvement over time. It’s important that you check only trainings with a HR below threshold, as you cannot filter out faster trainings you might be doing from time to time on the same route.

Physiological adaptations

I’ve shown already above some physiological adaptations as a way to track progress, as pace at the same intensity (heart rate threshold) will slowly get faster. These adaptations are mainly due to improvements in aerobic capacity, however, I’ve seen much faster changes in resting physiology.

Below are my heart rate and heart rate variability (HRV) over the past year, measured each morning using HRV4Training:

Heart rate (top) and heart rate variability (rMSSD, bottom) during this year. A reduction in heart rate is typically associated to improved cardiorespiratory fitness. Similarly, an increase in HRV can be associated to higher fitness as well as reduced physiological stress on the body.
The quick reduction in resting heart rate and increase in HRV put my mind at ease as I thought something positive (physiologically speaking) was happening rather fast.
I wonder if these are common adaptations, and I will probably try to understand more about this using HRV4Training’s data. I believe part of these changes might be due to the less overall intensity / load I was putting on my body, which might have been constantly overworked before. Here is another bit of anecdotal evidence in this direction, similar findings from another HRV4Training user.

Two other main adaptations that I believe should show up in most people were quite obvious. Training at low intensity allowed for much faster recovery, you go less hard not only on the cardiorespiratory system, but also on the muscles, less DOMS (delayed onset muscle soreness), etc. which in turn allowed me to increase significantly training load, something I’ve always struggled with (50% more running in 6 months, from 30–35 km / week to 70+ km / week, peaking last week with 92 km and a 37 km run at 5:04 min/km). Below you can see chronic and acute training load over time (also available in HRV4Training):

Chronic and acute training loads are computed on 42 and 7 days moving windows, according to the Banister model.

These data are particularly interesting especially when we look at them together with resting physiological data. Both heart rate and HRV show signs of reduced stress (high HRV and low HR) while training load was significantly increasing. This might be an effect of the more polarized training as the body is given more time to recover, due to all the low intensity training, with respect to the previous “always moderate” regime.

The second adaptation, that influenced both resting physiological data and heart rate during exercise, is improved aerobic capacity / cardiorespiratory fitness. It took some time to see these changes coming, but they are clear now as in the past month I PR’d all distances from 1 km to the half marathon, peaking with a 10 km in 40:22, something I almost had given up on.

How do we track changes in cardiorespiratory fitness? I’ve done quite some work on this topic during my PhD, the key is to contextualize sub-maximal heart rate. Intuitively, a person that can keep heart rate lower (with respect to her/his maximal) during a certain effort (e.g. running at a certain pace), can potentially perform better than a person that is already maxing out during the same effort (e.g. at the same running pace). In HRV4Training we use the speed over heart rate ratio as a variable representative of changes in cardiorespiratory fitness. We basically contextualize HR at different speeds so that you can track how your body adapts over time, without the need of performing a specific exercise or protocol. Here is how the data looks for my year:

Speed over heart rate for each workout. This parameter is representative of cardiorespiratory fitness and performance.

We can see above that I first plateau, then switch training to 80/20 and slowly build up to being able to sustain a higher speed a the same heart rate, which eventually resulted in my 10 km PR. This plot provides very similar information to the one shown above where we look at changes in pace for the same route when keeping heart rate at threshold (constant), with the advantage that here we can put together all trainings, as heart rate is contextualized by pace.

Closing remarks

Personally, I found low intensity training extremely beneficial in improving performance. I could see physiological changes in resting heart rate, HRV, sub-maximal HR (and therefore estimated VO2max) and improve performance more in these past 6 months than in the previous 7 years of running. These were not the only changes I implemented, for example in the meantime I’ve also adjusted diet and lost some weight. As some of these changes were simultaneous, determining causality is challenging. However, I believe the biggest changes (increased training volume and cardiorespiratory fitness) are mainly due to this more polarized training, and to finally getting out of the “always moderate” training typical of recreational runners.

As I think this was a key aspect in my progress, we will try to bring it to HRV4Training as well, to provide functionalities able to track both adherence and progress similarly to what is shown above, within the app.

That’s all for now. For more on wearable technology, physiological data, HRV, digital health .. Let’s connect on twitter.

EDIT

Training polarization can now be tracked in HRV4Training, see some screenshots below.

Above you can see how my data looked before starting a more polarized training program, when I was stuck in moderate intensity training (always training at way to high heart rates, only 23% of my trainings were easy at that stage), and how it looks now that I mainly train at low intensities (78% of my trainings in the past month are now easy), the last screenshot shows improvements in estimated VO2max following 6 months of polarized training (as VO2max is estimated using as one of the main parameters sub-maximal heart rate normalized by pace, changes in aerobic capacity resulting in the ability to run at low intensities faster, will reflect in improvements in VO2max)
One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.