The European Ironman season is at its peak, Sunday’s are spent on my laptop tracking triathletes. Having athletes in Ironman Austria and Challenge Roth has ensured a busy fortnight; when the race is over the analysis begins. Debriefings are a pleasure if the day went to plan, but when goals were missed it is a challenging and much more important process. I push my athletes for details, data, any information that will help me understand what happened. Answers aren’t always easy.
I had three athletes at Austria looking to break through the ten hour Ironman barrier. They regularly trained together; they were fit, hard working and good swimmers. The final month before tapering had inconsistencies, work and light bouts of illness interrupting training, but feedback said ten hours was a reasonable goal. On the day two comfortable beat their targets, the third suffered and fell short of our intentions. What led one to disappointment where his training partners succeeded?
All three started the marathon with the potential to go under ten hours, but one was unable to race as he trained. Their performance was a product of the proceeding six hours, events on the bike had determined their ability to run. The bike was the obvious area to focus on.
The Athlete Data
When it comes to analysing results the more data to consider the better; I want to relate details of performance to perceptions of effort. Many of my athletes train and race with power meters, the three in Austria were no exception. Once I received their reports and power data I set about analysing the race.
|Athlete A||Athlete B||Athlete C||Russ (IMNZ 2010)|
Despite the range of results their power data appeared similar, all three contained elements that might indicate pacing errors. Many factors play into Ironman performance so whilst I wasn’t surprised by similarities, I questioned why one athlete had struggled more.
- Power falls over the course of the race from an initial level trending above 75% FTP to below 70% of FTP. Their recommended power cap would have been at the 75% FTP mark.
- There are numerous spikes in power throughout the race, particularly in the first lap; these often cross FTP for short durations.
- Initial heart rates are high, expected after the swim and transition, but they remain high for an extended period. Athlete A had the most success settling his heart rate (and similarly controlling early power)
I plotted my data from Ironman New Zealand 2010 for comparison. A good race though I felt I may have pushed the bike too hard, something reflected by the high percentage of FTP I held. However the overall trend was within my target power range and rose while heart rate remained stable. I ran reasonably strongly and finished well off the back of this ride. Not textbook racing, but the result had been good.
My overall impression was all three went out too hard and surged a little too much, with notable consequences in one case. Side by side it was difficult to pick which performance had resulted in the harder day; I didn’t have a solid grasp on what happened. I decided to consider the distribution of power in proportion to FTP – how much time had been spent working too hard?
How hard I worked on the bike in New Zealand stands out; I believe the FTP values are correct, increasing mine would not overly impact the chart. But the main point was to consider my three athletes.
- Athlete A – was evenly distributed around a central 75% peak, but power tails off slowly as he crosses FTP. There is definitely a benefit in controlling surges more.
- Athlete B – demonstrated a faster tail off in effort and less work above FTP; he also spent more time coasting. His distribution of power is quite broad and he could gain from working more consistently in that central band
- Athlete C – spent a lot of time at lower percentages of his FTP (below 70%), but also worked a lot above FTP. His histogram is very broadly distributed and he needs to control his surges early in the race to avoid fading.
Although I’ve concentrated on power and heart rate I am well aware many other factors come into play. Performance in the water has implications for the rest of the race, but with all three being strong swimmers I felt its affect would be minimal. I have a stronger suspicion that nutrition played a heavy role, the two who broke ten hours are clearest on how much and how often they consumed calories. Greater awareness of fuelling potentially indicating greater overall management of race performance.
Pacing is clearly a challenge for relatively inexperienced long course athletes, especially those with ambitious goals. Mistakes are easy even with power and the results play out over the entire race. A conservative approach can insure a comfortable finish, but may not deliver the desired performance; on the other hand greater aggression is risky. Practice allows an appreciation of the feel of Ironman pacing – how easily it starts and how hard it finishes. It takes time to develop a finer sense of where the line is between optimal pacing and meltdown.
Lessons for Ironman Pacing
Studying this data closely has given me a lot to consider regarding race pacing. My guidelines to athletes need to be clearer and further emphasise the importance of nutrition and pacing. The rules aren’t strict and there’s room to support and athlete’s strengths; testing individualised strategies for more advanced triathletes would be the optimal approach.
- The start of the bike should feel easy. Heart rate may be high, but not power and effort.
- The elevated heart rate should be lowered as soon as possible, stabilising at a level comfortably below threshold. Heart rate and feel should not be ignored even when using power.
- Nutrition is vital! Know what you’re consuming; you should be able to accurately recount it after the race.
- It is possible to push the bike harder than a 75% effort, but it is dependent on training and fitness in both bike and run. Test this in training.
- Spikes in power are never a good idea and minimising time over 90-95% of FTP should be a basic aim.
- Power distribution should focus on a narrow band of sustainable intensity.
- A proportion of long rides should attempt to simulate racing to develop a pacing strategy.
On the day Athlete B was first to finish, pairing a fast bike split with a superb run. Athlete A followed, demonstrating a consistent performance. After fading on the bike Athlete C suffered through the run; he pushed on and made it across the line, all be it later than hoped. All three can learn from the experience and build on it in future races.
From nutrition to pacing - a collection of CoachCox blog posts focused specifically on Ironman training and racing.