top of page

Race Review

A large aspect of doing well at long distance triathlon is knowing how to aproachp and pace the race.  Read below to see how an athlete's file is reviewed after a race.

Corey Deveaux’s (Ironman Lake Placid Winner) Bike File Analysis

 

Last September I started working with Corey Deveaux, and two weeks ago he won both the 30-34AG and the overall at Ironman Lake Placid.  His previous best finishes in IM races had been 4th AG and 25th OA (not counting pros). I thought some of you may be interested in seeing his bike file, how we went about planning the ride, and how he executed it to set himself up for a good run and the overall win.

 

The Data

Time- 5:14:xx

Normalized Power – 239

Average Power – 229

TSS – 301

Intensity Factor - .76 (percent of FTP he averaged)

Marathon Time off the bike – 3:09:xx

 

In order for Corey to have his best ride and leave enough for the run, we had to make sure he didn’t over bike like so many athletes.  Just go to the IMLP results and see how many people rode under 6hrs and ran close to 5hrs.  Leading into the race we talked about the importance of not getting involved in group dynamics or worrying about his position at any point during the bike.  I should stress that Corey is a highly intelligent athlete, with great pacing skills, and only needed slight tweaking in his approach to Placid from what he’d done in the past to reap big results.

 

Coming out of the water, Corey’s HR was high, but came down as he settled into his power.  We followed what I call a “Double Cap” during the ride.  For no longer than 10mins was his power to be above 260~ or his HR above 145~.  If either was too high, he had to back off.  This is a great way of taking into account the differing conditions of the day, and as it turned out, Placid was unusually hot this year.  The best way to combat the heat is to be realistic and back off a little, had Corey become dehydrated his HR would’ve gone up, and this would’ve be a cue to back off the power and slow down, knowing that others would have to do the same or pay a price later.  Racing with power is great, but it’s only part of the total picture.

 

About 45mins in, Corey slowly rode up to a group of athletes.  Rather than burning matches to pass them, he settled into a slightly lower power and rode behind.  As we predicted, once the group hit the climb, they motored away.  Corey produced exactly 260watts for 10mins (our predetermined cap) and then backed off as the group continued to disappear up the road.  The athletes he had slowly caught on the flat were now out of sight ahead of him.  Undaunted, Corey kept his effort steady, and didn’t see them again for several hours.  During the 2nd and final loop, on the same climb that those athletes had ridden away from him on earlier, Corey caught and passed the lot of them. 

 

Going in, we had determined that Corey should ride about a 240 watt average on the parts of the course where he it mattered.  I can’t stress enough that a course like Placid needs to be approached differently than a course like Florida.  Corey and I discussed the benefits and drawbacks of “flattening out a course” (holding a perfectly steady power despite terrain changes).  We went into the race with a set plan of coasting once his speed increased above the low 30s mph.  The zeroes racked up while coasting would greatly decrease his average power.  To combat the mental stress of seeing an average power lower than what he would like, and to ensure steadier pacing on the flats/uphills, Corey lapped his Garmin after every decent.  I’ve seen a lot of files where AGs average their target wattage on hilly courses, but have blown their legs because they ride too hard in places to try and make up for the coasting or spin a cadence of 105 going 36mph down hills to hold power when they really should’ve just coasted

.

When Corey was pedaling, he was averaging 240 watts, but because of the downhill coasting, his overall NP was 239 and his average power only 229.  However, this enabled him to ride his fastest ride with the least amount of energy expenditure.

 

The way I came up with Corey’s target watts was developed around TSS.  TSS stands for training stress score, and although I find it highly useless for most workouts, in a 5hr time trial, it’s pretty important.   It’s a calculation of Normalized power multiplied by time, the higher the score, the harder the ride was. 

Most IM athletes should have a TSS below 300 for the bike portion, but Corey had run 3:15 off the bike before, and his workouts in the buildup suggested to me that he could run well off of a higher score.  Since TSS is calculated from time and normalized power, the longer the course takes to ride, the lower the normalized power needs to be. 

Before we started our final build with a lot of IM paced intervals, I started calculating what average watts would equal what average speed at IMLP for Corey.  This would give me his predicted bike finish time and allow me get a TSS score for the ride.  Using strava, past results, and normal weather conditions, I tried to find the right average power to create a TSS of 300.  Following the laid out plan of 240~ watts on the flats and uphills, I thought it would take Corey between 5:00 and 5:10 to complete the bike course, which would give him a TSS of very close to 300.  As it turned out, it took Corey 5:14:xx to ride the course, resulting in a TSS of 301 (pretty damn close to our goal).   This is important because if Corey had been racing IM AZ or Florida, his target power would have been higher.  An NP of 240 at IM AZ might get Corey off the bike in 4:50~, thus his TSS would’ve been much lower than 300.  Given that, Corey’s plan for a race like IM AZ might be to target a power closer to 250, getting him off course in 4:40 but raising the TSS to a target of 300.

 

 

A lot goes into proper pacing plan, especially on North American courses like Placid, Canada, Tahoe, and Penticton that have sustained climbs.  It can be greatly simplified though by following a few rules. 

1. Don’t ever go over 80% of FTP/LT for very fast athletes, but for the majority of AG athletes, don’t go over 70% and aim for an average of 65%. 

2.  Spend training time at that specific power and HR, the lower the percentage of FTP/LT you are targeting, the more time you should spend there on a weekly basis. 

3.  Don’t trust anyone on course, do your own thing and let everyone who’s going faster than you in the first 8hrs of the race go.

 

 

Lastly, this biggest takeaway from this should be that Corey had the fitness to go hammer a race best bike split, but it would have left him struggling on the run.  Instead he rode as fast as he could without going over the watts we knew he could handle and was able to catch everyone during the marathon.  There’s no such thing as a good IM bike, and a bad run, only poor pacing.

bottom of page