Gary’s Fitness Blog

It’s fairly common in conversations about triathlon training today to discuss watts, normalized power, TSS, functional thresholds and intensity factors.  These terms are all the result of more cyclists using power meters to monitor training intensity and even race efforts.

I have been using WKO+ (formerly cycling peaks) for a little while now, primarily with my Garmin 305 (because I still haven’t justified the power meter expense) to monitor my run training.  The WKO+ software is really great and allows an athlete to get deeper into the training data more than any other training software and log program I’ve ever used.  Because I don’t have a power meter it does have limitations.

The biggest limitation for me is that because I don’t have a power meter, the software’s performance management analysis doesn’t give me an accurate picture for triathlon training.  Why?  Because I have no way of quantifying the work done (TSS, CTL and ATL) on the bike that allows the software to analyze the data.

As a triathlete we also have to consider swimming.  Can we monitor power in the water in a downloadable manner?  Not yet.

So as I look at the athlete’s that I’m trying to help prepare for the 2009 triathlon season (specifically, Ironman Louisville) I have several issues when trying to use a similar method for monitoring training stimulus over time:

1.  no one uses a power meter (and likely are not going to purchase one)
2.  few have a Garmin 305/405 to monitor their running workouts
3.  if they had all this equipment, it takes a lot of time to download and analyze, which they may or may not do.
4.  they have to use the power meter and/or Garmin device for EVERY workout, or they can just estimate the workouts and enter a best estimate TSS or rTSS for the individual workout (which gets us back to why use it anyway)

So, while I am very excited to see some of the data that comes from my Garmin (and yes, hopefully soon my power meter?) it is not a practical solution right now to help my athletes by using the WKO+ software and the Performance Management Charts.  (I have to say though, it is a lot of fun to spend time with the data I can get.  It’s amazing the kind of data we can get in the field better data than what we had in the exercise phys lab on the Monarch.)

How we are tracking long term / short term training stimulus:  (the post to my Ironman athletes)

In the past years I have used total hours of training as my main monitoring system. This was a good method because the majority of the exercise that I did was done at a very reasonable almost easy intensity.

For most of us, this is still going to be the biggest limiter (steady state ability and duration we can hold that intensity).

But with powermeters, heart rate monitors, gps’s, etc…. coaches and athletes are now getting pretty analytical in these monitoring methods. In my opinion, we are making a lot of things too difficult - especially for Ironman training when it matters more that we are consistent and gradually build duration. .. but ..

I realize that we all don’t have powermeters/gps’s so I’ve been thinking about how to add in an "Intensity Factor" to our monitoring.

Here is what I’ve decided to do:

A mixture of the Aerobic Points System (as seen on slowtwitch ) and Borg’s 10 Point RPE Scale (as discussed in the power training article by Dr. Coggan )

Here’s how the scoring it works:

10min swimming = 3 point
10min cycling = 1 point
10min running = 4 point

So as an example: 9.5 hours balanced week
1.5 hours (90 mins)of running: 36pts
6 hours (360 mins)of cycling: 36pts
2 hours (120 mins)of swimming: 36pts

That was just an example of how to add the total times, now to look at the RPE scale / intensity. We’ll be using the Borg 10 point scale , notice the Borg Scale is weighted so that the higher numbers are more spaced out. (Which is done for a number of physiological reasons that Dr. Coggan explains in the article also.)

Example of a workout calculation:

60 minute swim, effort at 3 RPE = 6*3 = 18pts * 0.3 = 5.4

45 minute run, effort at 2 RPE = 4.5*4 = 18pts * 0.2 = 3.6

60 minute cycle, effort at 5 RPE = 6*1 = 6pts * 0.5 = 3.0

Does this make sense? What I’d like you to do is calculate your total points at the end of each week, but you’ll need to write the "RPE" score in the comments as you log each workout.

The key to this system is that you are honest with your RPE scoring, otherwise we could just track hours. We will be tracking hours each week, etc… but I like how this system will account for the differences in intensity, plus we get to track it across all 3 sports, not just power on the bike or pace on the run.

One other data chart that we’ve been tracking:

I had an athlete that put together her own spreadsheet to track her RPE score, aerobic points and what we are calling intensity factor (which isn’t the same as IF for WKO+ which is NP/FTP).  One of the charts that she set up was to a plot of the intensity factor to workout duration.  By plotting that chart we can monitor the ratio on a week-to-week basis.

Feedback?

I would love to hear what others have to say about this concept.  We’ve just started using it several weeks ago, so until we get more data I’m not going to make any conclusions.  I am sure that those triathletes and/or runners that are used to monitoring their hard data from high tech devices with balk at the idea of using RPE.  But I’m not worried about that, I’ve come to peace with using a subjective data point like RPE.  In fact, I think that it can incorporate variables that impact training that a power meter can’t - such as psychological variables (fatigue) and health implications (early stages of sickness and stress).

Here’s a few links to where and what the EndureChallenge was:

1. How it started - Why guys need to find fitness (and life) milestones
2. When I decided what to do - Celebrating 30 years of living well
3. Great Illini Race Report - iron distance race on Sept 6th, 2008
4. Lake City Marathon Race Report - marathon ran on Sept 13th, 2008

I was able to get some data loaded into motionbased, but not all because the Garmin 305 started deleting the oldest data during the week.  I have the totals of the workouts, but not the gps data (and therefore no maps or motionbased links).  Here’s what I have:

1.  Great Illini Marathon - don’t have gps
2.  Effingham, Illinois to Paris, Illinois - don’t have gps
3.  Paris, Illinois to Attica, Indiana - Sept 9th
4. Attica, Indiana to Logansport, Indiana - Sept 10th
5. Logansport, Indiana to Warsaw, Indiana - Sept 11th
6. Lake City Marathon

It’s too bad that I don’t have the gps map from my first day of bike touring, it would be comical to see how much I was backtracking and moving around the Illinois countryside to get away from small gravel roads.  The other thing about the data during the bike touring is that I started the gps when I left the hotel in the morning and stopped it when I got to the next one at night; therefore the charts are a little odd because I stopped to eat at diners, fast food joints, talk to locals, etc.  That’s what I love about touring!

Thoughts on what this taught me about my athletics:

Lesson One: The biggest lesson that I’m taking away from this event is that I don’t need to fear Ironman.  This was my third Iron Distance race in the past three years and up to this point I think that Ironman was still intimidating me in some ways.  The biggest way that it intimidated me was (as I mentioned in the lake city race report) by making me fear a complete collapse during the run that left me immobile.  That fear caused me to develop a race strategy that was possibly too conservative.

Granted, I did have somewhat of a breakdown during the last 10 of the marathon on the 13th, but the next time I do Ironman (Ironman Louisville in 2009) I will remember that it too 2.4 miles of swimming, 435 miles of cycling and 40.2 miles of running before I finally slowed below a 7:30 pace (and I still managed a 7:22/mile pace overall).

Lesson Two: I can ride a bike faster than “touring” pace.  I have been pretty consistent over the last couple years in telling myself, “back off the bike or you won’t be able to run… back off, back off.”  If you read my Ironman Wisconsin Race Report from 2007, that was a pretty consistent theme during that ride.  I wish that I had my heart rate data from the Great Illini because I guarantee that I rode well above 145 - 150bpm, which is what I used as my ceiling (or mostly) during IMMOO last year.

The one little bit of data that I have from the bike is when I turned my Garmin 305 on during the last couple miles of the bike during the Great Illini (to have it ready for the marathon).  During that period I was sitting in the 157 - 161 bpm, which is a time that I was trying to relax and prepare for the run.  The best thing is that I got off the bike and ran well!

Lesson Three: The third thing that I learned (again) will relate to training over the next year - when you find your behavior and emotions changing, it is a good sign of overtraining.  I noticed this during the touring that occurred between the two races.  I remember sitting down in the hotel room after one of the nights of touring and just felt like crying?  No reason, I felt wasted and wanted to cry as I laid there on the bed.  You can probably see some of this if you watch the youtube video updates that I shared.

As I sit here (Wednesday, 4 days after the last marathon) I have been dealing with small levels of depression each day.  Nikki has noticed that I haven’t been in the “best mood” too.  It might be an exaggeration to say “depression”, but it is really hard to find anything to be happy about - even though I know there is a lot to be happy for.  I believe this is just another way that our mind tries to tell our body what to do and not do?  It’s not easy to get out there and exercise when you have lowered moods; therefore I’m going to listen and be very careful over the next few weeks.  I don’t want to get sick (like I did two years ago a few weeks after Ironman).

Lesson Four: I have talked about this a little bit in the race reports from both races (Great Illini and Lake City Marathon) - but when racing in endurance events, getting the mind out of the way is a major part of the race.  The body must be trained and fine tuned, but the mind must also get out of the way and allow the body to work.

Chris McDonald just did an interview over on Endurance Corner Radio where he talks about his 2nd Place finish at Ironman Louisville and 1st Place finish (and course record) at Ironman Wisconsin a week later.  It’s a great interview and he does talk about the mental challenge during Ironman Wisconsin and how it played a role in his race.  They spend a couple moments talking about the mental aspect of fatigue.

The last thing that I’m excited about is that I’ve learned about barriers that I’ve built over the years and how those barriers are abstract constraints that I’ve placed on myself more than they are real physical and physiological limiters.  That is a lesson worth its weight in gold.

So how was I going to approach the marathon at the end of my EndureChallenge journey?  It would have been easy to go into the race thinking that all I wanted to do was finish the race, but other than celebrating the transition from my 20’s to my 30’s, I wanted to try and break through some psychological barriers that I’ve developed around racing over the years.  (I’ll write more on that in some upcoming posts).

So here is how I approached the race:

1.  Even though I wore my Garmin 305 and the heart rate monitor (thanks Saori and Paul), I told myself that I would not look at the heart rate data at all during the race.  I also decided that I would only look at the watch at mile 10, 13.1, 20 and the finish.

2.  Without the feedback from the Garmin, stopwatch or race clocks (this race didn’t have clocks or timers along the course), I decided to run a pace/effort that felt doable - But an effort that was “hard”.

3.  I also told myself before the race that I didn’t want any excuses for not “meeting expectations”.  I knew that there would be periods where I would try and use the Great Illini race the week before or the bike touring during the week as reasons that I wasn’t running well - I decided before hand that those excuses wouldn’t be acceptable.  (Easier said than done.)

Race Start:

There were tornado warnings in the area and it was raining pretty hard on and off during the night, so the race was pushed back a half hour.  At one point I was nervous that they would decide to cancel the race, which would have meant that my week would have come to an anticlimatic ending.  But after some sitting around and with the race director trying to get the course remarked with chalk, the race got started.

First 10 miles:

Before the race, I heard two girls discussing how they had planned on running just under 3 hours.  I thought that if I was going to see what was possible, why not latch onto them and keep them in sight as long as possible.  And hope that they don’t go out in 2:50 pace, because I wouldn’t have any way of knowing.

As we took off, it felt pretty comfortable to run with the small group of 4 or 5 that chose to run that pace.  I knew it was harder than I’d run in some time, but not unthinkable.  The race consisted of 3 loops (1,2,3) then you ran over a bike path to another division around a lake and ran 5 more loops (a,b,c,d,e).  I ended up running just behind one of the girls through loop d (when she started to pull away a little).

I crossed the 10 mile marker at 69:xx minutes.  “Holy Crap,” I thought, “I can’t believe that I’m actually running this fast still.”  It felt good at that point and around mile 12 the second girl started to run next to me.  As we ran back through the bike trail towards the half way point she said that she’d hurt her knee and that she was going to fall out at the half.  I was a little bummed that I wouldn’t have anyone to run around, but also knew that with all the loops there would be ways to see others and pace myself.

As we ran through the half, my watch said 1:31:xx.  Still going pretty well, I thought, but wondered how long it would last.

After running loop 1 and 2 of the second half, I knew that I was going to be in trouble - so I decided to take a conservative approach to my walking breaks.  I decided to walk 30 seconds at every other aid station,  I had been doing 30 seconds every 3 to 4 miles.

It seemed to help as I was able to run strong during the run portions of my race.  The a and b loops went pretty well, even the c and d loops were steady (although I could feel the pace slowing quite a bit).  I ran through the 20 mile marker at 2:24:xx, pretty good I thought.  10k to go.

I could feel the pace slowing more and more, along with my legs beginning to hurt significantly.  Many times during a run/race when I feel the pain and hurt begin to set in, I have confidence that my legs won’t give out (like on the run during the Great Illini last week).  This week it didn’t happen.  The last 10k was pretty rough.  I never stopped moving, but at times I really, really wanted to.

Finish: 3:17:xx (results not up yet)

Final Conclusions and Thoughts:

Most people say that I should be incredibly happy with how the marathon turned out.  To be honest, I don’t think that I’m ever fully excited about a race result.  Even at the Great Illini I wasn’t too happy and I set an Iron Distance Triathlon personal best by 12 minutes.  There is always something to improve when I look back.

But, that wasn’t the point of the week or the marathon.  It was to celebrate and I feel like that is exactly what I did for a week.  How lucky am I that I have the ability to get out there every day and push my body to the limit, without my body caving in?  How lucky am I that I have the health that allows me to be active and mobile everyday?  How lucky am I that I have so many friends and family that were supportive and interested in my crazy-little-mess-of-a-week?  How lucky am I that I have a wife that loves me, puts up with this craziness and supports me and even encourages me?

At one point early in my collegiate career I sat down and wrote out a sketch of goals in most of the major areas of my life.  The areas included:  education, financial, career, athletic and personal development/spiritual.  As I look back, many of those goals are starting to become a reality or have already been realized.  I remember after running my second marathon in 4:00, I thought that qualifying for the Boston Marathon may never be possible.  I sit here today a little dissappointed that I didn’t run under 3:10 a week after an iron-distance triathlon and 323 miles of bike touring - YES, I am a very lucky guy.

Athletic Conclusion to Marathon:

I am almost always very conservative when I develop a race strategy for triathlons and marathons.  I rather be conservative and finish well then go out and limp my way home - is my normal line of thinking.  While this often proves itself well in triathlons and marathons, I also realize that by always being too conservative we may never realize our full potential.

Fear of Failure is often the biggest limiter we face in endurance athletics

As I mentioned above, I did not want any excuses or reasons for not giving this marathon everything I had.  This meant I had to be ok with walking, stumbling or crawling across the finish line.  So I gave it a shot during this marathon and I feel very good about the opportunity my mind allowed my body have.

So was it realistic to run under 3 hours or even 3:10 at this race, with this training or in this situation?  Probably not, but it sure felt good to at least try!

Last Sunday (7/15/07) was my first race simulation ride (in 2007) as I prepare for Ironman Wisconsin. The ride was a workout that I took from Gordo’s bike workouts within his “Coaching Ironman Athlete’s” document. The specific’s of my workout were:

Lap 1 - 36.2 miles, 2:10:18, 125bpm ave, 159bpm max
Lap 2 - 36.2 miles, 2:03:58, 134bpm ave, 165bpm max
Lap 3 - 36.2 miles, 2:01:47, 135bpm ave, 169bpm max

Lap 1 description: made sure to ride what I thought felt “easy”, used my hr monitor to keep it in check too, tried to not let hr spike on climbs/hills. Nutrition: 3 egel’s, 1 bottle of xtra strength gatorade (1 bottle = 200kcals), 2 salt tabs, 2 bottles of h2o.

Lap 2 description: rode a little harder but never felt like I was pushing it, as the Gordo workout says, I tried to ride at Ironman effort/pace, let myself ride a little bit harder on the hills. Nutrition: 4 egel’s, 1 bottle of xtra strength gatorade, 2 salt tabs (I use salt stick), 2 bottles of h2o.

In transition: ate a honey bun.

Lap 3 description: rode the loop backwards, primarily to see Nikki and check on her and b/c Jeff couldn’t ride entire loop again. Tried to push and “work” the hills. It didn’t feel easy, but as you can tell from my results, my body didn’t seem to react much differently… (more later on this, see: fatigue below). It was very difficult to eat any calories! I felt like burping or vomiting for about 20 miles of the 36. (I think a really good perspective on this was written by Jeff Shilt, MD titled, “Tips to help prevent Gastrointestinal Breakdown“)

What I Learned about Nutrition last year:

So I don’t repeat too many things, I’ll share two posts I wrote last August in my attempt to straighten out nutritional plans for the Runovia Triathlon:

1. Figuring out a racing nutritional plan #1 - 8/6/2006

2. Racing nutritional plan #2 - 8/15/2006

Here were the highlights of those lessons:

- eat more than you might think you need (in most cases)
- monitor fluid intake; h2o and sports drink
- drink early in ride
- eat early in ride
- comfort food is good when used wisely (re: Ale 8 and oatmeal cream pies)
- move back and forth between sports drink and food by the hour

My current thoughts based upon this past workout; I forgot about the concept of moving from gel’s one hour to sports drink the next. I will definately try that option again b/c eating seven egel’s in 4 hours was easy to do, but left me feeling like I was unable to eat more. The other issue I feel I had was using the extra strength (not too much extra) gatorade. I’ll just use the regular strength gatorade.

A major lesson for me on this ride was that the extra spikes in intensity / heart rate changed my ability to digest the calories I was taking in. - (really go read the post by Jeff Shilt, MD)

A couple changes that I have made are changing from oatmeal cream pies to honey buns. The pies seemed too sweat and actually became hard to eat, while the honey buns go down really quick and are packed with calories… (the jumbo’s are over 500kcals and they take about 20 seconds to get down!). The second change is using gel flasks. It seems a whole lot easier to manage than using so many packets.

Fatigue.

So this race simulation ride came at the end of my biggest (duration wise, not counting Brevets) week of training this year. I could definately feel it in my legs and noticed it in my heart rates. The highest my heart rate climbed to was 169bpm on the third lap. This was while I was pushing as hard as I felt possible at a couple points, once during a climb and once at the end trying to fly home and go under 2 hours.

In a normal rested state, my heart rates will easily reach the upper 180’s and stay in the 160’s for several hours. (Running they’ll stay in the 170’s for hours.) An example of this was during our 300km Brevet from Atlanta back in May, when we hit a climb in Alabama my heart rate got up to 186bpm and stayed above 180bpm for a good 20 minutes. All of this shows me that there is probably a level of fatigue setting in. (Other signs show this too.)

So yesterday (7/17/07) and today I’m taking it easy, trying to put down a little of that fatigue and come back to have a big training cycle Wednesday through Sunday. While the extra day (today) of less training was unexpected, I hope the rebound will be quicker and I won’t end up overtrained.