What Did I Do Right?

     In running, as in life, I tend to focus on what I failed to do, or didn't do enough or didn't do right. Last week I wrote that my training for the Boston Marathon, in three weeks, was flawed because it lacked races and group runs. I said that Wilmington's half-marathon last Sunday would be a test. I passed. I ran in a personal best, more than 1 minute faster than in 2012, my previous record on the distance. That means I must have done something right.

     There's no magic in running: To become faster, you need to train faster. Speed-training runs can come in various flavors: speedwork, or repeats of half-mile or mile at an extremely fast pace; tempo, usually 3 to 5 miles at a very fast pace; and the unfortunately named fartlek (speed play in Swedish), bursts at a crazy pace over a few hundred yards/meters off a regular-run pace.

     Whatever the flavor, I find them unpalatable. I wrote last week that I felt as if I butchered my speed sessions this year. The main reason is that I'm unable to keep up with the program I downloaded from Runner's World's smartcoach tool (I have used it over the past four years, in combination with my homemade plan, and recommend it for everybody, from newbies to seasoned runners). The pace for speedwork and tempo leaves me out of breath and struggling after a few minutes on my treadmill. So I've been cutting the length of the repeats and doing more of them. I've been doing more fartlek, which I find easier. It was apparently enough to gain some speed.

     I'm also wondering whether my weekday, so-called easy runs on the treadmill helped me. I have a special technique (perhaps I should find a name for it, preferably not involving the word fart.) Because I find running on a treadmill a lot harder than outside, I never can start my sessions at 7 minutes 30 seconds a mile (8 miles per hour), the recommended pace for my easy runs. I start at about 8:30 (7 mph) and increase the pace every minute by 0.1 mph until I reach 9 or 9.5 mph. Then I come down to 7.5 mph (which then feels very slow) to resume my gradual increase of 0.1 mph per mile until I reach 9 or 9.5 mph again and drop down again to close to 8. The idea is that at the end of the session I will have averaged a faster-than-7:30 run, while not feeling like it was too hard. Those runs may be partial speed sessions in disguise: on a 50-minute session, I may spend at 10 to 15 minutes at a faster pace than a sub-3 marathon speed.

     My long runs may be another factor for my faster half-marathon. Owning a Garmin watch that indicates my pace has changed my approach to those runs. Until about a year and a half ago, I regarded them as a distance to accomplish. In the winter, I dreaded the prospect of being on the roads for more than 2 1/2 hours, fighting the cold, rain or snow. Now I see them as a succession of one-mile runs. When I started training in January, I aimed to maintain a pace that averaged about 7:30 a mile, following the guidelines of my plan. I realized I was going faster and started to push downhill to 6:30 or below to compensate the slowdown from uphill portions (there's barely any flat road around where I live). Uphill, I would endeavor never to go over 8. With that technique, I was soon averaging 7:15 without really trying to go fast. On my latest 21-miler, I dropped to about 7:05. A Garmin watch will never replace the emulation of a race or a run with faster runners, but it did give me an incentive to push a bit harder.

Matching colors: Caesar Rodney Half Marathon in Wilmington is my dress rehearsal for Boston

     Sunday, after rejoicing for a few minutes at my new record of 1h25m47 in a half marathon (enough for a second place in my age group and sixth female overall), I reverted to my old habits and reflected about what I could have done better: a stronger finish and pushing harder downhill, among other things. Personal best or not, I know this to be true for every runner, from novice to elite: During a marathon, anything can go wrong.

What's Wrong With Hermitic Training?

This year I trained almost exclusively on my own for the Boston Marathon: no club run, no competitive races and no one but myself on the long runs. It wasn't by design but the result of a litany of excuses, including poor planning, working long hours, post-work appointments, sleeping in and the flu. As the weeks passed, it became obvious my training was flawed. I decided to make it part of the game, as a test: Can I run a successful race after a mostly solitary training?

(Can you spot me training near St. Lichaa hermitage? Photo credit: Guillaume Piolle.).

Running a marathon is by definition an individual pursuit: You'll be on your own the day of the race anyway, said my massage therapist, a former professional female triathlete who still completes Ironman events in under 11 hours. True, but on race day I'll be surrounded by thousands of others who will inspire me to surpass myself. The same goes for training: running with better runners is the best way to get faster. That's why I always urge fellow runners to incorporate races into training, ranging from 5Ks to half marathons.

Races are more fun than trying to run fast on your own, especially on a treadmill, a torture device that is essential to my weekday speed sessions during the winter. They are also a good opportunity to get used to prestart jitters, to hone strategies and to fail: It's better to be disappointed by a training race than the race itself.

(Torture center with view, down in the basement.)

I kick-started the training for my past two Boston marathons with a 10 mile (16 km) race in Wilmington in January. The race, hilly and appropriately named "Icicle," is a great gauge for evaluating where I stand in terms of pace and a chance to grab a little award for my age group -- a morale booster. The race is about three months before the Boston Marathon so, even if I don't perform well (I ran 2010 at a slower pace than my eventual marathon), I know I have plenty of time left to progress.

This year I missed the Icicle race because of the flu, which grounded me for 10 days. The only other race I'd scheduled was a local 5K fun run, which I incorporated in the middle of a 20-miler. My plan was to get out of my comfort zone on a distance I'm not very good at by trying to follow the leaders as long as I could. It panned out when the fast 20-somethings apparently stayed home on that snowy day. After about 500 meters I was alone in front and stayed there for the rest of the distance.

Small local races can be very fast or very slow, depending on who shows up. I could have run a few more since. But I didn't: There was always an excuse.

Back in 2010, I wrote how running with the Delco RoadRunners Club helped me get back to running after a long illness and win my first award in a New York City half-marathon. Two months later, I ran the Boston Marathon in 3h01m43, a personal record at the time. There's a lesson here: Camaraderie makes you run faster. I see it as almost vital during training: talking about running gets some of the steam off my obsessive-compulsive mind.

It's good to be able to share stories that would bore non-runners to death. Most runners are over-sharers: we love to talk about our pace, injuries, pains, training strategies, types of shoes/socks, chafing and bowel movements. We have no shame. This year, I was unable to join my club on weekdays. I kept my insecurities about my training flaws mostly to myself. My husband has suffered the collateral damage of my lack of socializing with other workers. I try not to burden him with tedious tales of my runs, but I often can't help. Before he can utter the question "How was your run, honey,?" he usually already knows my pace, whether I'm happy about it, which muscles hurt and a few other details. 

I keep going back to my training log for the 2011 New York Marathon, the only time I finished under 3 hours. I check my pace and weekly mileage and inevitably find that my current training is inadequate for a repeat. But I like one entry: a half-marathon on Oct. 15, 2011. I ran it in a disappointing 1h30. Four weeks later, in New York, I ran the first half of the marathon in 1h27 and finished in 2h59m18. When I feel bad about my training, that log entry is like a chocolate bar.

With four weeks left before the race, I can't undo the wrongs. I continue to doggedly, solitarily follow my training plan. My speedwork has consisted of uninspired sessions on my basement's treadmill. I feel like I butchered them. I was often so tired after a day of work (I'm at my desk at 6:40 a.m., so no time for exercising before work) that I postponed those sessions day after day, until there was only Saturday left to do them. It is another quirk in my training this year: I would not recommend speedwork and tempo runs the day before a long run (which I usually do on Sundays). Those sessions belong to midweek.

Perhaps I got a few things right. I ran my long runs faster than I used to. They're no longer 20 milers. They are 20 one-milers, and in each I try keep a steady pace. My last long run of 21 miles averaged 7:04 a mile, which is "only" 12 seconds slower than the pace I would need to finish in 2h59m59. It restored some of my confidence. Not a lot.

Next Sunday will be the end of my hermitic experience: I'll be running a half-marathon in Wilmington with my club. The course -- downhill followed long uphill -- makes it a mini version of Boston's. I always use it as a dress rehearsal, perfectly timed four weeks before the race. This year it will be a public test of my private training.