Showing posts with label dreams. Show all posts
Showing posts with label dreams. Show all posts

Sunday, July 6, 2014

To Inform and Inspire (Training 6/2-6/22)

Here's a recap of remainder of the training cycle prior to my 2014 Grandma's Marathon. If you'd like, here are links to the plan I outlined after registering for the race and a recap of the first four weeks of training.

To begin, I'd like to reiterate the goals of the cycle:

1) Stay healthy. By prioritizing workout/long run quality over volume, I hoped to stay healthy. I ran too much the in first week of the cycle. Unlike in other cycles, I realized my behavior was not moving me towards my stated goals and adjusted for the rest of the cycle. I was able to complete the cycle healthy which gave me a lot of confidence going into the race.

2) Practice running Marathon Pace, again by prioritizing quality over volume, I hoped to run Marathon Pace more comfortably than in Boston. I was able to execute some key workouts that I believe really helped contribute to my ability to handle Marathon Pace. Executing these workouts successfully required me to focus on being properly recovered then properly recovering afterwards. For me this meant eliminating "junk" mileage. Though I did supplement my running volume with cross training (more on this below).

Week 3

Training at this point was starting to really become tiresome. My body was tired and I was burning out mentally. I remember desperately looking forward to my 10 day-ish taper. It is in these moments when it becomes necessary to lean on your teammates and support structures.

Monday, I decided, due to lacking motivation and a later than usual run start time, that I would swing by Fleet Feet Sports in Lincoln Square for the weekly 6:30pm "Fun Run." Typically Angelica and/or Brian attend these runs and are usually up for a nice 8 miles to/on the lake. Fortunately for me, Angelica and I were able to get some good miles in.

Nice weather on Tuesday prompted an impromptu double with strides.

Wednesday was my opportunity to really nail a hard mid-week workout. Sort of unintentionally, I ended up racing quite a bit during this cycle. A couple of these races fell on Thursdays so they sort of became my mid-week workout. Despite being registered for 13.1 Chicago the following Saturday, I decided that I had to get in a pretty high volume workout at just faster than marathon pace a pace I could live with.

After a string of races where I felt I had significantly under performed, my hope was that my legs were fatigued and that the strength I had built with all of my consistent running would eventually lead to faster running and racing. For Wednesday's workout, I drew on memories of comfortably running a three mile segment of a workout well under 16:00. If I could get close to 16:00 on my last rep I would be content (all this despite the fact I wasn't running much faster than 16:00 through 3 miles during races at this point).

Though I didn't manage to quite hit 16:00, I was pretty happy with how the workout played out:

"I was a bit disappointed that I didn't get any brutally difficult marathon type workouts in during this cycle. I did 3 x 3 miles on the lake half into the wind and half out of the wind, taking 4 minutes between reps: 17:01, 16:45, 16:19. I was very happy with this workout though it left me very tired."

Just to be safe, I took the day following completely off.

I've run a half-marathon in June for four of the past five years. I use this run as a barometer of my fitness going into the big summer training months. 13.1 Chicago as served as this barometer for three of these tests thanks to a couple free entries. This year's edition featured very tolerable weather (I ran my slowest half marathon ever here in 2011), but my big Wednesday workout and general fatigue prevented me from running very quickly:

"Wasn't 100% sure how the legs would respond after my very hard effort on Wednesday. Ended up just sort of running 5:45-55 pace for the whole race. One gear. I'm hoping since I did it on dead legs that this is pretty close to marathon fitness."

These words read as somewhat prophetic as I ended up running nearly exactly double my 13.1 Chicago finish time in Duluth (1:16:47 at 13.1, 2:33:26 at Grandma's). I like to think that it wasn't so much premonition as finally understanding what marathon pace is supposed to feel like. Previous cycles, I had gotten too much confidence from fast, hard workouts. A 17-18 miler with some very fast running mixed in is good training stimulus, but these runs made me overconfident when going into a marathon and didn't provided the appropriate aerobic stimulus necessary to run my intended marathon goal pace without blowing up. I'm pretty sure, easy to moderate 20 milers would have been more beneficial in retrospect.

Week 2

After one of the hardest weeks of the cycle, I was very happy to be done with workouts long, marathon type workouts. That said, two weeks is a long time to just sort of run aimlessly. Workouts (that you're slightly scared of) provide a very nice stimulus with intermediate goals and a mini recovery cycle. As you can see I didn't get too creative (I think I ran the exact same route 3 times this week). My goal here was to rest from marathon pace running while continuing to run somewhat consistent volume. I ran 2 hours for my final long run. This was probably a bit too long in retrospect, but I took off the day following so I don't feel too bad about this one.

I also did a mid-week 6 x 1k which went pretty well:

"Did 6 x 1k with Strubbe, Javier, and Andrew: 3:21, 3:15, the rest were around 3:10. Pleasantly surprised to feel decent during this one. Pretty cashed after the 6th one though. 2 min recovery between reps."

After so much running at or around marathon goal pace, I thought it might help break the week up and be good to do a bit of running at 5k pace.

Finally, due to additional rest/fitness coming around/boredom, my runs became much faster on average (let's say from ~7:45 average pace to more like 7:00).

Week 1

The first half of this week was an extension of the previous week. I was sick of running 8 milers, but I was also afraid that if I didn't run at least 8 miles, my body would stiffen up and not feel very good. I was very relieved to make it to Thursday prior to the race as I more or less let how I felt finally dictate how I ran. I was sick of running so I basically just warmed the legs up.

Friday, I alternated fast/slow 200s on the track for 1600m with a mile warm up and cool down. I wanted to get the blood flowing a bit faster as I knew I'd be sitting on the plane. Little did I know I'd be driving!

I was pretty happy with how my taper played out. I'm not a fan of cutting mileage significantly since I don't feel like I'm running too much mileage to begin with, however I did feel like reducing intensity 10 days out while keeping volume consistent, then slowly dropping volume until you're just relying on your body seemed like a good way to taper down for a goal race.

Unlike my first two marathons where I feel like stumbled on success, my previous three less successful cycles  (four if you count failing to even start in 2011) along with this mini-cycle taught me a lot about what sort of training I need for low 2:30s fitness:

  • Appropriate recovery, typically incomplete recovery in order to simulate the fatigue of the marathon distance, prioritizing recovery before and/or after key workouts in order to stay injury-free. I think Luke Humphrey does a pretty good job describing this in Hansons Marathon Method, he calls it "cumulative fatigue." I'd also lump in self/preventative care. I've been able to find a routine that has kept my lower legs from preventing consistent training so far.
  • Longer (hard) long runs (I count my 2:42 in Boston as one of my key long runs as well as my 2:49 in California). Now this idea is very Canova-esque as my Boston run was about 95% of my Grandma's effort for 100% of the marathon distance.
  • Some running at faster than marathon pace, 5k pace for me (including a few races). This will not feel very comfortable or build your self-confidence much, particularly if you're used to running faster at shorter distances.
  • Regular cross-training. I didn't really included this in my earlier write-ups as I've never viewed bike commuting as training, but I certainly spend enough time on my 11 mile round-trip bike commute to count these efforts a significant aerobic stimulus. I plan on starting to log these consistently for my next cycle. I realize now that when I was running well in the marathon, I was also doing a pretty decent bike commute on a regular basis.

Finally, I also drew a lot from Matt Flaherty's 2:25 at the 2013 Napa Valley Marathon which occurred after he was sidelined for much of 2012. Taking off the final two months of 2013 and spending January 2014 splitting time between the pool and the roads, I had my doubts about getting into low 2:30s shape this calendar year, but it certainly helped me to review Matt's record and not put too many limits on my own running. I also took a lot of ideas as well as inspiration from Rich Heffron's build up to the 2013 Grandma's Marathon where he posted a nice 2:31:21 PR. Rich started his build up in 2013 at nearly the same time I did in 2014 so it was very helpful to track my own progress against his. My hope is that someone else will be able to use these blogs to join Rich and I in the Chicago-area low-2:30s club! Thanks guys!

What resources have informed and inspired your running?

Saturday, June 28, 2014

Race Recap: 2014 Grandma's Marathon

I'd be remiss if I didn't begin with a thank you: thanks for reading, and for the kind, supportive texts/tweets/posts/photos/tags/etc!

I ran my final long run 7 days prior to the race, an easy-ish 2 hours (17 miles). The week of, I forced myself to run a couple 8 milers despite being pretty tired of running/training (I ran 3-5 easy on the other days). I also forced myself to stop biking to work on Thursday. Thankfully I only had to take CTA to/from Niles Thursday as I was able to work a half day from home on Friday before leaving for the airport.

After rushing to O'Hare (I'm usually late-ish), my flight was canceled shortly after arriving (late) to my gate. This was about 16 hours prior to the 7:45am start of the 2014 Grandma's Marathon.

Standing in the customer service line at O'Hare, I decided that my best course of action was not to find another flight but to drive. Even if I was re-booked on a later flight, how could I trust that it wouldn't also be cancelled? On my shakeout earlier in the day, I came to the realization that the time had come to be stubborn. Training without injury is a dance of compromise, changing or shifting plans in favor of consistency. Racing when the fitness is finally present is about courageously/stubbornly pursuing your goals: maintaining the pressure and not backing down or changing course when things get uncomfortable. It was a shift I was not so sure I had prepared to handle. That said, the first challenge came much earlier than expected when my travel plans fell through.

I felt good about driving, but I could not have done it without help! My parents kindly shifted their weekend plans in order to allow me to use their second car to make the drive to Duluth. Meg and Bess who were already in Duluth were able to pick up my race packet and room keys as I'd be arriving much too late to do either.


Arriving around 1am, I ate some food (two bags of microwavable rice if you must know, should have just done one bag), prepped my race gear, and rolled out my legs in an effort to mitigate the effects of 8 hours of sitting in the car. Getting to sleep at 2am, I was happy to finally be in Duluth. Having done the first portion of the drive up to Duluth many, many times driving to/from Carleton College where my sister, Rachel, and brother, Jonathan, went to school, the drive it self didn't really bother me too much. I knew I was capable of making the drive solo. The lack of sleep didn't really bother me either as my sleep as been somewhat inconsistent of late and prior to my fastest marathons I hardly even slept the night prior due to nerves. They say it is two nights prior that really counts.

5:00am came quickly, but I still felt good (not groggy or tired) when I woke up. I went for an easy 10 minute shakeout on the St. Scholastica campus where we were staying (I'd stay there again, it was great!). The legs felt pretty good, not great but good enough. We took the 5:45am bus to the start which picked us up from just outside the dorm where we were staying. Once in Duluth (haha), pre-race logistics were pretty painless.

We were fortunate to have a cool, but not cold day which made the pre-race waiting much more tolerable. That said, I can't believe I forgot any type of throwaway garments and warm-up tights for the start line. It ended up being totally fine, but in the moment I could have used a little something.

On the start line, they dropped the men's and women's elites in front of us normal folks so there was about 60-70 (?) runners already a head of me. Which was more or less totally fine. I hoped would help me stay controlled over the first mile or so.

When the race finally started, I started slowly, keeping in mind the task at hand, but not as slowly as in Boston where I split a 6:35 first mile. I split 6:10 with an approximate 6 second delta between gun and chip times. So I was just about perfect, pace-wise. The first portion of the race, I was just trying to run as comfortably as possible, as close as possible to 5:55 pace. 6:10s, 6:05s, 6:00s, were permissible as long as I was comfortable until at least mile 20-ish. I was trying to replicate my memory of cresting Heartbreak Hill feeling good aerobically (unfortunately that day, my muscles were totally trashed and were the limiting factor).

Without the elevation profile of Boston, I wasn't sure how to segment the Grandma's, however after being pleasantly surprised after feeling out the first few miles, I decided that the segmentation that Dan Daly had suggested for Boston was probably still applicable to Grandma's Marathon (and perhaps most marathons now that I think about it). Specifically this entailed:

  1. Starting conservatively
  2. Running goal pace, strong and steady through mile 17 (in Boston this is where the Newton Hills begin)
  3. Surviving miles 17-22 (the Newton Hills, typically my mentally toughest miles regardless of the course)
  4. Unleashing the kraken on miles 23-Finish
Miles 2 and 3 were 5:50 and 5:52. It was here that I began to trust a bit more in my intuition that my run at 13.1 Chicago was probably pretty close to marathon pace (I ran 1:16:47 (5:52 pace), but only had one gear the whole race). I was still cautious and backed off a bit, hoping to run 5:55s through mile 13-17.

I ended up splitting 6:01 for the 4th mile, but then put together a nice string of mid 5:50s: 5:54 and 5:54 for miles 5 and 6 then 11:53 (5:57 average) for miles 7 and 8. It was here that I got to chatting with Adidas Running Rep, Ben Kampf. Having a full blown conversation during a race is a weird experience, but I enjoyed it immensely. It took my mind off the miles for a moment, and kept me relaxed and hopeful I hadn't gone out too aggressively.

We slowed a bit in mile 9, splitting 6:00 and I broke away from the group I had been running with at an aid station and forged on. I was still pretty focused on running 5:55s, telling myself that I needed to stay as comfortable as possible through at least 15 miles. Mile 10 came pretty quickly and was the first time I really started to feel a bit of fatigue. Splitting 5:44, I pushed any irritation at my inconsistency out of my mind and backed off a bit.

Miles 11, 12, and 13 were a bit slower than I would have liked, but I found myself still clicking off sub 6 minute miles despite a very aggressive 10th mile so I couldn't be too upset. Splitting 5:58, 54, and 59, I found myself crossing the half-way point feeling pretty comfortable in 1:17:45. I was on pace to even split a 2:35:30 which was just a bit off one of my goals of running the sub-2:35 Fleet Feet / Nike Racing sponsored athlete qualifier. I figured with how I felt, I could find 30 seconds over the next half so I was encouraged a bit though still plagued with doubts as I've gotten to half-way in every marathon I've run still on or around my goal pace. The carnage usually ensues within just a few miles.

I told myself at half-way to hang tight and run comfortably for another couple miles to mile 15. Then revised my thoughts and told myself to chill until mile 17. Then mile 20. I've had too many races become death marches in these middle miles.

That plan went out the window when I was passed just after half-way by a guy running just a bit faster than my planned mid-5:50s. We ended up running 5:45 for the 14th mile. At that point, I decided to back off a bit, but to try to start running 5:50 pace. I was still feeling good and I figured that had I shot myself in the foot by running the earlier miles too fast, there was nothing I could do about it at this point in the race.

The next few miles went by pretty quickly as could see a pretty big group a couple hundred meters a head that I told myself I wanted to catch by mile 20. I hit 5:50, 5:47, 5:51, and 5:49 for miles 15, 16, 17, and 18. Then split 11:31 (just off 5:45 pace) for miles 19 and 20. I managed to catch up with the group I was trying to run down that included the top American woman as well as a couple guys from Lincoln Running Company Racing.

I had managed to survive to mile 20 without hurting too bad (it wasn't easy, but I wasn't totally suffering).I kept on telling myself that after I took my last gel at mile 21 I just had to run a sub-30 minute 5 mile tempo. Then I decided to break things up a bit more, using other runners on the course to motivate myself. I selected my next target and told myself to push slightly to catch him by mile 23.

The final miles contorted themselves in time seeming both short and long. I ran no slower than 5:50 over the last 10k, splitting a 5:38 for mile 25, my fastest of the day. I was able to pick off a few more runners over these final miles and received some well appreciated cheers from bike-mounted Chuck of Brooks Running and Dan and Allie Walters (if you're on Facebook and like running you should follow Dan Walters Running)!

Crossing the finish line less than two minutes off of my PR felt great, I laughed with relief and joy. I hadn't come closer than within nine minutes of my PR over the past three years and it was beginning to be difficult to believe I'd ever be able to achieve my goals. The marathon can be a cruel event and apparently I have been slow to learn my lessons.


I hope to follow up this race recap with a bit more of a dive into the last few weeks of the training cycle and the race itself to pull out some of the principles I think others can apply to their training and racing. Check out my race review on BibRave. The short review is that Grandma's Marathon is a must-run American marathon. In my opinion it is up there with Boston, particularly if you want to run fast as the field up front is very deep. They did a great job producing the event.

At Grandma's Marathon, my expectations aligned with my fitness/reality. Can you share a time when this happened for you? What were the key factors driving this alignment?

Sunday, May 11, 2014

5 Reasons to Bike Marshal


"What's a bike marshal?" you might ask.

Bike marshals help race directors keep race courses safe for runners. They act as eyes, ears, and voices for the race. Since they're very mobile, bike marshals help clear the course for runners, can respond to emergencies, and help keep race organizers posted on the locations of runners on the course.

I've been volunteering as a  bike marshal for a couple of years now. Here are some of the reasons I continue to bike marshal:

1) To meet new people.

(photo credit: Julian Reggans)

I've had the opportunity to meet and work with a wide variety of interesting people working as a bike marshal for a variety of events over the last couple years.

2) To gain a greater appreciation for the opportunity to race.


(photo credit: Wendy Shulik)

After being intimately involved with the logistics of a race, I have come to really appreciate the time and effort organizers and volunteers commit to make events successful.

Have you run a race that was very well executed? How about one that was poorly done? Take 5 minutes and write a review on BibRave, the place to find and review races on the Interwebs!

3) Take a break from running while still staying connected to the running "scene."

(photo credit: Peter Mone)

Whether forced by injury or by choice, it can be good to take a little break from running or racing. Volunteering as a bike marshal is a great way to keep you in the loop with your running buddies, and since you'll be riding the course at least a couple times, you can enjoy the post-race festivities guilt-free!

4) Gain a greater appreciation for runners.

(photo credit: Jenn Kincaid)

Runners come in all shapes and sizes! As a bike marshal you may get an opportunity to ride with the leaders of a race or maybe you'll be assigned to keep tabs on the back of the pack. Either way, I've learned to appreciate and be inspired by runners of all levels.

5) Help others achieve their running goals.

(photo credit: Kyle Larson)

It's totally cheesy of course, but without each volunteer, there would be no race for runners to test their meddle against each other, the elements, the distance, and themselves. Bike marshals help contribute to a healthy, safe environment for runners.

Sound interesting?

Contact me at daniel.kittaka@gmail.com if you're interested in becoming a bike marshal for a local Chicago running event, I coordinate bike marshals at a number of Chicago races throughout the year!

Already racing or out of town?

Share this blog and help me recruit bike marshals!

Thanks for reading!

Thursday, April 24, 2014

Race Recap: 2014 Boston Marathon

First off, thanks for reading and for the kind, supportive texts/tweets/posts/photos/tags/etc!

I've been terrible at keeping this space up-to-date for the last 8 weeks or so, but I wanted to make sure to get down my initial thoughts about my 2014 Boston Marathon experience:

The race itself presents some pretty interesting logistical challenges as it is a point-to-point course. Of course one of the biggest perks of the Boston365 program is that we got to ride in a chartered bus (instead of the race provided school buses) and could wait (as long as we wanted) on the warm buses. This was great for the first couple hours, but by about 9:10 am, when I began walking to the start corrals, it was nearly warm enough outside to stand in a singlet and shorts and not be chilly at all (a slightly ominous sign, but at least it wasn't pouring rain).

The walk over to the corrals was filled with greeting various other Chicago-area runners and in my corral (wave 1, corral 2), I quickly found a group of guys I knew from Chicago. Once in the corral, I was thankful to have read about Sage Canaday's hilarious attempt to pee into a bag at the start of his Boston Marathon experience in 2010. Instead of a bag I chose a 20 oz. Gatorade bottle which served me well.

After the gun start, we seemingly very slowly moved in the direction of the start line, ultimately crossing the timing mats around 45 seconds after the gun. I fell in step with Chicago guys, Jason Ream and Craig Taylor. All three of us were focused on a sub-2:40 finish and a very conservative start.

Our first mile was a very pedestrian 6:35 which made me pretty uncomfortable knowing that we had run some pretty significant declines and had perhaps been actively breaking during this mile. I stuffed any fears away, hoping I'd gain tens of seconds back charging into Boston after mile 22.

The next few miles were conservative but not slow as we ran between 6:00-6:10 for miles 2-5. I was feeling good, but not great and was hoping that I'd really be able to get into a rhythm when we dropped the pace below 6:00. The roads were crowded with runners and spectators. So much so that it was difficult to see the aid stations early on. I immediately started drinking water and after the first couple stations also started dumping water on myself as it was pretty warm.

After mile 5, the course flattens a bit and we started trying to get a bit of time back from the slower early miles. We started running our miles in the mid-5:50s. Jason fell off a bit. The pace felt a bit hot and Craig and I had to do a fair amount of weaving as we were already passing slowing runners, but I decided I still felt like I had enough in the tank for the Newton Hills so I kept it up. 

By mile 10 or 11, my left quad was starting to bother me.  Anytime you feel something like that before the half-way point in the marathon, you know you're in trouble. That said, I kept relaxed and enjoyed high-fiving some of the coeds in Wellesley around mile 12. By half-way, the discomfort in my quad hadn't gone away and I considered slowing down, but I again decided that otherwise I felt okay and that slowing down wouldn't necessarily make running on a sore/strained(?) quad less painful. 

Around mile 14 or 15, I ran into Boston365 runner Andrew Kaehr and tried for a short bit to pull him along (while simultaneously dropping off of Craig's pace). After this failed attempt, I regrouped and began setting my own rhythm for the first time in the race this allowed me to feel a bit more comfortable as I was just about to enter the famed Newton Hills.


Running the Newton Hills with fellow Chicagoan Rob Chenoweth.
(Photo credit: Jason Dement)

The Newton Hills are a bit of an enigma as the final hill is somewhat appropriately named Heartbreak, but at the same time they're often down played by experience marathoners. I had made it to Newton, MA on pace and ready to tackle whatever was in store. I was hurting, yes, but generally still running okay, I was happy and hopeful that I'd still be able to pull this one out of the fire. As we began climbing, I noticed that the inclines were taking pressure off of my left quad! I was passing people left and right (literally) the first three climbs and felt good. I had even almost caught back up to Craig. The only problem was that I was getting caught between climbs as it was painful to run downhill and even on flat surfaces. By the time I got to Heartbreak, I was beginning to tire as the rolling terrain was starting to wear me down. I also knew there is a pretty significant descent the mile following which didn't bode well for how the shorter descents had been going. Heartbreak was long, but that's about it. The pain kicked in as soon as I crested it. My quad was shot and I couldn't really use the downhill portion to my advantage.

I went deeper into damage control mode (versus racing mode) and tried to stay as smooth as possible while still moving towards the finish line. It felt like I was crawling along, but really I was running around 6:40 pace (then 7:00 pace for mile 25). I had wanted to get to 22 feeling good, read to "unleash the kraken" in the words of Dan Daly, but instead I was just trying to keep myself going. It felt like I had eons to deal with the disappointment of this development. I did my best to let the crowds carry me (and they did) and I also did my best to enjoy the experience. Jason, who had held back earlier blew by me.

With 1000m to go (underneath the Mass Ave overpass), I knew there wouldn't be anymore quad pounding declines so I decided to do my best to run hard through the finish. I was a bit surprised at how much I had left. I took the right on to Hereford feeling pretty good and passing some runners. I took the left on to Boylston and picked it up again. The stretch to the finish seemed never ending and I did my best to stay engaged mentally, but I probably slowed down after the 26 mile marker.

Looking back on my race, I am disappointed I wasn't able to run more strongly in the final 5 miles. I don't mean this to be an excuse at all, but based on this experience, the Boston Marathon course is hard to train for in Chicago, specifically it is difficult to prepare your legs for hard (marathon pace) downhill running. Sage mentions the 10 x 1 mile workouts he did downhill when preparing for Boston with the Hansons. No doubt 1-2 of these sessions would have been helpful in my preparations. I also could have done a little more of a warm up before the race to loosen the quads and slowed the second mile down a bit (6:35 to 6:08 is a pretty big jump). Other than that I would say I am pretty satisfied by my performance and am happy to have made it to the finish line healthy (not needing 2 months off unlike my previous couple marathons). The 2014 racing season is just beginning and I am optimistic about future success!

It is a bit embarrassing to admit, but I did not really understand how much the Boston Marathon means to the people of the Boston area, other participants, and the running community in general. Prior to this experience, I was certainly guilty of a certain cavalier attitude towards the event (rather foolish, I know, perhaps this was also a way to dissociate from the pressures of performance). While at its core, a running race, the Boston Marathon more so than any other race in which I've participated, reflects the hopes and dreams of the watching world, its host community, and its determined participants.

For me, the 2014 Boston Marathon was a gift from the people of the Boston area, an opportunity not only to leave behind terrestrial cares for fleeting moments to chase a dream, but to be celebrated for this act. The Boston Marathon is my reminder that racing and running are valuable because these acts require and inspire hope.

What does the Boston Marathon mean to you?

*For my thoughts on the 2014 Boston Marathon weekend experience... Check out this blog here.