So, How Many Hats Do You Wear?

My photo
Pensacola, Florida, United States
Husband. *Dog Dad.* Instructional Systems Specialist. Runner. (Swim-challenged) Triathlete (on hiatus). USATF LDR Surveyor. USAT (Elite Rules) CRO/2, NTO/1. RRCA Rep., FL (North). Observer Of The Human Condition.
Showing posts with label increase. Show all posts
Showing posts with label increase. Show all posts

Thursday, May 26, 2011

15 Miles-a-Week To 26.2 In A Day: Got A Plan?

A reader of the blog post about "smart" mileage increases over time ("Your Ego Is Not Your Amigo"), was kind enough to send me a question last week:



"I have a question regarding your 10-percent increase every three weeks. How would this work if I were training for a marathon? Would I have to do a 20-mile run five times a week? I'm sure that can't be good for your legs. Do you have another training schedule that you recommend for marathons? Like your friend in the article I have also had IT band problems, which I believe was due to increasing my mileage too fast when training for my second marathon. Thanks for any help you can offer."



Most well-laid-out marathon training plans have the longest (easy pace) run of the schedule in the 16-to-20 mile range, or no more than two and-a-half hours in duration. Naturally, runners will go longer than that on race day, but those longer runs occur two or three times during the latter weeks of the training schedule.



I've shamelessly borrowed from a couple of good marathon training plans over the past five or six years:



The first one/s I've recommended were developed by Keith and Kevin Hanson, who coach the Brooks-Hanson's Distance Project. Their beginner and advanced marathon plans are not a far cry from the ones they used to train (2008 Olympian) marathoners Brian Sell and (2011 Boston Marathon womens' runner-up) Desiree Davila. The Hanson's focus is on "something of substance" training; there is no focus on one single day's workout over another during the training week. Keith Hanson has explained the (relatively) low-mileage long run feels longer because of accumulated fatigue during the rest of the training week.



Links to the beginners' and advanced marathon plans can be found at the Hanson's Running web site (http://www.hansons-running.com).



Not everyone who participates in a marathon has a particular finishing time goal...but the majority of runners who do train for a marathon have an idea how they'd like to finish. Most of them, at least the ones willing to admit, would love to run well enough to qualify for Boston. The biggest problem comes when we talk about pace discipline: One of my marathoners wanted to run a 4:00 to qualify for Boston, and probably is strong enough to run a 3:40. In her first attempt at the marathon this last November, she passed me at mile 12 (I was running the half) and went through the half-marathon mark in 1:35-1:40. I didn't want to believe she'd have a bad day, but (being the pessimist I am) I knew it was coming. After finishing my half, I went to the half-mile to go point on the course. My watch ticked off 3:55...no Deena. 3:57...no Deena. 4:00...no Deena.



Finally, she rolled by, cramping legs and all, at 4:03. She finished her first marathon in 4:07, having fought leg cramps from mile 16 onward. I told her, after congratulating her on her age-group win, that we would focus on pacing strategy for Rock n' Roll/Mardi Gras, her next marathon.



The Marathon Nation (http://www.marathonnation.us) training plans, developed by coach Pat McCrann, are based off Jack Daniels' VDOT tables. Plans are boiled down to the essentials; there's no fluff in a MN plan, which is great for time-stressed runners.



Most importantly, McCrann has a very effective approach to race day pacing. He breaks the half or full marathon into approximately 25-percent chunks; the first 25 percent of the race is run about five seconds per mile slower than goal pace. The middle fifty percent increases in pace to a point where the runner averages about five seconds per mile ahead of goal pace, and the last 25 percent is where the runner makes the tactical decision of whether to maintain (should they feel all right, or not so good) or increase the pace (should they feel very good).



I used a blend of my own speedwork, the MN speedwork and the Hanson's distance focus when training Deena. When it came to race day, I sat down with her and broke down the pace she needed to run; a particular time at 10K, a particular time for the half-marathon, another goal split for 30K...after that it was up to her whether she wanted to push the pace or hang on. She ended up hitting the splits almost exactly as I asked, ran a 25-minute personal best and qualified for Boston.



I asked her how she felt on the first 10K, to which she said, "all these people were blowing by me like I was standing still." And the last 10K? "Gosh, Coach, I was passing people left and right."



The right training plan for a distance event will get you to the starting line healthy and ready to run. The right pacing plan for that distance will get you to the finish line...ideally healthy and ready for your next run.

Tuesday, April 12, 2011

Your Ego Is Not Your Amigo


Brett and I have known each other since the summer we first started working for the Navy. I saw him win his first age group award and witnessed his phone call to his wife (he's the guy I advised to not downplay his accomplishment) Meredith in Alabama. So, I guess you can say we go back a few miles.

He sent me a running question the other day:

"I'm starting to experience some pain on the outside of my right knee after I run. For example, I did eight miles this morning and was fine while running. When I got home, the pain really started kicking in just walking around the house. The pain seems to occur at the point when I step forward with my right foot. Any ideas? It has been happening for a few weeks now and seems to come and go. I did six miles on Monday evening and didn't have any trouble. Thanks for any help. I definitely don't want to mess up my knee."

When I sent my response back to Brett, I initially suspected iliotibial band syndrome because of the location and intermittent nature of the pain. The only other overuse injury I can think of would be patellofemoral syndrome, or "runner's knee", which would have the pain at the lower margin of the knee; the IT band would be at the upper or outer margin of the knee.

Either way, Brett has an overuse injury.

He later revealed to me he went from running five to running ten miles at a time over a four-week span, which came from training with a triathlon training group at their local YMCA. "Guess I was trying a little too hard and too quick to hang with the 'A Group'", was his lament.

When an overuse injury such as IT band syndrome, achilles tendinosis, plantar fasciitis, patellofemoral syndrome comes to pass, most of the root causes are these:

1. Old, worn-out, or improper running shoes. If the runner cannot say how long (in time or miles) they have run in a particular pair of shoes they might have run in them too long. Sometimes an old pair of shoes will give fair warning by "smelling dead," or the runner might suffer from some aches and pains in the ankles, feet, knees or lower back. Naturally, the remedy would be to get into a pair of shoes which best fits the foot type. Most experienced runners know what kind of shoes work best for them. Once in a while a particular model of shoe changes construction or materials, so it doesn't hurt (no pun intended) to have a "short list" of acceptable shoe models. The major running magazines do annual shoe reviews which can make the search more simple, or a running speciality store can point the individual runner to the "short list."

2. Significant changes in training volume, terrain, or surface. A short-term (or even a long-term) business trip or a new training group can wreak havoc on a training cycle. Most good training schedules aren't necessarily (and probably shouldn't be) written in stone. I've discussed with my coach/advisor about synchronizing my workouts with my coaching; some times solitary training sessions are necessary to train at the proper (read: easier) intensity. Look closely at the recent changes, then subtract them for about three weeks. Why three weeks? That's how long it takes for the body to benefit completely from a change in training volume or intensity, or the minimum time it takes for a low-level overuse injury to begin healing.

And when adding distance/duration to a workout, the "ten percent every three weeks" rule of thumb is best. When talking ten percent, the addition of time/distance should be spread across the training week as much as possible. For example:

OLD WEEK - 30 miles/week

- Sunday - 6 miles

- Monday - Rest

- Tuesday - 6 miles

- Wednesday - 6 miles

- Thursday - 6 miles

- Friday - Rest

- Saturday - 6 miles

NEW WEEK - 33 miles/week

- Sunday - 7 miles

- Monday - Rest

- Tuesday - 6.5 miles

- Wednesday - 6.5 miles

- Thursday - 6.5 miles

- Friday - Rest

- Saturday - 6.5 miles

I've met runners who tacked the ten percent on the Sunday run, which in the example above would increase the volume of that day by 50 percent and increase the longest run of the week to more than 20 percent of the week's volume. Neither one of those are a good idea. If there's a time crunch during the week the additional miles could be split between Saturday and Sunday, but even then there would be the risk of adding too much stress too soon.

And, regardless, cambered roads and hill running can wreak havoc on the unprepared runner. Stress injuries abound from too much "new" (surface, distance, or intensity), too soon.

3. Muscle weakness, especially in the calves, gluteus medius, and abdomen. When a runner has weak muscles or muscle imbalance it puts undue strain on the rest of the "drivetrain." I sent Brett a link to a YouTube video (http://www.youtube.com/watch?v=5RC7VH3bEB4) with some exercises to strengthen his glutes and stretch the IT band. Six of ten runners who make these changes can recover from a low-level overuse injury in as little as three weeks, with the remainder recovering in six weeks. There are those cases (this coach included) where recovery can take up to six months; more of a compliance and patience issue than anything else.

Brett sent a reply which ended with:

"I signed up for a ten-miler this coming Sunday. I want to finish it, then my plan is to go back to six miles and see how I do. If I still am having problems, I'll keep backing off until I stop having problems and may look into seeing a physical therapist. Once I figure out where my baseline is, I'll start slowly increasing my distance again, only this time at a reasonable pace."

When it comes to training, and especially when it comes to recovering from an overuse injury: Your ego is not your amigo.

Monday, September 20, 2010

If At First You Don't Succeed

Got up at oh-dark-thirty a couple of mornings ago to run a ten-mile race simulation workout. If that statement coming from me does not provide a deep sense of foreboding, then stick around; the sense progresses from ankle-to-knee depth in nothing flat. Even on the most-industrious of training days, save for the ones when I visit my New Orleans friends (I have to justify my dietary indiscretion!) I don't get out the door any earlier than 7 a.m. Yes, race days are a different story, hence the simulation workout being so darn early. So, I began my early morning ritual: Feed the dog, fire up the coffee pot & await the, er, signs which tell me my body is completely awake. After dressing & stepping out the door it was time to start; why stand around thinking about what needs to be done? The sooner I start the run the sooner I can get on with breakfast & the rest of the day.

I figured the first two miles would be a bit of a slog; my body is usually in a state of denial, or shock, at the thought of running. After two miles my heart & lungs figure out what is happening & join in on the "fun." However, at two miles I began to feel some sharp pains in both of my heels. I decided to see if I could continue through the discomfort; perhaps the plantar tendons would loosen up enough to let me finish the run. At two-and-a-half miles my gut decided to join in on the chorus of complaints. Game over. Shut it down. Walk it home. Call it a day.
The law of cause-and-effect rings true in running: For every action we take, there is the opportunity for the body to exert an equal & sometimes opposite reaction...which it will if certain laws are not followed. Running places stress on our body, which it learns to adapt to over time. After a while, the stress which caused us to lay on the couch all afternoon only tires us for an hour or so; eventually we get stronger because of the stuff we first thought would kill us. See? Nietzsche was right! This is essence of training - we throw our body little curveballs to make it stronger.

The problem when we start running is, we feel too good about the first stresses & overestimate how much the body can take. That's why new runners eventually get dinged up, & old runners (like me) occasionally nurse overuse injuries - plantar fasciitis, achilles tendonitis, iliotibial band syndrome & patellofemoral joint pain, just to name a few - when we make a few too many changes in our training plan before thinking about the effect. Add some hill repeats or bridge running when you're used to training on the flats, or increase the intensity or mileage beyond the level your body can stand, & the next thing you know you are gobbling ibuprofen like it's candy.
Here's a list of some of the most common running-related (overuse) injuries, causes & treatments:

Symptom: Swelling & pain around joint (i.e., ankle).
Possible Diagnosis: Sprain.
Possible Cause: Applying weight to foot in a rolled position, while running or jumping on an uneven surface.
Treatment: Rest, ice, compression & elevation for 7-10 days. Anti-inflammatories to reduce pain and inflammation. Gradual progress to weight-bearing exercise as tolerated. See a doctor if injury does not respond to treatment in two weeks.

Symptom: Pain at back of ankle.
Possible Diagnosis: Achilles tendinosis.
Possible Cause: Tight or weak calf muscles. Too much training, hill running or speedwork. Excess stretching can aggravate the problem.
Treatment: Reduce/stop hill/speed work. Gently stretch calves after exercise, & ice the tendon area. Strengthen the calf muscles (toe raises, balancing on your toes, wall stretching). Cross train on some “easy” days.

Symptom: Muscle pain, soreness or stiffness.
Possible Diagnosis: Delayed onset muscle soreness.
Possible Cause: Microscopic tearing of the muscle fibers from exercise. Eccentric muscle contractions, like downhill running, going down stairs, and squats cause this most.
Treatment: Rest, ice, compression and elevation for 7-10 days. Anti-inflammatories to reduce pain and inflammation. Drink more fluids.Symptom: Pain along the outside of the knee and lower thigh, especially when going down stairs or getting up from a seat.
Possible Diagnosis: Iliotibial (IT) band syndrome.
Possible Cause: Common in runners who run only on one side of a crowned road. Biomechanical abnormalities, muscle tightness or lack of flexibility in the gluteal (buttock) or quadriceps (thigh) muscles.
Treatment: Rest, ice, compression and elevation. Anti-inflammatories to reduce pain. Decrease mileage. Consider a physical therapy visit for leg strengthening exercises.

Symptom: Pain under or around kneecap, worsening with activity, while descending stairs, etc.
Possible Diagnosis: Patellofemoral pain syndrome.
Possible Cause: Likely the way the patella tracks along the groove of the femur, depending on muscle strength and balance, use, & tracking. This means the cause may be from a variety of different factors, to include muscle imbalance & shoe breakdown.
Treatment: Rest. Non-impact exercise, like swimming. You may want a physician or physical therapist to coordinate your treatment with additional strengthening & stretching.

Symptom: Pain under the glute/buttocks.
Possible Diagnosis: Piriformis syndrome
Possible Cause: Shortening of the muscle and compression of the nerve. Overuse of glutes & other hip muscles can also cause piriformis muscle spasms. Other factors include gait problems, poor body mechanics & posture.
Treatment: Stretching & strengthening of the core and glutes & the best treatment for piriformis syndrome.
Symptom: Pain in the heel, especially during the first steps in the morning/of a run.
Possible Diagnosis: Plantar fasciitis
Possible Cause: Flat feet, high arches, excess pronation, weight gain, tight achilles’ tendons, sudden changes in workout intensity/time/type/surface, poor shoes.
Treatment: Nonsteroidal anti-inflammatory drugs. Stretch the achilles’ tendon. Massage the sole, achilles’ tendon & calf with a roller. Walk/run in proper footwear – no barefoot walking or running.

Symptom: Pain at front of lower leg, along shin bone.
Possible Diagnosis: Shin splints.
Possible Cause: Improper stretching, lack of warm-up, hard surfaces, improper footwear, biomechanical problems.
Treatment: Rest, ice, compression & elevation for 7-10 days. An anti-inflammatory can help reduce pain & inflammation. Gradual progress to pain-free weight-bearing exercise. See a doctor if injury does not respond to treatment in three weeks.

So when it comes to increasing the amount of mileage or time you spend running, the best rule is to not increase by more than ten percent; and that ten percent should be stretched across the week as much as possible. When looking at pace and effort, the percentage of maximum heart rate multiplied by time can provide a training stress score which can be tracked over time. Lastly, when dealing with hill/bridge repeats, err on the side of caution; easy paces and cautious increase in volume.

If at first you don't succeed in learning how to wisely increase your workout volume, don't worry. Your body will let you know it's time to try, try again.

Wednesday, February 20, 2008

Energy Conservation

Today I'm kind of in the middle of bouncing between a meeting with some HPC folks from Orlando and trying to get other research done, so today's screaming will be brief. Besides, I'm starting to figure out that fighting City Hall is more trouble than it's worth. It still sucks, but at least I see my leave and earnings statements twice a month. Near the end of yesterday afternoon I took the time to look at the web site for Peter Reid, two-time Ironman world champion (CORRECTION: Three-time Ironman world champion. Sorry, Peter. MB) and now coach. One of the articles he had posted grabbed my eye almost immediately...which is what a good title should do. The title was Want To Swim Faster...definitely something I would love to do, since I'm taking a more-serious approach toward triathlon. I know, 'what does tri-geek stuff have to do with running?' Well, more than you can imagine. While running is the third element of triathlon, the swimming and cycling elements translate well into most good cross-training programs; you can still work the cardiovascular and musculoskeletal systems without pounding your legs. So, Reid lists many of the ingredients necessary to swim faster, of which I'll try to adapt to strict road running:
1. Believe that you can swim faster. As Reid says, 'where the mind goes, the body follows.'
2. Swim more. Don't just depend on the once/twice/thrice-weekly track workout to provide speed and endurance gains. Get out and run on your own. Make certain to rest. Cross-train at a high-enough intensity to provide variety and ward off staleness.
3. Use new and existing technology. Videotape your running form. Watch videos of elite athletes and good runners to pick up on the cues they use. Compare how you look to how they look in flight. Odds are good you'll find posture and mechanical inefficiencies (if you look closely) that can add a few seconds here and there to your 5K.
4. Coaching. Goes without saying. But really, really, really use that coach for something more than a guy who stands at the trackside and tells you little more than 'five 200s, fresh...' In other words, don't hesitate to ask questions, advice, give feedback...learn what you can so you can coach yourself, if the time ever comes that you have to do so.
5. Get with faster swimmers. (I get beat on twice a week in the pool by faster, more efficient athletes who have years and years of swimming experience on me.) Running the occasional Six at Six with Paul Epstein and his gang reminds me I'm decent, but not world-beating. If I could make it down there, and be in the pool at the same time...I would. Sometimes it doesn't hurt to work out with good runners.
6. Swim faster. Add short hard stuff on a regular basis. Push the envelope every so often...not every workout, though, lest you get injured. The third week of the month seems to be the good one for me.
7. Consistency. Know how you respond to a certain level of training and be prepared to adapt accordingly. Set a training schedule and stick to it, with illness and injury being the only rationale for missing out. All right, emergencies do come; family members do show; business trips do happen. Most of the time you can plan in advance for these.
8. Make the most of your hours. If you don't like 350s on the track, do them anyway. There's a reason for them or your coach wouldn't have assigned the repeat. If your mid-week run is supposed to be at aerobic threshhold pace, then run it at that pace. You have to run the workout at the right effort, otherwise you're wasting your time.
9. Flexibility. I don't stretch because I never learned how to not fight the instinctive stretch reflex. If you can stretch, do it. But do it when your muscles are warm. Do it gently, without a lot of fighting. And if you do stretch, do it regularly.
10. Visualize. Goes back to the use of technology. There's no lack of video on YouTube for running, swimming, cycling and triathlon. If you feel like you can visualize proper form and relaxed mechanics, fast running without the use of video, then cool. I try to get my athletes into the mindset of thinking about racing during some of the last Tuesday/Thursday workouts before a big race; how to deal with the pack, who to draft off early on, how to pass when the person being drafted off tires, and so on.
11. Feeling badly in the water isn't so bad. Once again, Reid says: 'my college run coach used to say, "if you're training well, you're not training well"'. The days you feel like $#!+ at the track or on the Sunday long run are probably a sign that you were operating at your limits...for the day. So stop beating yourself up over a single effort, or a week or two of bad days. It's probably going to pass and you'll have a day soon enough when you feel very, very strong. No doubt you'll forget all about those days when you felt your training, and you, flat out sucked. Res Ipsa Loquitur.