Mossman Park City Olympic Distance Triathlon Race Report

It's good to be back.

That is, it's good to be back in racing shape.  It's been a long year thus far, mostly due to two bouts with injury (hamstring and calf) that eliminated about 3 months of running from my training.  Still, I raced earlier this year though not in top form, and while I achieved results that were OK, I clearly was not firing on all cylinders either in training or racing.  But after months of PT, pool running, massage, and extra amounts of swimming and cycling, I was able to finally put in two months of HARD training, courtesy of my coach, Ray Kelly, to prepare for the series of races in August and September...starting with yesterday's Mossman Park City Olympic Tri.

Park City is just about the flattest race there is.  It's also a 5-lap bicycle/2-lap run course, which isn't everyone's favorite, but I enjoy that style of racing.  I'd been putting in a LOT of work and was walking around starving and exhausted most of the past few weeks.  I enjoyed working out hard in all three disciplines, but I'd forgotten what it felt like to be in the midst of that sort of build, but it all was coming together as I got ready to race. Sessions that included numerous run/bike bricks and transitions as well as a lot of power on the bike helped. By race time, which was 6:30am (ugh) on Saturday, I felt ready and relatively rested.

The swim looked easy - swim way right, turn left, follow what looked like a straight line for a while, make a sharp left, swim in.  I was the second wave, and while I was startled by what seemed like a quick start after the first wave, I took off. I also saw people in the first wave (2 minutes ahead?)...walking. It seems the tide was WAY out and as I was swimming, I did notice that my hands weren't very far from the sandy bottom.  Nearing the first buoy, I did stand and dolphin a few times, but went back to swimming so as not to tire out my legs. After the buoy, the water deepened, and though I swam a BIT left of the middle buoy, I stayed on course and had a strong swim. Indeed, it was a PR swim for me in 21:21 (including the run from shore to T1), 20th overall and in the top 7%. The hard swimming has totally paid off this year as all of my swim finishes have been top 10% for the first time ever.

Into T1 and relatively quickly (1:00+) out and onto the bike (note - not putting on socks helped here but hurt after my run racing flats ripped up my feet - more on this later).  The road was pretty clear for the first lap and I stepped on the gas. I was aiming for close to 1:00:00, so I had 12-minute laps in my mind, which meant 24-25mph.  I tried to stick between 24 and 25, but I was under and over throughout the first few laps, and as the crowd of people entering the road on bikes increased and I started to feel the ride, the speed came down just a bit.  NO ONE passed me, however, which made me happy, and the turns were not an issue at all even with the crowd.  I finished the bike in 1:02:09 (sub-1:02 without the run to the timing mat), another PR on the day.  I ended up with the 9th fastest bike overall (top 3%), and was happy having hit my goal.

In and out of T2 in under 40 seconds and onto the run. I felt comfortable at the pace I started (which felt like it would be low to mid 6s per mile), which was good. I looked ahead to try and tell how many were in front of me and if there was anyone I could target, but only saw one or two people. I figured that was good in that there'd be few ahead of me.  As I got toward the turnaround on the first loop, I discovered a lot more people on the road than I'd thought and went "uh oh" and figured I'd need to pick it up, which was sort of my intent after the first loop.  Good idea - but not happening. I went through 2M in 13:00 and was somewhere between happy and worried...happy that 6:30s felt relatively easy but worried that the effort only garnered 6:30 pace. I was 19:40 at 3 miles and realized that I wasn't going to be picking up the pace and instead tried to maintain where I was. This became hard to do and I lagged in the 4th and part of the 5th mile. Friends ahead of me yelled encouragement (or joking insults meant to encourage), which helped, and I tried to pick up the pace. I could see I was gaining a bit on some ahead of me, but not much.  The finish line was - unfortunately - visible for the last mile and a half, and it felt like it would never come.  I kept trying to pick it up, but aside from tired legs, my increasingly bloody feet (I didn't look down but I could feel several areas on both feet that were losing skin) were hurting.  Fortunately, I didn't see anyone close that was in my AG, so I just held on and pushed a bit through the finish.  This was a tough run and showed I have a lot more work to do to try and get back under 40:00 (distance...strength...tempo). I was 42:22, or 6:50 pace, WAY slower than I intended (6:30s or better).  I took my shoes off immediately after crossing the line and walked painfully back to transition to clean up.

It took a while, but I ultimately found out that I'd won my AG -- there were so many people that miscounted their bicycle laps that the finish results were pretty skewed at first.  That makes it 4 of 5 AG wins this season (the 5th was a 2nd place), so I'm holding pretty close to my goal of age group wins in every race this year. It is a bit ironic that my swim and bike performances are now overshadowing my runs, and I'm not sure if I'm happy about that or not.  I AM happy to report that Ray's planning (augmented with just a bit of my over-zealousness) has paid off well. I PR'd on the bike riding less miles than any year in recent memory at the same time as I have come back up the curve on the run pretty quickly. I think I run more often than Ray wants and ride a bit farther as well, but psychologically and (I think) physically, I need to do that. The best thing for me, though, is to finally be race sharp and able to push hard in racing and training in all three disciplines. Bad news -- if I thought it was going to get any easier at 50, THREE guys in 50-54 beat my time yesterday.  Indeed, I believe all but 2 of the first 12 finishers yesterday were over 40 (the other two were in their 30s), which is pretty amazing considering the times (even despite the flat course).

Up next: Nation's Tri in Washington, DC on September 8!

Race Report: MiniMightyManFreezingColdSuperSprint

Last Sunday, I officially kicked off triathlon season with my first tri race.  "In APRIL??", you say incredulously? Yes! The event was the MiniMightyMan sprint, a neat race on Long Island held in and around the beautiful natatorium in Eisenhower Park.  I've done the race 3 times prior (once was a conversion to a duathlon due to problems with the pool), and it is a salute to insanity given the distances (400M, 6 miles, 2 miles) and related neurosis-inducing (or supporting) racing.

While the weather looked like it would cooperate with respect to lack of rain, race day dawned with the temperature at 37 degrees.  UGH! That didn't bode well for swim-to-bike or the bike ride itself, but hey, what does one expect in April (yes, I know, "spring").  But I drove to the race and readied myself for the conditions. 

This is a packed race filled with those taking advantage of the pool swim and short distances to try their first tri, and I encourage others to tackle this for the same reason.  However, the crowd made setting up transition a bit of a challenge, especially after the spot I "reserved" for my bike on the rack by strategically placing my towel and gear whilst I went for a warm up ride was taken over by folks with mountain bikes during the 10-15 minutes I was riding.  I ended up just squeezing my bike in and hoping for the best later.

I was able to jog a bit and get in a good warm up swim.  I was a bit worried about my calf as it had been sore from a track workout earlier in the week, but it felt like it would give me at least the 2 miles I needed for the race.  After warm ups, we went to gather for the start, including a moment of silence for the Boston victims and the National Anthem. 

The race has a time trial swim start; that is, we line up according to our predicted swim times and jump in rapidly one after another.  I figured I'd swim 6:00-6:15 and lined up accordingly.  My start came up and I was off!  I felt great in the water, actually better than I ever had at this race.  I passed two people and did not get passed myself, which was a surprise.  After snaking back and forth through the 8 laps, I climbed out right on schedule -- my time eventually was officially recorded at 6:16, which was more like a 6:05 if you subtract climbing out of the pool and running across the timing mat on the deck.

And then, the COLD hit me.  We ran from the pool over grass to our bikes in transition, and the chill and wind on my body was quite a...rush.  Got my bike gear on, extracted my bike, and ran out of T1.  I mounted the bike to start riding and HOLY CRAP WAS IT COLD.  The first 3-5 minutes of that bike ride were among the coldest I have felt racing.  Fortunately, getting into the aero tuck helped as did furious pedaling.  Around the first turnaround, and I was confronted with the lovely wind, which slowed the ride from 23+mph to 21+mph in that direction.  I felt stronger with every lap, and after the 3 laps, rode back to T2.  Bike time was 14:05 (no, the course is not an accurate 6 miles).

I had a bit of trouble re-racking the bike given the crowded conditions and wasted a bit of time, and I almost ran out with my helmet on, but I left T2 and focused on the guys ahead of me.  I wasn't sure my place, but I could see two runners and started to work to try and catch them.  I caught one at the mile turnaround, but the other seemed to be adding to the gap.  At about that time, my calf also tightened and I could not accelerate to try and catch him, so began a game of "try to maintain pace."  I was able to do so, and eventually finished having run an OK 12:05 for a total time of 35:04 and a 5th place overall finish and first in my AG.  Not my best time there, but acceptable given the conditions and calf issue. 

Takeaways: warmups and course preparation were key.  Knowing exactly where to go is critical in a sprint race such as this, so walking through T1/T2 and having a mental plan - and visualizing it - for transitions and race strategy were key.  Happily, this was a race for which everything pretty much worked according to plan.  Looking for slightly warmer conditions for my future races, however.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Tension vs. Force

Here's a great quote that I retweeted today from 2:04:58 marathoner (PR from Boston 2011, btw) Ryan Hall: "The art of running is finding the tension between working hard and forcing workouts. Breakthrough comes in tension. "

I think that this is true of ANY workout across sports, but I know that it is something that we confront specifically in running and triathlon every day, and perhaps even moreso, at this time of year as we step up the load and the pace to prepare to race (gee, that rhyme just developed itself).

For me, my workout yesterday was a great example of this quote at work.  I'd been feeling a bit tired during the week as a result of the intensity I had been putting into training.  Tuesday was a fairly hard bike ride followed later in the evening by a hard run, which actually went pretty well considering how I felt.  However, when I arrived at the track yesterday evening for my speed workout, I could feel in my legs that "speed workout" could be an oxymoron.  Nevertheless, I intended to put forth a good effort and get the workout into the books and into my legs.

Halfway through, after I'd run actually a bit faster than I'd intended -- a good example of the tension mentioned above since it wasn't easy but also was not a struggle to complete -- when I went to start another pickup, I felt that my legs had nothing, and I'd begun to feel some soreness creep in.  At that point, I knew that I'd be forcing the rest of the workout if I went forward, and what I did next was somewhat of a surprise to me: I did not do the next 400M repeat; instead, I just did my easy warm down, feeling that discretion was the better part of valor at that point.

We all are confronted by times at which we need to choose to welcome the tension and go a bit harder, and we are often in situations where forcing it might be the only way to complete a workout.  I'd argue that forcing it is never good as it delivers diminishing returns, either by making us more fatigued longer than we need to be or potentially opening us up to injury.  Instead, embrace those moments of tension and use them to build upon, but be wise enough not to force the issue if your body is telling you it's had enough.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

The Morning After Boston

For a variety of reasons, I really didn't feel like working out this morning when I woke up.  I was still a bit sore from prior rides and runs, but I was also still dumbfounded in the wake of the insane and tragic events at yesterday's Boston Marathon.  But like so many others that I've talked with or whose posts I've read, there is one central feeling I have: I am unbowed.

There are two photos from the race yesterday that have struck me (and many others):

This was taken by John Tlumacki of the Boston Globe, and it is a photo of a 78-year old gentleman named Bill Iffrig.  I was fortunate enough to see an interview with both last night.  Bill was just about to finish the race when he was knocked off his feet by the first blast.  As you can see, heroic police were rushing toward him and others caught in the mayhem.  But what makes this an amazing photo story to me is that Bill stated that after he was helped to his feet, the next thing he did was...get to the finish line to complete the race.

The second photo is this one:

I unfortunately don't have the credit for this, but I think it is a surreal shot of some of the 9000+ (if memory serves) runners that never got a chance to finish the race.  To me, it symbolizes unfinished business, not only for them, but for law enforcement and for the rest of us to continue on.

I chose these photos to symbolize yesterday's events rather than any of the more brutal pictures that I've seen because for me, these pictures -- and their subjects -- symbolize the heart and soul of the marathon and those that undertake it, regardless of surrounding circumstances.  When the NYC Marathon was cancelled (rightfully) in the aftermath of Sandy last November, I felt bad for those that had trained for the day, but I felt worse for those suffering from the storm's horrific impact.  Today, I obviously grieve for those killed or injured (and their families) at the Boston Marathon, but I am entirely unbowed and focused on continuing forward, just as Bill Iffrig did and as those above were unable to do yesterday.

I will be running a marathon this fall, either in Arlington, VA at the Marine Corps Marathon or in Philadelphia at the Philadelphia Marathon.  I am doing this to show anyone who would think they can suppress us -- Americans, marathoners, people -- and keep us from achieving our goals and living our lives.

By the way, I WILL work out later today.  Bet on it.

Scarred...and better for it.

A few posts ago, I alluded to the fact that I was going to write an entry about "scarring." Well, coming off of my track workout from last night, this is the perfect time to take virtual pen to virtual paper.  But first...what the heck am I talking about here?

The harsh term is somewhat meaningful in that the essence of scarring is to put your body through efforts that "scar" it - that is, essentially toughen it through effort - to prepare for future hard efforts.  For running, this translates to running at faster than race pace in your workouts to condition your body such that actual race pace feels easy(er) on race day.  There is a mantra I subscribe to that says that the race should be the easy part and the training is where you pay your dues.  While we all know that one's actual race isn't typically easy, if you've done the conditioning and the scarring right, your body and mind will both know what to expect when called upon to deliver the effort on race day, and since you would have exceeded that effort in training, your body/mind should respond with, "Hey, this isn't THAT bad.  I can do this."

Let's use my workout yesterday as an example.  First, let me set the stage: a primary goal for me this year is to once again go sub-40 minutes for the 10K in an Olympic distance triathlon, or maybe in the 37s without the swim and the bike.  The latter is essentially 6 minute/mile pace, and I know that if I want my body to be able to achieve that on race day, I will need to train a bunch faster than that before the race.  Thus, my track or speed sessions need to be geared to sub-six-minute pace.  Yesterday, my workout was 5x800M at a pace faster than my 5K race pace per quarter mile (thanks, coach!).  Ultimately, this became a set of 800s run at just under 2:50 each, or at about 5:40/mile pace.  Having done that, I know that running 3:00 for an 800 (6-minute/mile pace) will be easier.  As the season progresses, I will do two things: run that same workout a bit faster; and run longer intervals at the faster than race pace (I will likely also do tempo runs that approximate race over a distance of 3-5 miles).

You can easily translate this sort of effort to your goals and your intended pace.  One of the reasons to baseline, which I've done for myself and am now doing with my triathlon club members, is to figure out the pace at which  to run the speed sessions.  Someone running a test mile (85-90% effort) in 6:30, for example, suggests to me that that athlete might run repeats of 6:15-6:20 miles or 3:05 800s (which is basically what that athlete did this week).  Given a goal of roughly 42 minutes or better for 10K, these repeats will help the athlete prepare physically for the pace and mentally for the effort of sustaining it.

It's also important to realize that you can't simply rush into hard workouts like these with no base.  Sure, everyone can come out and run one fast workout, but you don't want to pay the price with an injury (worst case) or a week of soreness (which happens often early in the season).  Thus, I'd recommend coming in with a couple month base of miles if possible vs. starting off with speed.  If you've not put in those couple of months, there's no harm in ratcheting down the speed for a bit until you've got the strength base under you.

Interestingly, as the season progresses, it's useful to incorporate shorter bursts to facilitate turnover and leg speed.  Indeed, I often incorporate striders (essentially 50-100M sprints to open up one's stride) into warmups and warm downs now, and while I am very protective of my achilles (partially torn in 2011) and hamstring (sprained last December...getting old stinks), I will begin to add 400s and (maybe) 200s into the repertoire as the speed gets more comfortable. 

So...don't be afraid!  If you've built your base, come get scarred!  On race day, you'll appreciate it.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

The perfect distance

This week kicked off track workouts for the Rye Triathlon Club (I'm the "run captain," which means that I create workouts, provide tips, attempt to run with many folks, rely upon a cadre of volunteers to help with pacing on long runs, and generally try to help our triathletes with their running).  Although the chilly temps and gale force wind kept attendance quite low, a couple hardy souls came out to set baselines.  My workout of choice for this?  The mile run.

In this age of precise instrumentation and GPS-based watches, I still rely upon the construct of a track mile to tell me where I am in my training.  Full disclosure: I spent the bulk of my competitive running career as a miler, so it's clear that I love the distance.  But to me, not only does the mile blend elements of strength and speed, it's an easy distance to cover, AND we can all come up with an average mile pace based on the last 5K, 10K, or half marathon we've done that gives us a frame of reference.

That reference point is useful to understand one's level of fitness as well as what needs to be done to improve both now and throughout the season.  The mile is also useful in beginning to establish a sense of pace. EVERYONE that has run a mile knows the fun feeling of going out WAY too fast for the first 400M and paying for it in the 3rd 400M.  Understanding the point at which oxygen debt sets in or learning how to cruise along at a pace that's right on your border line is very important for racing. The mile brings all of this home since it's short enough to do relatively hard and long enough to allow you to think about your pace per 400M, a very useful tool to get your body used to starts, surges, and overall pacing.

Now, telling a few runners to "go out and run a mile and pace yourself" is admittedly quite hard when they don't yet have a sense of pace.  But very quickly, they realized what was too fast as my runners all did their first 400s WAY faster than their ultimate average pace would be.  But that's a valuable lesson, not only for future miles but also for racing.  Whether you're in a running race or a triathlon, going out too hard too early spells doom.  I know because that's how I ran for most of my career.  Even pacing for me didn't show up until I was too old to go out crazy fast anymore, and the discovery of consistent pacing opened up a new world of somewhat less suffering over my race distances.  Understanding the mile pace at which you're comfortable is a big part of that, both mentally and physically (stay tuned for a blog on "scarring" in the near future...no, that is not a typo).

My runners did well...both exceeded what they felt they could do, though I'm sure a certain amount of "track bravado" helped.  Still, we could establish baselines for what their track workout paces would be going forward, and we were able to create a view into what race performances might look like given work throughout the season and the ability to maintain a pace slightly slower than what they did but still quick.

Personally, I have not done a one-mile baseline setting for this season...I've done several track workouts incorporating miles and 800s at paces that I feel I should be able to handle given current fitness and recent/past performance, and thus far, my sense of my fitness has been accurate.  However, my gut tells me that I'll get out there soon just to see where I am regardless of the other workouts.  Don't tell my coach.  ;-)

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Speed Thrills

Warming temperatures and longer days herald the arrival of spring...and the commencement of formal speed work for many of us.  If you're like me, the temptation to get to the track and try on your spring (or spring loaded?) legs is intense.  If you're like many others, however, you might approach the track with trepidation, either because it's like a sideways hamster wheel or because it may seem intimidating ("Me run 400s?And what's a 400?").  OK, it MAY be a bit boring for some, but approached correctly, the track can be an awesome addition to your training plan.

Success on the track starts with consistency on the roads and trails.  While anyone can go to a track and run fast for a bit, sustained speed is based upon strength, which is based upon aerobic fitness, which is based upon...a base!  Of course, sheer speed also depends upon anaerobic fitness as well, but the mistake made by many is to launch into a lot of short/fast training -- by the way, "short" for most of us means distances of 400M (one lap) or under -- without having established a firm base or without gearing your muscles toward such efforts.  Running a fast 200 is a very different animal from running a fast mile, and both have very different benefits (and outcomes).  If you want to run bunches of either, however, you need to have established the ability to sustain the efforts in your legs, heart, and lungs.

This also is not to say that running short/fast can't be helpful, since there are definitely benefits in terms of improving one's stride, turnover, and ability to get to a faster middle distance (800M, mile, 5000M, etc.) pace.  But since most of us don't do drills or do explosive runs or lift with our legs a lot, it can be harmful simply to start out on the track running 200s and 400s.  My advice is to work into the shorter bursts or perhaps incorporate a few towards the end of a longer workout.  50-100M striders work well also after a workout (and at an easier pace before the workout) to stretch one's legs and prepare for faster work.  Indeed, striders after a long run can help work out some of the kinks as well.

So where does one start?  I'll be starting track workouts (for myself and others) in the next week or so, and I'll be doing repeats of 800M and above, likely up to 2M runs.  Depending upon levels of fitness, we might run more or less, but a decent track workout typically will cover three miles of speed (plus the rests, or intervals).  I am also a huge fan of tempo runs that can be done on or off the track, but I find it very useful as a fitness indicator to do three or four-mile tempo runs on the track.  Tempo basically means a pace at or near race pace, and the runs can be done numerous ways.  A three-mile tempo run could be done at a consistent pace or as a step down (2nd faster than 1st, 3rd faster than 2nd, etc.).  You can get a good idea of where you are relative to a 10K or even half marathon with a 3-5M tempo run, and these runs become a staple of my training in season as a source of strength AND speed training.  My marathon training, for example, incorporated 3x3M on the track; my half marathon and marathon training also incorporated track tempo runs that built from 3M up to 10M (yes, 40-laps of the track).  I also run workouts like 5xmile as a step down, one of which recently may have helped spark a friend and club-mate to a 3-minute PR in a half marathon. 

There are many variations, but the important principle is to show up with a base that can support these efforts as noted above.  Going a LITTLE faster than normal and continuing to build base is fine at this point as well.  One need not worry about going super fast at this point - it would likely be counter-productive anyway.  But going faster and beginning to get to and under) race pace has great physical and mental benefits come race day.  So get ready, take your marks, and go take a run on the track in the near future.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Race Wrap Up

Last week, I left you all with the reasons I race and a predicted time.  The reasons all held up and I had a blast; the prediction, well, not quite time-wise, but I did win my age group at the March Madness Duathlon in Central Park, NY.

EVERY race is a learning experience, and this one was no different.  Coming back from injury means that racing is a bit of a crap shoot, but I felt in decent (if not sharp and super fast) shape and able to compete.  Race day was cold - mid-30s at the start - so a good warm up was important, and I had an OK warm up, though no real ability to warm up on the bike, which I think I paid for later.

In a duathlon, effort management is paramount.  The first run needs to be quick but not over the top given the bike and 2nd run coming afterward.  For me, I hadn't launched into a fast run first thing in the morning in a while either, so I was a bit cautious.  Everything went fine, and I felt in control the whole way, remaining in my comfort zone more than I usually would...which resulted in a time nearly a minute slower than I'd done in the past, but...OK.  A fast transition and a bike mount, and off for two loops of the park.

The bike ride HURT - but I mean in terms of suffering, not injury-type pain (btw, being able to tell the difference is an important skill).  I suspect this is because I was not rested nearly enough, but since this was the first race of the season and not really a focal point, it was OK.  But WOW, the first loop of the park was not fun.  Things improved somewhat the second loop, but my bike time was also a minute slower than in prior years and well slower than I wanted.  Turns out that all the times seemed to be impacted a bit by the cold.

Off the bike to the really rude awakening of the second run.  I'd been doing bricks - runs after bikes, in this case - for weeks, and my strength is typically the run after the bike, but I felt AWFUL the first half-mile.  Welcome back to racing, I guess.  I gutted it out and my legs loosened a bit.  I was able to pick it up (or so it felt) a bit and held off a runner behind me.  I finished in 1:03:33, off my prediction by 1:48, but it was still an AG win and everything felt fine (if not a bit sore) after.

I took away a few things from the race in terms of my fitness, recoverability, and stamina.  All important lessons as the season now begins in earnest.

PS - I'm the guy in the "G" Gatorade kit.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Why Race?

I race to compete.

I race to be the best me.

I race to win - now, it's my age group.

I race to celebrate the fruits of my training.

I race because I love the thrill of competition.

If I don't win or podium, as long as I am happy with my performance, it's all good.

Let's see how this all works out tomorrow.  The race: March Madness Duathlon in Central Park, NYC.  Distances are 2.2M run - 12M bike - 2.2M run.  Prediction: 1:01:45

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Different strokes...er, strides

[Coach's note: this is not a technique entry, though there may be an attempt at that in the not too distant future]

I had a conversation with a club-mate this morning over coffee and after swimming about improving at running.  "I want to run faster," she said.  Now, I view this person as a pretty strong runner, but everyone wants to improve, right?  But I also thought she ran fairly frequently.  Nonetheless, I asked how often she ran.  "Three days a week."  My knee jerk reaction, based on many conversations with triathletes, was "Well, that's not enough!"

Later on, I thought about that automatic reaction and felt that perhaps I had spoken a bit too soon.  To be honest, I really don't think that three days a week of running is enough to drive improvement.  The basic reasoning is that I don't believe that those three days offer enough volume or provide enough base to support strong speed work or longer distance (triathletes, take heed...running well off the bike takes both cycling AND running strength).  That said, the intervening couple hours of thought caused me to reflect and think about the individual.

Obviously, there is no cookie cutter answer for how much training one needs to improve.  Someone who is injury prone might ONLY be able to run 3-4 days a week, and then perhaps not be able to run long on pavement; someone else might be able to run 5 or more days per week but not be able to sustain speedwork; and so on.  What this gets back to is the need for individual approaches and adaptations to standard thinking in terms of training and results.  3 days a week might work well for someone new to the sport to get from 11 to 10 or 9 minutes per mile; 5 or 6 days a week might be necessary - if tolerable and available - to get from 8 minutes to under 7 per mile; and so on.  Moreover, the combination of runs (and their intensity) ranging from speed to distance to recovery play a huge role in success. 

The important thing is that what works for one person may not work for another, and it is that individuality that must be considered when applying any sort of running advice or a plan.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Pooling your (running) interest

I love deep water running.
I hate deep water running.


What's the source of this love/hate relationship?  For years, I'd heard that elite athletes not only take to deep water running (DWR) when injured, but that some use it regularly as a training supplement. Why would they do this?  Simply put, the lack of impact and the effort level achieved (assuming you have the right leader/teacher) are well worth what is often a mind-numbing experience, particularly if done solo.  More to the point, however, injuries over in the last year and a half forced me into the pool, and I'm a better (and now uninjured) athlete for it.

I'd tried the elliptical. I'd tried other machines.  My conclusion is that there is simply nothing that simulates a run better than DWR.  Sure, there is no impact, and thus when you finally do hit the pavement, your muscles (thighs and calves) might be in for a bit of a wake up call, but you can absolutely get a similar range of motion and aerobic benefit from DWR.  Indeed, with the right instructor and techniques, you can get a whole body/core/run workout over the course of a class.  You can do intervals.  I have seen the light.

That said, I am quite happy to be back on the pavement, but I've learned that an hour-long (or even 30-minute long) DWR session can be a great substitute for a run.  Find a good group and some great music, and you'll find yourself enjoying the workout even as you sweat (yes) in the pool.  Want more details from an expert and class leader?  Contact Debbie Ragals at treadh20@gmail.com.

http://thebestmeruncoaching.com.p9.hostingprod.com/home

Run(ning) on sentences

Welcome to the first Best Me blog.  Within  these confines, I'll wax poetic - and sometimes less so - on everything running.  First item to tackle should be interesting: running outdoors vs. indoors.

I confess -- I HATE the treadmill just like I HATE spin class (OK, I'm a hater).  I do enough boring stuff, like cycle on a trainer endlessly and swim laps in pools, but those simply cannot be helped. Well, that and I refuse to cycle outside below 30 degrees, which may have SOME relationship to what I'll write about running here.  But I'd argue the pain factor of a 25-degree bike ride is WAY more than that of a 25 (or 20 or 15) degree run.  I've written my adage of dressing for 20 degrees warmer than it is outside when running; well, in cycling, every descent brings fresh freezing.

I've run in 3 degree temperatures in Minnesota; I've run in 4 degree temps in Hanover, New Hampshire. I often run in the teens and any other available temperature here in Westchester, and other than cold hands and toes for the first ten minutes, it's all good. There's no freezing of lungs, no frostbite, etc. assuming you dress appropriately and cover/wind-protect those areas that...demand such protection.

But some folks are as against running in the cold as I am against cycling in it, so OK.  But the thing that makes me really nervous about the tready (or dreadmill, as some call it) is that it can take you out of your normal stride, unless you are using an extra large version like elite athletes often do or have access to (though even then, you have to concentrate on lifting your foot off the tread vs. having it dragged along extra).  Now, as someone with a prior achilles problem and current (though seemingly fixed) hamstring issue, having a normal stride (and foot plant and push off) is paramount, so I loathe to hit the tready for anything more than a jog, and even then only when unavoidable or extremely practical (e.g., quick warm up in the gym).

That said, there are folks who succeed and swear by the tready, so I'll never make a broad pronouncement warning people away.  Rather, my counsel would be to see how you feel on it, make sure that you can maintain as normal a stride and plant as possible, make sure you are hydrating, and try it out.  But please don't be afraid of the cold...my default is always to get out there and run!

http://thebestmeruncoaching.com.p9.hostingprod.com/home