Keep It Simple, Part II

“It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience.”  Albert Einstein (1879-1955), during a lecture, Oxford, June 1933

Einstein’s goal of achieving simplicity without loss of the necessary holds true, especially for runners.  Figure out the amount of data you absolutely need to track progress, after that it's simple to gradually acquire the stuff which works best, or to steer clear of the stuff which won't work at all.

First, let me explain that I’m not slamming brick-and-mortar running specialty stores.  If given the choice between a major retail sports store, a locally-owned/operated running specialist and an interlink-based provider I'd much rather deal with the guy who's paying local property taxes and hiring passionate young men and women from my town's high school or local college; someone who really has some skin in the game when it comes to the running community.  Usually that's a person who's going to do the right thing.  But you can tell when a shopkeeper has become too-mercenary when (new) runners toe the line at a local 5-kilometer race with a four-bottle hydration waist belt.

I have a love-hate relationship with the consumer grade GPS receiver.  As a course measurer I love to use the GPS to provide ballpark estimations of where my intermediate splits will fall on the race course, and to get latitude/longitude references in those rare instances when no permanent reference point exists.  The hatred comes when runners who have no understanding of the necessary technological limitations of the GPS try to tell me a course is "too long."  Upload a run to Google Earth and you'll see some places you never thought you could run.  Runners who do most or all of their workouts on a treadmill or a track most likely aren't going to need GPS devices; there are times I would dare to say that for most a GPS is little more than a very expensive running watch.  I've also played with running watches which used accelerometers those little pods attach to the running shoe and track how fast and how far you ran, without the need for all those satellites.  They're a little expensive and the batteries tend to die at the wrong time, but they're very reliable if all you need is distance and speed.  If all your courses are known distances, choose a running watch or a heart rate monitor. 

Good ballpark distance figures for runs on sidewalks, roadways, and now even trails can be mapped out on map programs like MapMyRun, GMaps Pedometer, the USA Track and Field "My Running Routes" program, and Google Earth (which requires a little more patience).  There are a few disadvantages to these programs:  When flat photographs are used to try and measure distance on a rounded surface (our world) there can be varying degrees of inaccuracy; a half-marathon course I measured last year proved this to be true.  As a plus, MapMyRun allows runners to track workouts they've run on a particular route, and even gives runners the ability to print out courses...if you purchase a membership.  Go on the cheap like me and you best be able to read what can best be called “gibberish.”  A race director sent me his MMR files last year and all the street names were “Asflkue Ib.”  And worse.

You'd rather not wear a heart rate monitor, you say?  My wife is one of the many who would agree with you.  Some folks don't like to have that fabric/plastic strap around their chest, especially guys who like to run shirtless (I like data, therefore I run with a shirt).  Those persons who still want to check their intensity every so often can purchase a watch which has finger contact plates; place the two fingers of the non-watch wearing hand (of course…) on the plates and the heart rate reading appears in seconds.  Runners who use fairly modern treadmills with heart rate equipment attached can most likely forego this and use the handrail plates, which are about as accurate as chest strap monitors. 

You Luddites can lay a couple of fingers along your carotid artery on the left side of the neck immediately after the run is completed, or gauge your effort on a scale of one to ten, where one aligns to ”am I awake?” and ten means ”if I take another step my chest will explode!”  Some of the really good heart rate monitors will not only break down your workout effort by average heart rate, but by amount of time spent at a particular intensity level.  Entire books have been written about training by heart rate, and quickly leaves the beaten path to go into the weeds of the “should I use the ‘220-minus-age’ formula to calculate my heart rate?” question, the “male-versus-female max-heart-rate” debate (which my wife and I have had on many occasions), and so on.  Surprisingly enough, physiology researchers found a strong correlation between perceived effort (that “one-to-ten-scale” thing) and percentage of maximum heart rate; a perceived effort of “five” was found to be right around the fifty-percent of maximum heart rate point, and so on.

So now we've talked about the simple "where," "how far," and "how hard" of running.  I'll talk in the next installment on what to do with that information.

The Big Plan B

*BEEP*

That was the low battery warning signal from my (formerly) trusty Garmin 310XT GPS receiver. The sound was immediately followed by a slight buzz, silence as the receiver shut itself off, & an unprintable comment from my mouth. I guess it wouldn't have been such a bad thing if not for the fact I was driving out to run a tempo run with a group on a Wednesday evening.

My wife asked, 'do you have a charger in the car?'

'My charger, unfortunately, is attached to my computer back at the house,' was my reply. As we continued the 20-minute drive I was stewing in my own juices of stupidity. I know I put the receiver on the charger the previous evening, so how could this be? I resigned myself to the thought of going out for what former triathlete (now triathlon coach) Chuck "Chuckie V" Veylupek calls a 'caveman run.' This would be an acceptable compromise. I took a deep breath, let it out, & returned to conversing with my wife about life, the universe, & everything. You know, the kind of stuff married couples talk about when there's nothing else to do...wink, wink, nudge, nudge...

My wife then pulled out her new smart phone to check her voicemail & realized her phone had been off all day. She had a little trouble turning the phone on & assumed the battery was dead. I managed to reset it, & then realized, 'hey, these smart phones have GPS. If I download a run mapping program (like iMapMyRun) I should be able to keep track of the pace I'm supposed to do for this tempo run.' So, with precious few minutes left before the group was scheduled to leave on the run I tried to download the software. However, I couldn't get WiFi or set up the phone in time to download. That's where the ability to "Plan B" a workout is a valuable skill.

When talking about training I repeatedly have borrowed the John Lennon song line: 'life is what happens to you while you're busy making other plans.' This is so true as a runner or as a coach. I can lay out a training schedule in macro for 16, 18, 20 weeks out from a race, but more often than not it's going to get adapted, truncated, or...worst of all...pitched in the wastebasket as life takes hold of the stick & throttle. Even the micro level of an evening's (scheduled) track workout gets adapted; heavy cranes & lighting equipment, soccer matches & "facility fascists" can take up part or all of the track & leave an inexperienced (or unprepared) runner - or coach - wondering what to do as a "Plan B."

While in a two-year internship with the Navy I spent periods of time ranging from two weeks to two months at training commands. The assignments had the obvious drawbacks of living out of a suitcase, with access to hotel treadmills, & so on. But I learned how to adapt my training to the conditions. During a two-week assignment to Orlando I learned that light poles along this nice long stretch of road near my hotel were set at approximately 50 yards. So, all I had to do was count the number of light poles for my interval workouts; run three at 5K pace, walk one to recover, repeat six times, jog eight poles...I'm certain you get the message.

Frank Shorter once was quoted as saying 'hills are speed work in disguise.' So, running up a section of hill or bridge for a period of time (or distance, if you know it!), then jogging easy or walking down can provide a great workout. A 300-yard hill near the track facility where we train has three points marked on it; if a soccer match is going to keep us off the track for most or our entire workout I can always go down the hill. Sometimes the soccer matches are not interrupting; I'll do a set on the hill just to break up the monotony.

Training by perceived effort for a long enough period can help a runner develop a sense of pace; after a while you know what a nine-minute per mile pace feels like, as well as an eight-minute pace, & so forth. The most important thing in understanding pace sense is to know how a particular pace FEELS. I always marveled at my coach's pace sense when we would go out on easy runs during the weekend. I had purchased my first heart rate monitor/foot pod combination & was geeking out checking our pace during one run. He asked me at one point what my heart rate was; I looked at my wrist, then told him, to which he replied, 'yeah, I figured that. We're at the right pace.' Sometimes, it is safer to not ask how they do it. They just do it. I've got a few paces pretty well nailed down after eight years of training by perceived effort, so I can tell how hard I'm working give or take a few seconds now.

But I don't have a good sense of time, with the exception of swimming in a pool. I can tell you exactly how long it takes me to swim 50 or 100 yards, even though it feels like forever, give or take a second. (It must have to do with that love of oxygen.). So when it comes to running a particular period of time at a particular pace I'm doomed if I don't have a watch. So rather than the planned tempo workout of eight minutes at the pace I need to run a half marathon, two minutes easy, eight minutes at threshold, two minutes easy - repeated twice - I had to adapt. I decided to count telephone poles; eight at moderate effort, two easy, eight at hard effort, two easy, repeat until the end.

Adapting a workout to meet life's demands: So simple, even a caveman - or a smart runner - can do it.