Tuesday, December 4, 2012

CIM 2012: Thoughts on the H-B Plan


I started this blog to document the quest to answer a simple question: is it possible to run a marathon using a training plan that calls for no runs longer than 16 miles?  At the finish line of Sunday’s 30th running of the California International Marathon in Sacramento, the answer is an unequivocal YES!  I crossed the line in 4:08:10, a PR of more than 13 minutes.  AMD finished in 4:09:58, a nearly 9 minute PR.  And another friend of ours who followed the HB plan BQ’d with a 3:38:42.  And this was on a day when Sacramento broke a 71-year-old rainfall record with 1.32 INCHES of rain by noon Sunday.

There’s lots of details about the race I’d like to share/document, but I’ll start by summarizing my thoughts about why I believe we succeeded with the H-B plan.  First off, I ran nearly 650 miles since July 17, 428 of them since Sep 24.  Never before have I logged a 50 mile week, yet in weeks 14-16, I ran 50, 51 and 53 miles.  Removing the stress/burden of the 20 mile runs enabled me to run more miles because I didn’t need the usual recovery time and I didn’t sustain any serious injuries.  I feel like the constant running also taught my body to be more resilient.  I did get a couple of minor tweaks along the way, but a bit of compression and some ice usually solved things within 24 hours.  During the last 6 miles of CIM, this resiliency manifested itself in my ability to work through and overcome the quad cramps that have debilitated me in almost every other marathon I’ve done. 

Finally, I think I came out of the H-B plan much stronger mentally than ever before.  Running 6 days in a row is hard and requires a lot of discipline and planning.  You have to run the proper mileage at the prescribed PACE, and you cannot succeed if you skip too many days.  The “no 20 milers” thing doesn’t come for free.  In the critical weeks 10-17 of the plan, I ran 47 of the 48 scheduled days (I missed a day so the family could go to Sea World, I told myself walking all over the park was just a REALLY easy recovery run.)  I ran early in the morning, during a long lunch, after work, after dinner, whenever I had to in order to get my run completed and still keep my job and my family.  When the quads started to tighten up in the last 10k, I went through many tactical options before settling on walking, where in past races I would have walked at the first sign of pain.  Ironically, I think it was the easy runs that helped me the most in the end.  I remembered how slow those days felt and yet the pace was always around 10-11 min miles.  I convinced myself in those last few miles that a running motion, no matter how slow, would be so much faster than walking.  The last 3 full miles, 11:05, 11:23, 11:08…hello sub-4:10 finish.

I was not as disciplined about my writing, but I did add a “Running Log” page to show the daily mileage and paces.

Wednesday, August 29, 2012

Day 19 to Day 24

Ok, so I'm clearly doing better at training than blogging.  I'm going to take the advice of my friend Madison and scale back to once or twice a week.  Tuesday nights are a good time since Wednesday is the one sacred rest day of the week.

The past week has been highlighted by a hard speed workout, an absolutely awful marathon pace run, the first back-to-back 8 mile runs of my life, and the first mile repeats of the plan.

Day 19: August 21, Speed Ladder
I realized I could make this workout harder by running the recovery lap faster.  Seems obvious but it feels counterintuitive to do anything but shuffle around the track after an interval.  The previous week, the recovery pace was in the 10:30-11 min range.  This week it started in the 9:45 range after the 400 and 800, and got slower after the two 1200s.  Even so, the pace for the entire workout was 8:25, well below goal pace.  I felt like this was a significant achievement, until...
http://connect.garmin.com/activity/213529359

Day 20: August 23, MP Run
I tried to run 8:45s for 7 miles after last week's rest day, and I knew I was in serious trouble when I could barely keep the pace running downhill for the first 3 miles.  When I turned around to come home, it was over by mile 4.5.  I had nothing left to run even 9:09s uphill.  I had to get back home, so I did the last 2 miles at a comfortable pace and lived to run another day.
http://connect.garmin.com/activity/214491005

Day 22: LSR
The first 8 mile run of last weekend was actually faster than the aborted MP run on Thursday.
http://connect.garmin.com/activity/214887773 

Day 23: LSR
The second 8 mile run was even a bit faster than the first 8 miler.
http://connect.garmin.com/activity/215286666

I think the best part of this first ever back to back 8 mile weekend was using my new Garmin Forerunner 610!
I've been using my wife's 110 for the past few months after my trusty 305 USB charger stopped working.  However, she's about to begin her own training program for the Tinkerbell Half Marathon, so I was feeling the pressure to find something new.  Fortunately, I came across, of all things, a Garmin rebate!  $50 off a new Garmin when you trade in your old one.  Combined with my $100 in REI gift cards (thanks mom) I got the 610 (w/o HR monitor) for $200!  If you want to grab this deal, you need to buy your new watch by Aug 31.

The 610 is noticeably heavier than the 110.  It took me a couple of miles on Saturday's LSR to get used to the weight.  It has the new Garmin touch screen versus the touch bezel that was featured on the 410.  After years of using Apple products, it takes a bit of adjustment to use the Garmin swipe feature. 

The main reason I bought the 610 is the ability to configure multiple data screens.  I had my 305 configured to show me pace/distance/time on the main screen, and lap pace/current lap/time on a second screen.  I used the screen almost exclusively for track workouts.  The 110 did not have the feature, forcing me to spend a lot of time doing math during a track workout. "Ok, I just finished my recovery lap and the watch says 4:19, so I need to do hit 8:19 on this 800 to make my 8 minute pace.  Or did the watch say 4:22?"  Today's workout was a return to normal, hit the lap button, the current lap count resets, no more math, just remember to hit the lap button after every interval.

The other feature I missed is the ability to scroll through the history of a run on your watch.  The 110 has basic functionality, meaning you can't see your splits or any other data until you download it to your computer, or upload it to Garmin Connect.  The 610 has this feature, and pretty much every other feature of the 305, in a nicer form factor, and as a bonus, it syncs a lot faster to the GPS satellites.  I'm a little concerned about the charging interface, and I'm not convinced that transferring data via the ANT WiFi dongle is the best thing, but it's comforting to know if I encounter any issue, I can always exchange/return it to REI.
 
Day 24: Mile Repeats
Can't say the 610 made the first mile repeat workout of the training plan easier, but it was comforting to see the 0:00 at the beginning of each interval.  We made the workout a little less daunting by walking the recovery lap between each mile.  The best thing about this workout is you know it will be over soon. 
http://connect.garmin.com/activity/216124318

On a final note, I want to mention that I skipped Monday's recovery run.  Maybe this is why the mile repeats weren't awful.  I woke up Monday morning and had a weird pain on the top of my foot.  It had not hurt at all after Sunday's LSR, so I figured I slept on it wrong, and figured it would go away after my day got going.  But as I was walking to the gym at lunch to get ready for an easy 4, it was still bugging me, so I reluctantly bailed on the run.  This was hard because I just hit 30+ miles last week and was excited to repeat the mileage this week.  Losing 4 miles on Monday was a bummer.  But I woke up this morning pain free, and had a very successful track workout.  One of the underlying tenets of the HB plan is to not worry about a missed workout.  I didn't and it was a great decision.  Of all the workouts, the recovery run is the most expendable.

Wednesday, August 22, 2012

Day 15 to Day 18

Need a shortcut to get totally caught up with the blog, so I'm grouping the Friday-Monday runs since Friday and Monday were recovery run days, and Saturday and Sunday were LSRs.  Friday's recovery was notable because I woke up thinking I had to go 3 miles, and had mild panic attack when I checked the schedule and it said 5 miles!  Oops.  So much for being prepared the night before a run.

Sunday's LSR was the first time in this training cycle that we went beyond the 10k distance.  AMD and I feel like we can do more than the bare minimum we originally laid out, so we're looking over the plan to see where we can add miles.  Extending the long run seems like the most meaningful spot.  We choose a route where we ran up an incline for the first 2 miles, then felt like we were running downhill for the final 6.  Running a slight decline is a great confidence booster!

http://connect.garmin.com/activity/212601956

Day 14: Aug 16 MP Run

Two things of note on this MP.  1) This was the first step up in the MP distance, a solid 10k.  2) AMD and I had a conversation every set of running partners should have: how injured does your partner have to be for you to stop running?  We were cruising along at MP pace around mile 3 when AMD suddenly stopped.  I had the tunes cranking so when I turned to look at her, I couldn't hear what she said, but she didn't seem to be in distress, so I kept going.  I stopped and waited for her at the top of the second uphill section, and we devised the following rule for a MP/tempo run:

You need to stop if your partner:
1. Falls down
2. Gets bitten by an animal
3. Screams 

The last condition is a bit problematic when you're both running with music, so, just like scuba divers, we agreed on a massive waving of the arms signal to also indicate run stopping distress.  I'm glad we settled that.  The run was good too, 6.26 miles at an 8:37.

http://connect.garmin.com/activity/211371759

Tuesday, August 21, 2012

Day 13: Aug 14 Speed Workout: Catching up...again

A week ago, August 14, represented the return to training after two weeks of traveling.  As of this morning, I just finished 7 days of running in 8 days.  Unfortunately, I have not done as well at maintaining this blog.  So I'll get caught up with a brief recap of August 14. I jumpstarted the training schedule with the speed workout.  I did my favorite one, a ladder of 400-800-1200-1200-800-400.  It breaks up the monotony of running the same distance 6 or 8 times, and it's good practice to focus on maintaining the same pace over varying distances.  The Runner's World Veteran Plan I followed in 2010 added a 1600 between the 1200s.  Running a 400m recovery lap between each interval as specified by HB provides more temporal rest, but it's not the same as standing still waiting for your next interval.  There's no way I could have done that 1600.  I love an interval workout after a lot of travel because it's a nice confidence booster.  The short distances give you a chance to feel fast and successful.


MILES
TIME
PACE
TOTAL
3.0

00:00
Lap 1
0.25
01:57
07:43
Lap 2
0.50
03:59
07:57
Lap 3
0.76
05:57
07:48
Lap 4
0.76
05:56
07:50
Lap 5
0.51
03:55
07:42
Lap 6
0.26
01:47
06:59

http://connect.garmin.com/activity/210686874

This was a good way to start last week.

Tuesday, August 14, 2012

And then work got in the way...

I can't believe my last post was July 29th!  I've actually been home for 48 hours in a row now, so it seems like its time to catch up on everything.  There have been a few runs that need a post, I'll get those up later with their corresponding data.  The lack of posts is quite reflective of these last crazy two weeks of my life.

I was in Sao Paulo, Brazil from July 30-Aug 2 for a trade show.  Usually when I'm in a foreign city, I like to go for a casual run to get a feel for the city, not worrying about pace of getting lost.  This was the first time I didn't take that opportunity.  I had no idea if the city was generally safe, or which areas of the city to avoid, and this sign in the elevator didn't help much either:
So I did 30 minutes a day on the treadmill for the three full days I was there and hoped that would be sufficient to slow the inevitable loss of fitness that occurs when you stop following your training plan.

It was the red eye home on Aug 2, which included a 5 hour layover in Chicago's O'Hare International Airport before arriving back in Orange County.  Does walking from Concourse B to Concourse C, eschewing escalators along the way, count as a training run?  Probably not, but I figure I managed to walk between 1 and 2 miles since I backtracked to Concourse B to get Vosges chocolate.  I figured there would be a location in each terminal. I was wrong.

I was home for approx 40 hours before my next trip began.  Aug 3 was a completely lost day, just totally wiped out from the 19 hour journey home.

Managed to get in a 3 mile run on Aug 4, it was more of a recovery run than LSR. 

Aug 5, 8 AM, it was off to Keystone, Colorado for another conference, so no LSR on Sunday morning.

I travel to Keystone every year for this conference.  It is about 100 miles west of Denver, which you may have heard is called the "Mile High City."  That's 5280 feet.  You drive up into the the Rockies to get to Keystone, which bills itself as being at 9280 feet.  That would be 1.75 miles above sea level.  I swear there is no oxygen there.  No matter what my fitness level is prior to this trip, I assume I've got nothing at 9280 feet and set my running expectations extremely low. 

It was about 7 PM on Sunday night after I finished my work, and I had a choice between eating dinner and attempting to squeeze in a run.  I consulted AMD who encouraged me to "Get my butt out the door, you won't regret it."  I was kind of regretting it after the first quarter mile when I felt like I was drowning because my lungs were inhaling so little O2.  But after making the deal with myself that I would walk uphill, jog downhill, I was able to grind out 2.8 miles.  In 33 minutes.  Ugly, but effective.

http://connect.garmin.com/activity/207491849

The next morning, I got out again.  This time, I drove down the hill a bit so that I could do the uphill first, then finish downhill.  Again, I made a deal with myself to walk for one song on the iPod, run for one song, repeat, all the way up the "I-swear-it-felt-steeper-than-100-feet" incline, then run all the way down the hill.  All told, 3.3 miles in 37 min, improvement!

http://connect.garmin.com/activity/207491837

The last full day of my trip, Aug 7, I ambitiously planned out an interval circuit through the resort paths that included three half mile-ish running portions, and two quarter mile walk portions.  I repeated it twice, with each running interval in the neighborhood of race pace.  Convincing myself to run the loop the second time took every ounce of will power in my body.

http://connect.garmin.com/activity/208618882

I posted links to these three runs just because it's cool to see the elevation vary between 9150 ft and 9350 ft.  If I could do this entire plan at this altitude, I think the 4 hour barrier would seem a lot less daunting.

Sunday, July 29, 2012

Day 10: LSR4

Today was my last real run before my business trip to Brazil (I'm posting from O'Hare International while I wait for my connecting flight to Sao Paulo.)  Went up into Peters Canyon for a second day of hills.


MILES
TIME
PACE
TOTAL
5.6
0:54:32
0:09:44
SPLIT: OUT
2.8
0:27:49
0:10:03
SPLIT: BACK
2.8
0:26:40
0:09:27

http://connect.garmin.com/activity/204343981
This is a good benchmark run because I've done it so many times before, and will do it many times to come.  After 10 days, I'm pleased that I've been able to go a bit longer than intially planned.  Of course, all this confidence is gained on runs that have been less than 6 miles.  The last 3 weeks of August when the 6 and 8 mile runs start will give me a better idea of how I'll fare with this plan.

There does not appear to be any suitable places to run in Sao Paulo, so the plan for the week is to do a treadmill + pool workout at the hotel Tue-Wed-Thurs, then try to get a recovery run done on Friday after I get off the plane.

Day 9: LSR 3

Saturday was the sixth day of running this week.  The initial shock of running more frequently has worn off a bit, my legs do not feel as tired when I first wake up.  I have to ease into every run but after a mile or two, the legs feel ok.  Decided to multitask yesterday, did my LSR in Rancho Santa Margarita while I was having my car serviced.  Pros: got two things done at the same time.  Cons: had to run at 10 AM with the sun beating down and the mercury over 70 degrees.  RSM has some nice areas to run, I took a trail called "Live Oak Trail" which ran alongside part of O'Neill Regional Park.  The path had a slight incline, but as the garmin data shows, I ended up gaining 400 feet in elevation.  What goes up, must come down, so I was able to hit a pretty decent pace coming back.


MILES
TIME
PACE
TOTAL
5.4
0:50:29
09:25
Lap 1
1.0
09:31
09:31
Lap 2
1.0
09:49
09:49
Lap 3
1.0
09:26
09:26
Lap 4
1.0
09:17
09:17
Lap 5
1.0
09:08
09:08
Lap 6
0.4
03:17
09:07

Here's the garmin data:
http://connect.garmin.com/activity/204044885

It felt good to do some uphill running.  I would like to include hill running on at least one of the LSRs each weekend to build leg strength.

Logged 25.5 miles this week, starting to find a groove just as I'm leaving on 3 trips in the next two weeks.  I'm hoping this interruption is early enough in the plan that I can maintain fitness on a treadmill without losing too much of the training momentum I've gained.

Day 8: Recovery Run

Oops, a few days behind in my posts.  It's difficult to leave the office for two weeks.
Friday was a double down day, recovery run in the morning, swim at lunch.


MILES
TIME
PACE
TOTAL
3.0
0:30:40
0:10:17

At the pool, repeated last week's workout with six 5-minute intervals, only this time I aimed for 175 yards in each 5 minute period.  Worked better this week, I got 20 seconds of rest after each 175 yards, and I did the full distance in each period, so I totaled 1050 yards this week.

Thursday, July 26, 2012

Day 7: MP2

Today was the first time I've felt fast since the 2011 Surf City Half Marathon.  Here was today's plan:

Workout Unspecified by HB
Distance 3 miles
Goal 8:45 pace

and here's how it turned out:


MILES
TIME
PACE
TOTAL
5.3
0:45:36
08:36
Lap 1
1.0
08:43
08:43
Lap 2
1.0
08:43
08:43
Lap 3
1.0
08:37
08:37
Lap 4
1.0
08:29
08:29
Lap 5
1.0
08:36
08:36
Lap 6
0.3
02:28
08:10

According to the garmin data, the first two laps were slightly uphill.  But except for lap 4, the route seemed like it was downhill the whole way.  I felt like I was in cruise control for the first 3 miles, so I used my reserve energy to attack the slight incline at mile 4.  I was torn between going for it hard like a true RW Advanced Plan tempo run or staying in range of the MP, treating the run like the first 5 miles of a marathon.  I compromised by slowing down over the last mile and coasting to the end. 

I gained quite a bit of confidence from Tuesday's speed work (I'm bummed that my business trips are going to force me to miss the next two track days.)  The muscle memory from the pace of the 800s made today's MP feel easy in comparison.  I was able to find a good groove and lock it in.  I also realized that Duran Duran and the 80s in general have no place on my running playlist.

http://connect.garmin.com/activity/203313163

Tuesday, July 24, 2012

Day 6: Speed Session 2

Back on the track today for the first speed session on tired legs.  Focus today was to run faster intervals with shorter rest periods in between.  Here's the workout:

Workout Speed, 6x800m, 400m jog
Distance 4.25
Goal 8:20

and here are the results:


MILES
TIME
PACE
TOTAL
4.3
0:38:15
08:50
Lap 1
0.5
04:11
08:13
Lap 2
0.5
04:06
08:14
Lap 3
0.5
04:09
08:13
Lap 4
0.5
04:08
08:17
Lap 5
0.5
04:04
08:07
Lap 6
0.5
03:50
07:38

Clearly those six laps only add up to 3 miles.  The total miles includes the 1.25 miles of recovery jogs (5 x 400m.)  I targeted running each 400m in 2:05 to get to a 4:10 for each 800m.  The rest intervals ranged from 2:42 to 2:48, roughly a 10:15 pace.  It felt SUPER slow.  I like running my intervals with music to break up the monotony of going in circles.  Usher's "DJ Got Us Fallin In Love" came on in the middle of Lap 5, and gave me a major shot of adrenalin.  The final interval was a combination of running the first five too slow and a burning desire to be done.  Next time I hit the track (in 3 weeks) I'll be targeting 2:00 min 400s, with a more brisk recovery lap, maybe at a 10:00 min pace.

My legs were tired when I woke up this morning, and I felt it a little on the first two intervals.  But by the third, I was in a pretty good groove and didn't notice at all until I climbed the stairs to my office when I got to work. 

Best part of doing track work at 6:15 AM...realizing you have nearly 48 hours off until the next run!


Day 5: Recovery run

My ultra conservative plan had Monday as a rest day, but I felt like the first 4 runs did not wipe me out completely.  Also, my 3 trips-in-two-weeks begins Sunday afternoon which is going to wreak havoc on my schedule, so it seems prudent to get miles in if I can.  After a quick core workout (that really needed to be harder) here's what I did:


MILES
TIME
PACE
TOTAL
2.9
0:28:51
0:09:53

It was a quick jog from work through the UCI campus.  The first mile was downhill and I thought I was going slow, but my watch said I was running at a 9:36 pace, so I took it REALLY easy up the hills.  Felt like I was practically walking.  These recovery runs are going to be tricky at first because it's difficult to run short distances slow. 

http://connect.garmin.com/activity/202429730

Monday, July 23, 2012

Day 4: LSR2

Day late on posting Sunday's workout.  It was only Day 4, but my legs were noticeably tired when I woke up.  Here was the goal:

Workout Unspecified by HB
Distance 3 miles
Goal 9:00 to 9:15

Here are the results:

 
MILES
TIME
PACE
TOTAL
4.6
0:43:19
0:09:23
Lap 1
1.0

0:09:16
Lap 2
1.0

0:09:12
Lap 3
1.0

0:09:21
Lap 4
1.0

0:09:47
Lap 5
0.6

0:09:16

Without looking at the Garmin data, you can probably guess that we ran downhill for the miles 1-2, uphill for miles 3-4.  I may have been able to get to an even 5 miles, but 6 would have been tough.  However, an hour later, my legs felt fine.  Maybe next weekend we'll try to get Saturday's pace to more closely match Sunday's.

http://connect.garmin.com/activity/202348494