Saturday Morning was my first run of the season with Kenyan Way and it started off with me at the back of the pack. In fact, I was beyond the back of the pack thanks to the ol’ “gotta go now” feeling barely a hundred yards in.
I did a 180 and was thankful to discover there was no line at the port-a-johns. Hence I quickly completed my biological business and recovered from my aborted start. The Running Gods may have been snickering at their little joke, but I would have the last laugh. There was no panic once back on the road. I settled in with an easy pace, not worrying about the pack because I knew I would catch up to the back sooner or later. It would be sooner.
Other than that early hiccup, the run was non-descript. Well, until I caught Lee prior to the final water stop. Lee is training for his first marathon (hopefully Houston) and was a bit worried about making it back to base without getting lost. Being a former marathon coach (specifically for first timers) I opted to run him in those final few miles. And that is when I heard the beeping. It would not stop.
Although knowing exactly what it was, I posed a question regarding the incessant noise assaulting my ears. His watch was set for a specific pace and he was well over it, thus the beeping was a constant reminder.
Now I cannot blame Lee. While many of us know an individual running their first marathon should focus more on finishing than on time as a goal, I suspect that many of us had a time in mind and either consciously or sub-consciously were at least as focused on time as we were on finishing.
The problem is, and most of us know this from experience, we can never predict what impact marathon training will have on our bodies, and how well we can perform. Unfortunately for Lee, he – like many other first time marathoners, consulted a pace calculator to determine how fast he “should” run his first marathon. Oops.
During my years of coaching I learned that the drop out rate from marathon training groups isn’t about not being able to run a marathon, it’s about not making an arbitrary pace number when the half marathon and 25K runs come around. Pace is determined on an assumption that I can run a 5K in X, therefore I should run the marathon in Y. Or the pace calculator said… Sadly, this can lead to increasing frustration and eventually giving up.
Pace calculators and the like are good for experienced runners who have a marathon or more under their belts. I will concede there are some runners training for their first marathon who are exceptions and can pull a goal from a pace calculator, but they are likely well-trained and either elite or bordering on elite.
Personally, I think it’s mostly ridiculous to ask a person to forego any thoughts of time and focus only on doing what is necessary to finish. A number is always going to be looming and the job of any coach (training group or training plan) should be to get them to accept it.
How do we find the number? Execute and adjust; then find the baseline. I say execute and adjust because the first several long runs are an orientation period. Many new marathoners-to-be will go out too fast, therefore they need to adjust for the next run. Execute and adjust again until they have found a pace where they can finish the run without being finished for the day. Then we can get a baseline and work from there.
Will the baseline change? Indeed. As speed work and hill work is introduced into the training program a runner may become not only stronger, but faster. Conversely, the increasing miles and the longer runs may take a toll on a runner and require them to slow down or modify their training plan.
Ideally, a first time marathoner will focus strictly on getting through 26.2 miles. However, we have to accept the time component will always be lingering in the background. As coaches, mentors, and experienced runners, it’s up to us to help our new brethren find the right number – because it’s likely not coming from a pace calculator. We can leave that for their second marathon!