There are a lot of benefits to training with a heart rate monitor. First, ask any professional running coach about the biggest training mistakes recreational runners make, & they will inevitably list somewhere in the top five running "easy" runs too fast / hard. I know I've certainly been guilty of this (though at least I'm aware of it & have definitely gotten better about it). If you know your max heart rate & run with a monitor, it's pretty hard to get away with "But this TOTALLY feels like the pace I should be running!!!" when there is hard evidence to the contrary staring you in the face. They're particularly excellent for keeping tempo / threshold runs at the right effort level regardless of terrain or weather, and it's also cool to watch your average pace improve as your average heart rate gradually drops over weeks or months of training.
But, after a while, I got lazy about it & went to wearing it only for speed & tempo workouts, then only for races, & eventually just abandoned it altogether. I wanted to go back to using it last year to make sure I wasn't running my easy runs too hard as I recovered from my hip injury, but shockingly, the three-year-old battery was dead, & I never got around to replacing it. Which actually worked out for the best, since just a few weeks ago I learned from Page that heart rate monitors generally only last for 2-3 years anyway & after that don't really provide reliable data. So, I took her advice & picked up the Garmin premium heart rate monitor (soft strap) for ~$45 on amazon.
AND, it only took me a week and a half to open the box and figure out how to activate it & pair it up with my Garmin! :D
On Saturday I went for my first run with a HR monitor in three years. Because it's been so long, I wasn't aiming for particular numbers so much as just to see what my heart rate was doing and compare it to what it was doing on average the last time I was using it regularly. It was encouraging to see that for runs of the same distance (5 miles), my heart rate was lower and my pace faster, even though most of the runs for which I have records were in the 45°-50°F range & Saturday in the city was closer to 70°. (Temperature tends to have a dramatic effect on heart rate since your body has to do additional work to keep itself cool.)
If I was being super-rigorous about things, I would probably need to go get my max heart rate tested again. The highest number I have ever personally seen on the monitor was 223 (mid-2011, toward the end of speed work on a hot day) & when I had it tested in a lab in early 2012, we got it up to 211. (It's harder to get up to true all-out effort on a treadmill than, say, running on a track, but it's close enough for science.) That wasn't TOO too long ago, so I feel like somewhere in that range is probably a reasonable number to go by.
(Maybe this is a good time to bust some myths about max heart rate. It is not 220 minus your age or any other formula you read on the internet or on some poster at the gym. Anyone who tells you it is should not be telling anyone anything about their cardiovascular system. Also those little charts that tell you which zone is your "weight loss zone" / "endurance building zone" / etc. are total bullshit. If you want to know your max heart rate, get it tested in a lab or do some speed work with a monitor for a while.)
With that in mind, here's what I'll be aiming for, courtesy of Papa Daniels (who I trust in all things running-related):
- For easy runs, 65-80% MHR, or ~140-172 bpm (I averaged 160 on Saturday & 164 on Sunday, so HELL YEAH!)
- For marathon pace runs, 80-90% MHR, or ~172-193 bpm
- For tempo runs, ~90% MHR, or ~193-194 bpm
- For speed work, 98-100% MHR, or ~210-215ish
(11 to go)
Up until Friday, I was sure that the story of week 4 was going to be the story of cumulative fatigue that may or may not end up causing me to skip training days. This has happened to me before in training cycles; more than once I've had around a month of strong, solid, gung-ho training, and then suddenly it would all start catching up to me. My legs would start feeling heavy & leaden on every run, and even after rest days I would start thinking that maybe another one was not the worst idea ever. (And don't get me wrong, sometimes unplanned rest days are *exactly* the way to go.)
But just as in week 3, things started looking up with the weekend. Not because the runs were easy; they were still tough and I absolutely had to work and dig deep to get them done, which called to mind one of my favorite marathon training quotes from Kevin Hanson (of the Brooks-Hanson Hanson Brothers):
- "Everyone wanted a regimen that would leave their legs feeling fresh. They wanted to know, 'How can I get that spring in my legs?' That was the wrong question. The question should be: 'How can I train my body so that when the fatigue hits me, I'm still able to respond?'"
And that's exactly what I got towards the end of the week. Not painful, not utterly soul-sucking, not stopping-to-catch-my-breath-every-half-mile exhaustion; just general fatigue, tough but doable, & just challenging enough to finish and go, "Not bad; still glad it's done." It's given me confidence this week to get some runs under my belt that have forced me to practice powering through and maintaining good form and good turnover even when my body felt tired & like it would really rather just lie on the pavement with a beer than run even one more block, plzthnx.
Grand Total: 31 miles
- * 1.5 speed
* 2 threshold
* 7.5 long
* 20 easy
- * 2.25 hours strength/stretch/roll
Monday: afternoon strength work / p.m. karate
- I had to drive 40 miles to get to the South Bay butt-early in the morning, which means I had to do my strength work in the afternoon. Guess when I am the least motivated to do strength work? :P
Tuesday: speed work (1.5 warm up, 2 x 1200m @ 5K pace, 1.5 cool down = 4.5 miles total).
- In case you missed it:
That pretty well summarizes my feelings about said track workout.
Wednesday: a.m. strength / afternoon 5 easy / p.m. karate
- I woke up feeling super tight & kind of fragile all over, & also just generally crappy from not sleeping well, so Wednesday morning definitely involved more rolling & stretching & less actual strength work than usual (but still not an insignificant amount).
With this whole six-day deal I've been working under the assumption that Wednesday runs are just generally going to suck, coming as they do on the heels of speed work. Thus far this assumption seems to be a valid one. I was deeply unexcited about this run & the only way I got through it was by running one-mile laps in my neighborhood & making occasional water stops by the house. I felt slow & sluggish & was quite happy just to get this one in the books.
Thursday: 4 easy
- I desperately needed some extra sleep Thursday morning, so I skipped the bike & hoped that would make my run a bit easier than the previous two. No such luck; like Wednesday, this one pretty much sucked from the very beginning. My legs felt exhausted & I was seeing numbers on the watch that I haven't seen since my very first runs back after my hip injury. At least after the first 3 or so miles I did feel ever so *slightly* less like ass. So it only, like, 80% sucked.
Friday: a.m. strength work / p.m. tempo (1.5 wu, 2 @ LT pace, 1.5 cd = 5 miles total)
- Thankfully, Friday (once again) brought my streak of sucky runs to an end. Yes, my legs felt heavy starting out, and I was a bit discouraged because of the massive headwind I found myself running into in Golden Gate Park. I loosened up a little but still wasn't feeling confident that I'd be able to ratchet down to (not to mention maintain) a 7:25 pace. And then suddenly it was just happening, with less effort than I expected. I ran the first mile in 7:24, which was fine but realistically probably just a bit fast considering the crazy headwind. I was sure I was seeing things, though, when the second mile clicked off in 7:11. Yes, I had a tailwind going that direction, but it was also net uphill, including two not-insignificant climbs. The good news: I'm fitter now than I thought, apparently. The bad news: still out of practice re: pacing. This is why we have tempo runs!! :D
Saturday 5 easy
- The afore-mentioned first HRM run since 2011.
Sunday: 7.5 long
- Usually I don't start labeling runs as "long" until they're at least in the double digits, but RunningAhead has had all my Sunday runs pre-designated as long (since they are in fact longer than the rest) & though I've just been switching the category back to "easy" up to now, I forgot to do it Sunday when I recorded this run, & once it was done it seemed kind of silly and pointless to go back and change it.
In less awesome news, I pulled my shoes off post-run & was greeted with this lovely scene:
Which wouldn't be so ironic & annoying except that a) I just randomly mentioned the last time this happened in my recent Kinvara 5 post, and b) I had just clipped my toenails Sunday morning specifically to prevent this kind of thing.