Finding Your Marathon Pace

Since I am right in the thick of peak training for Shamrock, I wanted to focus on the process of finding your appropriate marathon pace.  I've written before about my thoughts on paces and how to find them, but I want to specifically focus on how you should go about to not only think you have the right pace, but confirm it. 

Now, finding your marathon pace is not some magical calculation that some app is going to spit out for you (although it is used for part of the process), and just because you've found your correct pace doesn't mean that is the pace you'll be able to run on race day.  External factors such as race conditions, course variations, race execution, etc all play into a role.  And unlike most other distances where you can power through to the finish, the marathon doesn't provide much wiggle room for error once you've gone past "the line".  And anyone who has raced (ie pushed your body to the edge) a marathon knows what going to "the line" feels like.  Once you go over, you don't go back.  You merely survive, which in most cases means a combination of slowing down and gritting your teeth till you finally cross the finish.  So my goal here is not to get to the line, but to get right up close and stay there through to the finish. 

This approach only applies to those who are looking to run to their potential.  If you are simply looking to run (but not race) a marathon, then I would recommend running comfortably through 18-20 miles and if you feel like picking it up, go for it.  Your marathon pace is likely to be pretty close to your long run pace.

So with that out of the way, let's get to it!

1) Find a recent race result to get goal paces

Take your most recent race result (must be at least within the last 3 months to be considered recent) as a marker of your current fitness and use one of the many online calculators.  (The key here is using your most recent RESULTS to determine your paces, not what your GOAL is or what your PR from 2 years ago was.  If it isn't recent, it isn't relevant to your current fitness state.  You can't teach yourself to run faster by running at paces that aren't within your level of fitness.  Otherwise, you risk overuse injuries and the inability to absorb the work from training at the appropriate paces.) From those results, you should have an approximation of your potential, which is exactly that - not necessarily what you will run on race day.  If you run to your potential, you will be right at that line, so my recommendation is to take a little off that time.  If you truly use a race result where you put it all out there, racing a marathon to your potential is a risky endeavor.  However, if you want to test yourself, by all means.  As for me, I'm taking a little off and calling it close.

2) Map your training to progressively build toward implementing more goal pace work

What I mean here is this - using the theory of race specificity, we become more race specific as we get closer to the race.  This means that when you first start your training (assuming you are at least 12 weeks out), you will do very little marathon pace running.  You should be running fairly faster/slower, as marathon pace isn't fast enough to give you significant fitness gains, but isn't slow enough to help you become more efficient at burning fat.  So what this means is spending a lot of your faster workouts at your tempo pace (somewhere around 10k-10 mile pace), or your easy workouts running easy.  But as you begin to get closer toward peak training, you shift those tempo workouts to incorporate more marathon paced miles, and also include chunks of marathon paced running in your long runs.

3) Confirm marathon goal paces through execution of key indicator workouts

Including indicator workouts is a fundamental element of properly training for a given race, regardless of distance.  There is no such thing as "race day magic". You've either put in the hard work to know what you are capable of, or you are racing blind.  Sometimes racing blind can yield great results, but I come from a much more structured school of thought (can you tell?!?!?), so I like to know, rather than hope.  Hope leads to false assumptions, and more commonly failed race execution.  When you know, you have guidelines to work from.

Only about 1-2 times during a given marathon training cycle should you include indicator workouts, but I consider this part of the homework of making sure you won't cross over that line in the actual race.  Better to learn this in training and make corrections as needed.  The reason you don't do this more than a few times is simply because these training sessions create a lot of stress on your body, and while it would be great to be able to knock these workouts out every weekend, most people simply cannot handle a big workout like this AND continue quality training during the week. 

So what are some of these key indicator workouts?  Well there are a couple of options, all of which should be incorporated into a long run, but these depend on experience, weekly mileage, etc.  So I will provide a few examples, but before implementing such a workout, consider your training leading up to it and whether or not the workout will benefit you. For all of these workouts, I would recommend a thorough warm up, nutrition/hydration plan, clothing selection, etc as you would for a race, as these are the closest you'll get to simulating your race.

- 6 miles at 10% of marathon pace, 6 miles at marathon pace, 6 miles at or faster than marathon pace
- 10 miles easy, 10 miles at marathon pace
- 1 mile easy, 3 x 5 miles at marathon pace, each set with a 1 mile easy between

None of these workouts are easy, and they are ordered by degree of difficulty.  They are all between 18-20 miles, but will take a lot more out of you than your standard 18-20 mile easy long run, so heed my warning above regarding whether or not you are ready to tackle one of these workouts.  However, rest assured that by the end of any one of them, you will know whether or not your marathon pace is accurate.

Other key points to note - Simply nailing 1 or 2 indicator workouts is certainly a marker of one's fitness, but if you approach these workouts rested (ie mini taper), then you are defeating the point.  Doing so can lead to false sense of accomplishment of one workout, whereas your total body of work (ie weekly volume and intensity throughout the training cycle) has more of an impact on how race ready you are.  Since these are training workouts, we should treat them the same as all other training runs.  So that when you execute one correctly, it provides that validation.

Now no post on finding marathon pace would be completed without my own story.  On Saturday, I ran a variation of 10 miles easy, 10 miles at marathon pace, where I also added 2 easy miles on the end.  And how did it go?  Well it certainly validated my guidelines of pacing:

10 miles easy: 8:10 pace
10 miles marathon pace: 7:06 pace
2 miles easy: 7:40 pace (it was too difficult to slow down to easy pace at that point, so I just ran comfortably)

So does this mean that I'll be able to hold 7:06 at my marathon?  Maybe, maybe not.  It depends on race day conditions.  However one thing is for sure, I know where my potential lies.  And that fact is what I will use to structure my pacing plan.

Right In The Thick Of It

Time just keeps flying by, doesn't it?  I am now finding myself staring down at 7 weeks until race day!  Which means, 4 more weeks of peak workouts, a transition week, and then taper time.  Phew...it seems so far away to have to get through the next tough weeks, but also so close.  But as always, I like to take things one day at a time, because you need to focus on the now, before you can focus on the future.  Otherwise, you risk losing sight of what you need to do first, in order to get THERE. 

So that is where I am today.  Taking a look at today's tempo run and looking forward to running outside.  This past week brought some challenges, between busy family stuffs and a few minor snow events.  I still ran outside wherever I could, but I had to hit up 3 treadmill workouts this week after the Z man was asleep, due to being on daddy duty for much of the week.  Thankfully it was a recovery week, so it all worked out and my body feels ready to move forward.  Ask me again in a few weeks and I'm sure it will have a different answer...but I digress.

As much as I recommend runners participate in tune up races as they build toward their goal race (no matter the distance), I am having a really difficult time making that happen for myself this training cycle.  For the marathon, I prefer to use a 13.1 as a predictor/tune up.  It most closely resembles the distance compared to other options, and works pretty darn well to figure out if you are in the ballpark of your marathon goals when you race one all out.  For those curious, I've found that doubling your 13.1 time and adding 10-12 minutes gives a pretty good approximation, which is typically a little closer to reality than most calculators.

However, the DC area really lacks 13.1 and 10 mi distances in the January/early February timeframe, despite having thousands of 5ks to choose from each weekend.  Rightly so, since it is the middle of winter, but it would be nice to have an option.  There are also so many runners in this area training for goal races in mid March (ie RnRUSA, Shamrock, B&A), that it seems a shame there aren't more options for us.  Last year, I ran the Snapple Half Marathon, and despite the mis-measurement issues of the course, found it to be a good race for a good cause and fairly priced.  I had every intention of racing it again this year, since the timing fell perfectly at the end of my recovery week, but family business required me to stay home.  No biggie at all, but I sure was looking forward to putting a shiny new PR out there.  My 1:29:xx is a soft PR for me with my current fitness, so it would be nice to put a dent into that or the 10 mile PR which is even softer, since I set it DURING the 13.1 last year. 

But given the place I am at in my training, I don't see where it makes sense to substitute anything shorter than a 10 miler into my plan, simply to get some race experience.  And I don't subscribe much to the belief that racing hard (10k pace and faster) on tried legs the day after a long run will do anything for me, other than lead to a sub-par performance in the race (potential confidence killer and injury risk), and require even more recovery.  The only 10 miler that is reasonably close to home is only 2 weeks out from my race, which could be substituted for my long run, but it is also not the time to blow out the legs just to get a PR.  And I don't sign up for races just to run supported miles.  Its just not in my DNA to stand on the start line and not run to my potential (unless I am supporting someone else of course).

Gotta have some priorities and the marathon is it right now.  So I will continue to flex my mental muscle on my long runs, speed workouts, and tempo runs.  I've been racing for a long time, so I don't think the experience will be that helpful.  Really it would be more for race prediction and PR setting than anything, which is something that would be nice, but isn't a requirement for me.  So I am going to hold strong and leave the PR setting at other distances until after the marathon.

It take a strong person to train patiently and properly throughout a race build up.  It takes an even stronger person to refuse the temptation of short term gains (ie "testing" oneself in workouts, setting shorter distance PRs, straying from the plan) in exchange for sacrificing the big picture goal, which is obviously to run to my ability at Shamrock.  And that's all I've got to say about that.  Now if you'll excuse me, I have a lot of miles to go run!