Another Thirty Days of Running

I’m not exactly sure when I was first introduced to the concept, I think it was during a month long training camp on Lanzarote back in 2009. Following a disastrous race I returned from the island willing, or perhaps sufficiently desperate, to try anything in the pursuit of better performance. Many changes followed, it would be hard to pin subsequent successes on one, but thirty days of running remains strongly associated with a breakthrough. A simple idea: a handful of rules necessitating consistency.

April's Challenge: thirty runs of at least thirty minutes over the thirty daysThirty runs of at least thirty minutes in thirty days.

The appeal was obvious, I liked the rules, I liked the simplicity and I liked the symmetry around thirty. I knew there was nothing special in this number, it was an arbitrary choice, about a month of regular running without interruption. Focussing on frequency, its significance came in the form of discipline, demonstrating a willingness to just keep training. Tired, hungry, wet or miserable – I would still have to go out and put one foot in front of the other. But there was nothing to stop me running further or faster should I feel inclined.

Of course I adopted a hardline approach: I had to run – or at least run/walk – every day and it had to be for at least thirty minutes. There was no banking extra runs to earn a break, I could run once, twice or even three times in a day and I would still have to run the day after. There was no dividing the time, I couldn’t top up a twenty-five minute run in the morning with five minutes in the afternoon, thirty continuous minutes, one after the other. There were no free passes. Break the rules just once and the game was over. Awareness of the impact of training became heightened, the choice to train harder or longer having added implications in light of the need to be consistent; the benefits of frequency and consistency balanced against those of intensity and duration.

Challenges are part of my motivational repertoire – trying to go further or faster, or increasing rank on a Strava segment; chasing small milestones on the way to bigger things. Thirty days of running laid out a new template that came to define many periods of training; not necessarily optimal, but whenever motivation waned, effective. Forty kilometres of swimming in a week, fifteen in a day, forty days of cycling, or riding the length of a country in two weeks, the same pattern – a given workload in a given time. Simple, easily measured targets – how far, how often, or how long – no real pressure, just switch the brain off and train.

The concern, of course, is of injury or perhaps junk milage. Certainly injury is a genuine risk, any form of excessive overload can present it, and potentially this is excessive. I jump into a challenge carefully, when I feel I am ready, I measure out my effort over the timeframe, and I accept that at any sign of injury I will abandon my goal. And junk mileage? Sometimes the training is slow or easy, but it can be hard, or long, or any other combination that strains my body. There are quality sessions, and then on the days when I might have rested, I train again. There may be more effective, more targeted approaches, but when I am becoming bogged down in the minutia of a plan, this works – I can simply enjoy training; a few sessions that some might term ‘junk’ is a small price to pay for the overall gain.

So the first of April – a month of thirty days – in a year when, lets be honest, my motivation is not at its peak is the perfect time to play the game once more. Thirty runs of at least thirty minutes in thirty days. I will run every day in April, even a second weekend of birthday celebrations for my girlfriend didn’t stop me completing run number one; it was slow and I did have some concerns about my stomach, but I started as I mean to go on.

How to Plan a Season Using the Performance Management Chart

The plan is working. Day one I did do a little more than intended, but with great weather and an opportunity to meet up with one of my athletes, I couldn’t resist; day two compensated as I did a little bit less than planned, my legs were feeling the previous extra effort; today I’m sticking to the plan as it’s only a short session. The flexibility is there and I know not to race ahead of schedule, the urge to cram in more is under control. A good start, but I’ll save declarations of success for three months down the line, rather than three days.

On Wednesday I planned a year of running in the form of a Performance Management Chart (PMC). By managing my weekly training schedule to replicate this intended growth in fitness I should avoid many of the pitfalls from previous seasons without being tied to a rigid timetable. Obviously I also need a plan for cycling (and I should do one for swimming too), so on a clean copy of the spreadsheet I repeated the process.

For those interested in trying this, or in seeing how their current plans line up, I’m going to walk through how I plan with the PMC and have provided a copy of the spreadsheet at the end of this blog.

Everything hinges around Training Stress Scores (TSS), the PMC is built on these after all. Every workout can be assigned a Training Stress Score, it’s calculated from intensity and duration of the session, the longer or harder you train the higher the TSS. Software like Training Peaks can do this automatically from uploaded data files, it weighs the relative intensity of every second to produce a figure. Different workouts will have different TSS and you can achieve the same TSS in many different ways; it is simply a value that attempts to give some indication of the impact of training. So to plan ahead with the PMC we need to estimate the TSS of every session we intend to do.

  Estimated TSS per hour
Easy bike 20 – 40
Steady bike 40 – 60
Tempo bike 60-75
Intervals (including recovery) 75+

I’ve developed a sense for the kind of TSS a session will score. There are no set rules and it takes time and experience to develop a good impression of the scores you will likely produce. Some sessions are harder to estimate than others – intervals alternate between the high scoring work and the low scoring recovery, add enough hills into a long ride and similar variability can be there. However experienced you are with the PMC this is not a precise art, but the approach to planning I’m describing here is not intended to be precise.

Performance Management Chart - Setting Seed Data

If you download the spreadsheet the first thing you will need to do is set up some seed data for the PMC algorithm; you’ll find the ‘Seed Data’ sheet at the far end. There are three values in particular we are concerned with – a start date, a starting ATL (fatigue) and a starting CTL (fitness). You can pick any start date you like, the spreadsheet plans for 53 weeks from that date. Dates are only specified to help build the plans from a calendar. The starting ATL and CTL values are a little more complex, for those already using the PMC, set them to the respective values from the day before your plan’s start date. Those who have never used a PMC (and have decided to play with this) should read this information on getting started to help choose values appropriate values that reflect their level of training.

Performance Management Chart - Estimating TSS

Now our estimation skills come into play. For each day on the PMC Data table we can enter a TSS value to represent the training we intend to do, this value will feed into the algorithm and predict fitness and fatigue. I’ve shown my plans for the period around Ironman 70.3 UK and leading the Pyrenees Multisport Iron Camp at the end of June. As the camp itinerary shows there will be a lot of hard riding over the week, so I’m expecting high duration and moderate to high intensity which means some high TSS. From my table of estimates I’d anticipate sitting in the 50 – 70 TSS per hour region, high for me on long days of cycling. Working around known events and with a rough idea of the sort of sessions I’m likely to do I can fill out the entire table; hard days and long days scoring higher TSS than easier days, and rest days scoring none – allocate these out and a chart develops.

Performance Management Chart - 2012 Season Bike Plan

Once again a plan of action in the form of a chart. Reviewing the chart allows me to refine the plan, eliminating periods of overly rapid growth, preventing TSB (form) dipping too low and ensuring I don’t go fallow for too long. As with the run plan I take lessons from the past, while I’ve sustained higher fitness before, doing so often came at a cost and the time involved is incompatible with the run plan. By avoiding rapid spikes in fitness and following a gradual path to greater fitness I should be more consistent across the season. It’s a realistic approach that fits with my available time.

Performance Management Chart - Summary of Planned Weekly TSS

One final chart from the data – total weekly TSS from the plan. Summing the estimated TSS for each week gives an easier figure to follow and target as I attempt to put this PMC into action. It allows me greater freedom within the week, so if my high TSS long ride was scheduled for a Monday, but a Tuesday works better I can just change it; within reason as long as I target weekly TSS I should be on track with my PMC.

So I have plans now and it does seem targeting a weekly Training Stress Score incentivises me, at least so far. For those unfamiliar with the Performance Management Chart this may seem an abstract and convoluted way to work, but on a personal level it fits my needs; for those who use the PMC and haven’t attempted to plan with it before, it can be a useful tool, providing a simple sanity check on your training. At the end of the day it’s just another way to approach planning training.

If you want to build your own Performance Management Chart you can download an excel copy of the PMC Planner.

An Overview of Season Planning using the Performance Management Chart

Perhaps it’s the weather. As I basked in the sun on the homeward leg of my early morning run I had a thought, “maybe I can race well later this year.” The arrival of an unusually warm spring has broken the negative cycle – my mood is lifted and my desire to train, specifically to run, has returned with full force. And so positive thoughts arrive, the idea that perhaps I can be both fit and capable of racing well enters my head, only compromised by the knowledge that it will take some time and some planning. The path ahead is littered with events, too many to hope to be on top form across them all. I need to take the smart approach, utilising races as part of my development, rather than an end in themselves, stepping stones to greater things.

I suffer from an allergic reaction to strict training schedules, and while there is a strong case – one that made me stop and think – for the benefits having my own coach would bring me, it’s not something I want to pursue right now. But I need something more than loose guidelines to make the longer term transition to greater fitness, something that appreciates the impact of my heavy race season, using those events to build me, not break me. Rather than limiting my use of the Performance Management Chart to retrospective training critiques, I can use it constructively to manage this coming year; utilising my experience of the system to set training targets and a rate of growth for the weeks and months ahead. Perhaps it seems at odds with that desire to train for pleasure, but there are many ways to achieve fitness growth.

I’ve dabbled with the approach before – planning tapers or testing out ideas for a build; manipulating the underlying values of the model to see the effect different work loads are likely to have. It’s a matter of trial and error, adjusting those numbers to produce the pattern I want. At this point I am guided by experience, those times I’ve analysed historical PMC data actually come in useful as I avoid my previous mistakes and attempt to replicate the successes. I tweak until I produce a pattern I like.

Season Planning: 2012 planned run Performance Management Chart

By now a familiar chart, but this time the product of good intentions. Reviewing the last four years of run training showed 2009 to be my most successful season, a race heavy year much like the one ahead. I achieved it through a consistent, moderate training plan, 30 runs of at least 30 minutes in 30 days forming a large part of it; I could take that consistency, without excessive overload, and apply it again. Firstly building up through April – perfect for thirty days of running – then maintaining the run fitness from race to race, my work then being to minimise fitness loss. There isn’t time to chase high peaks of fitness, 2010 has taught me the danger of building too rapidly; the volume of running this pattern suggests is a sufficient challenge after a season out of running.

It sounds like a plan, albeit an abstract one defined by the shape of a curve rather than the details of sessions; and it’s that abstraction that gives me the freedom I desire. The curve is the product of a training load deliverable through whatever (sensible) combination of intensity, duration and frequency I desire and I’ve already indicated my preference for a repeat of the high frequency, mixed duration and intensity approach to run training that worked well in 2009. As long as I accumulate a sufficient training load each week my fitness will progress in line with the chart, within reason further details don’t matter; my training is flexible to match my moods.

Finally I’ve found some much needed direction and – perhaps – a way to guide myself towards this goal without feeling overly restricted by a plan. I may not have written a single session down, but I know the kind of work I need to do; starting in April with thirty days of running at least thirty minutes.