In 2011, I raced three Ironmans in nine weeks. It was my first year of iron-distance racing and it was, in retrospect, the most formative season of my career.
Ironman Switzerland: 11:02. Ironman Vineman: 10:18. Henley Iron Distance: 10:28.
The 44-minute improvement from race one to race two in just 20 days wasn't the result of fitness gains. You don't build meaningful fitness in 20 days. It was the result of lessons learned and immediately applied. That's what tight race cadence does. It compresses the feedback loop.
Race One: Ironman Switzerland (July 10, 11:02)
My first Ironman. 2,200 athletes launched into Lake Zurich at 7am. I'd positioned myself near the left edge hoping for a clear path, but 250 people appeared on my left out of nowhere. Instead of being on the edge I was in the middle of a churning blue washing machine.
The swim was stop-and-start for the first kilometer. My goggles kept sliding up my face. By the time I found my rhythm, we had to swim under a bridge, run up a ramp over an island, and get back in the water.
On the bike, I looked down at my Garmin in the first few minutes: 300 watts. Way over plan. The adrenaline of a first Ironman had me riding at threshold effort when I needed to be at endurance effort. I forced myself back to 200 watts.
The run started well at 5:00 per kilometer. Then at 13km, the sunshine vanished. Bucketing rain. Howling wind. Massive puddles. I slowed down and started getting cold. I walked through every third water station, then started stretching the definition of where a water station ended.
At 32km the rain stopped and the sun came out. I found another gear and ran the last 10km without walking. Finished in 11:02.
Lessons identified:
Do more anaerobic swim training to handle aggressive race starts. Don't look at the Garmin for power in the first 10 minutes, just ride by feel until the adrenaline settles. Practice running through water stations instead of walking. Bring spare goggles.
Race Two: Ironman Vineman (July 30, 10:18)
Twenty days later. Same body. The only physical difference was that I'd recovered from Switzerland and done a few easy training days. The mental difference was enormous.
I applied every lesson from Switzerland. I swam more aggressively at the start and found clear water faster. I rode by feel for the first 20 minutes before looking at power data. I ran through every water station.
I also made one major nutrition change. At Switzerland, I'd bonked on the run because my bike nutrition was too dependent on gels. At Vineman, I used a maltodextrin-to-fructose 2:1 ratio in my bottles, supplemented with real food. The result was dramatically better energy on the run.
The finishing time was 10:18. A 44-minute PR in 20 days. I finished 17th overall out of 821 athletes. It was the first race where I realized I might actually be competitive at this distance, not just a participant.
Lessons identified:
The 2:1 maltodextrin-fructose ratio works. Real food on the bike is better than gels alone. Starting the run at a controlled pace (even when feeling great) pays off in the second half.
Race Three: Henley Iron Distance (September 4, 10:28)
Five weeks after Vineman. This was a UK iron-distance race, not an official Ironman-branded event. The course was flat but exposed to wind, and the weather was typical British September: cold.
I got a flat tire on the bike and lost about 8 minutes changing it. The cold was a factor on both the bike and run. I was shivering through the last two hours of the bike, which burned extra calories just staying warm.
On the run, fatigue from three iron-distance races in two months caught up with me. I fell asleep briefly while running. Not nodding off. Actually asleep, mid-stride, for a few seconds at a time. My crew had to keep talking to me to keep me awake.
Despite the flat, the cold, and the micro-sleeps, I finished in 10:28, ten minutes slower than Vineman but still over 30 minutes faster than Switzerland.
Lessons identified:
Practice changing flats until it's automatic, not just something you can do. Carry arm warmers and a vest even when the forecast says mild. Three iron-distance races in nine weeks is too many for my body at this stage. The micro-sleeps are a sign of deep accumulated fatigue.
The 41-Month Resolution Timeline
Here's the part that surprised me when I looked back at this season years later. The lessons I identified at Ironman Switzerland in July 2011 weren't fully resolved until Ironman Arizona in November 2014. Forty-one months.
"Do more anaerobic swim training to handle aggressive race starts." I identified this lesson at Switzerland. I started incorporating sprint sets into my swim training. My swim improved gradually over the next three years. But it wasn't until IMAZ 2014 that I finally swam sub-60 in an Ironman. That's 41 months from lesson identified to lesson resolved.
"Don't bonk on the run." Identified at Switzerland, partially addressed at Vineman with the 2:1 ratio, but not fully resolved until I overhauled my entire race-day nutrition protocol through metabolic testing and the rice-cake approach I used at Kona 2013. Twenty-seven months from identification to resolution.
"Practice race-pace running off the bike." Identified at Switzerland when my legs felt like jelly starting the run. I started doing brick runs after every bike session. The jelly legs improved steadily, but it took until Los Cabos 2013 before I consistently executed a strong IM run off the bike. Twenty months.
Lessons don't resolve in one cycle. They travel from race to race over months and years. The feedback loop isn't "identify lesson, fix it, next race is better." The feedback loop is "identify lesson, start working on it, partially improve, identify refinement, work on refinement, eventually resolve it 12-36 months later."
Why Tight Race Cadence Accelerates Learning
The reason I improved 44 minutes in 20 days between Switzerland and Vineman wasn't fitness. It was the compression of the lesson-feedback loop. I identified a dozen things at Switzerland and immediately tested the fixes at Vineman.
If I'd waited until the following year to race my second Ironman (which is what most people do), those lessons would have sat in a notebook for 12 months. By the time I raced again, I'd have forgotten half of them, and the others would feel abstract instead of visceral.
Racing three times in nine weeks forced me to test my fixes immediately, while the lessons were still fresh and emotionally charged. The nutrition change that produced a 44-minute PR at Vineman? I made it because the bonk at Switzerland was still vivid in my memory. If I'd waited a year, I might have tried some generic nutrition tweak instead of the specific fix the data demanded.
This doesn't mean everyone should race three Ironmans in nine weeks. My third race showed the cost of that approach: accumulated fatigue, micro-sleeps, diminishing returns. For most athletes, two iron-distance races per year with a tight feedback loop between them is plenty.
The principle is: race often enough that lessons from one race can be tested at the next one while they're still fresh. For some athletes that's two Ironmans per year. For others it's quarterly half-Ironmans. The cadence matters less than the feedback loop.
The Framework Lesson
The 2011 season taught me that racing is a learning system, not a performance system. Each race produces lessons. The lessons compound over months and years. The races where you PR are the ones where enough lessons have resolved simultaneously.
My first Ironman was 11:02. Seven years later I ran 8:59. That's a 2-hour improvement, which sounds like a fitness story. It's actually a lessons story. Hundreds of lessons identified across dozens of races, each one traveling forward until it was resolved, each resolution making the next race slightly better.
The first Ironman produced the most lessons per dollar of any race I've ever done. Not because it went well. Because it went imperfectly, and I was racing again 20 days later with a chance to test the fixes.
That's the value of tight race cadence. Not fitness. Feedback.
Want to work with me? I coach athletes from first-time Ironman to Ultraman.