It might be about the bike after all…

I have to admit it, the Dimond bike is a head turner.

The Dimond is ready for its close up

The Dimond is ready for its close up

It looks fast. But the question is, is it fast? When I switched over in the middle of last season from my tried-and-true Specialized Shiv (the original with the nosecone), I took a little bit of a leap of faith that it would be. Sure, there was some wind tunnel data, but this data gets endlessly debated on Internet forums by “experts” of all kinds, so it’s hard to know. Also, it had just been ridden to a convincing victory by pro TJ Tollakson at Ironman Mont Tremblant, but pros are likely to be fast on any bike.

What is important to know is whether I am faster on it than on my old bike. For that, we need data. Luckily, I have lots of data-gathering devices – especially the power meter – and I also like to do the same races either every year or every two years. Call me a creature of habit.

The key in performing an apples-to-apples comparison is to eliminate as many variables as possible. I only had a couple of races on the bike in 2014; the second one was Ironman Arizona. Here’s a comparison between 2014 and 2012:

imaz comparison strava

The overall times aren’t quite right since they’re when I started/stopped the bike computer, but they’re close enough. The heart rate data is almost identical, and the power data is pretty close. The split is a lot slower on the Dimond, though, so at first glance it wouldn’t appear to be a faster bike at all.

However, 2014 was really windy, and 2012 had no wind to speak of, so the conditions weren’t comparable. In 2012 I had the 4th-fastest bike split in the age group, and I did again in 2014, so that might argue that the two performances were equivalent. However, placing is a factor of who shows up, and two trials aren’t enough to claim a trend. So onward we go.

Then comes last weekend’s Ironman 70.3 St. George in southwest Utah, a venue that’s become one of my favorites. I did race here last year on the Shiv, so this race presents an opportunity to generate more comparison data. First, the tale of the tape:

stg comparison ian

A minute faster in the swim and 4 minutes on the bike (we won’t talk about the run). So the Dimond scores on the initial numbers; however, we have to examine two main variables: was this year’s course faster than last year’s, and how did the efforts compare in terms of watts?

The course was slightly different this year; while it eliminated some strange, slow sections on a bike path where two parts of the course crossed one another, it did add a section on a bike path in Snow Canyon, which we then partially descended and had to execute about the tightest 180-degree turn I’ve ever encountered in a triathlon. Then climb the canyon. The total elevation gain recorded by my Garmin, however, was nearly identical at just under 3300 ft (1000m for the rest of the world).

Another way to look at relative difficulty is to look at the pro times. Since many of the same pros raced this year and last, they’re a good benchmark, since as a group they have the most consistent fitness year over year, and they are racing for a living, which means they’re both supremely motivated to push hard and also able to sustain a higher intensity level than age groupers, in part because their race doesn’t last as long. :-) (Joking aside, that’s actually true if you look at the formula for how Training Stress Score is calculated – to achieve the same metabolic cost, measured in TSS points, for a workout, if your duration is less, then your Intensity Factor is higher, actually by its square.) Anyway, if we look at the male pros:

stg pros male

(2014 is on the left and 2015 is on the right.)

What we see is that the same pros year over year were mostly 2 minutes or so slower this year than last year. The male pro race dynamics could have been different, though, so let’s look at the female pros:

stg pros female

Not quite as many repeaters as the males, but of the 6 or so, the gap – other than Heather Wurtele, who was not quite 2 minutes slower – is 3 minutes or more.

That tells me that this was definitely not a faster year, and in fact was probably a bit slower (I’d love to hear from any of the pros about the differences from their perspective between this year and last, especially if I’m missing something key in my analysis).

The other possibility, then, other than the bike being faster is that I worked harder this year, i.e., put out more watts. But that doesn’t appear to be the case:

tp stg 2014

tp stg 2015

Compared to 2014, my faster speed in 2015 was achieved at 6W lower normalized power and 10W lower average power – for .8 mph better average speed. I hadn’t worn a heart-rate monitor in 2014, so I can’t compare the efforts along that dimension.

Finally, if we go back to Strava, we can use the segments to compare each year to see whether I rode the course any differently, i.e., did I push the uphills or downhills more in one year than the other?

strava stg 1

strava stg 4

I’ve just shown the beginning and end pages here (I skipped another couple because I see many eyes glazing over already), but you can see the trend: I did start a little harder this year (2015 is on the right), but after those initial climbs I was faster on pretty much every segment, and at lower wattage. In 2014 I pushed up Snow Canyon a lot harder (I was also probably fitter, having come off of Ironman Los Cabos at the end of March), but even so my splits are very close. I have a few theories:

  1. The Dimond definitely seems faster on the flats and downhills. I saw the same phenomenon on training rides, when I started getting Strava segment PRs on routes I ride pretty often. These always came on flat and downhill sections.
  2. The fact that my uphill splits were so close (and still mostly better) at lower wattage is somewhat baffling. I don’t weigh less than I did last year, so watts/kg doesn’t explain it. The Dimond itself weighs about a pound less than my Shiv, which could be part of it.
  3. Both bikes are equipped with Quarq power meters. They both run the same firmware version, but they are slightly different models, so I suppose there could be a slight difference between the power readings on the two.
  4. I did run a different wheel combination this year – Zipp 808 front / Super 9 disc vs. a pair of Reynolds Aero 72 wheels – which likely gave me some of the better speed on the flats and downhills, though likely cost me a little on the uphills due to weight. Tires were, in both cases, Specialized S-Works Turbo 24s with latex tubes, so no difference there.
  5. Finally – and this could be a big factor – I could be spending a greater percentage of my ride down in the aerobars than I have in the past. This season I have been making a concerted effort to do my hard efforts on the trainer in the aero position, and I’ve also been doing a weekly stretching class (and reinforcing the exercises at home during the week), so I feel as though I maintain the position more easily. I can’t quantify this as a percentage of my race, but it could certainly explain some of the better speed at lower watts.

To be clear, I do believe I have enough data to say conclusively that the Dimond is a faster bike than the Shiv, at least with me on each of them. What is unclear is how much faster. I rode 4 minutes faster on a course that the pros rode 2-3 minutes slower on, and I did that at 6W less normalized power. So that alone would say that it’s way more than 6W faster. However, some of the other variables I listed above potentially contribute to some of that speed gain, so I don’t feel I can say anything more than “it’s at least 6W faster than the Shiv.”

The rest of my season has a lot of repeat races from last year and/or two years ago, so it will offer plenty of additional data points to see whether this trend holds. I’m happy thus far, though, with what I’ve seen from the combination of Dimond and rider. We’ll try and keep improving the rider as the season progresses.

You Won’t Believe What I Did Next…

For a guy who’s been in the business of analyzing human language via computer for almost 30 years, you’d think I’d be happy that the language of the Internet and of social media is becoming more and more predictable. The same conventions everyone uses to be found and to be heard – hashtags, @mentions, clickbait phrases, unimaginative headlines aimed at search engine optimization (SEO) – play right into the hands of those working in the field of natural language processing and text analytics. After all, whether their purpose is social engineering or algorithmic engineering, they’re formulaic and therefore amenable to pattern recognition.

However, I’m married to a journalist, who happens to be one of the wittiest writers I’ve ever known. She’s worked at big-name newspapers – the Washington Post, the Boston Globe and the San Francisco Chronicle, to name the most notable ones – and what I think has kept us together over 30+ years is our similar sense of humor, a lot of which revolves around language (of course, she has many other charms as well :-) ). Non-straightforward, novel use of language is part of what makes for great writing, and for great humor, but it’s exactly these sorts of literary devices – metaphor, puns, intentional malapropisms, etc. – that confound computerized language analysis. We in the business like to call them “corner cases.”

Headline writing, when done well, is one of the supreme literary art forms of the pre-SEO days. Back in the day, when writing for print only, headline writing genius often emerged under very tight print deadlines, with fixed page real estate dictating the constraints of one’s expressive canvas. One of Jeanne’s Boston Globe headlines actually made the Tonight Show, where Jay Leno had a regular bit on funny headlines. Hers was for a movie review about a well-intended-but-poorly-executed period piece about a castrato singer, and her headline was “Beautiful Castrato Movie Missing Something.” I’m afraid the 2015 version would be something like “Singer loses his ‘nads, and you won’t believe what happens next.”

Of course, the best headlines often never made actual print – they remain forever locked in newspaper publishing systems, fueled by late night deadline fatigue, gallows humor, and the almost certainty that upper management would never see them. Case in point: this Washington Post review of “The Hunt for Red October.” Unbeknownst to all but a few, the original, never-published headline took the submarine theme, together with the reviewer’s critique of the film’s ponderous and difficult nature, and wrapped it up neatly in a bow worthy of junior high stardom: “Long, Hard and Full of Seamen.”

I'll take "Anal Bum Cover" for $7000

I’ll take “Anal Bum Cover” for $7000

Come to think of it, that headline would probably get a lot of clickthroughs today.

Age Is Just A Number

Out on a run in Northwest Florida the other day, I passed a house with a bunch of decorations in the front yard, among them this:

No U-Turn Youth

Some of the other decorations, which included black balloons and tombstones, made it clear that someone in the house was turning 40.

40.

The implication, even in jest, is that it’s all downhill from here. I can understand the fear – when I was a teenager, I thought anyone over 20 was old. In my 20s, it was a big deal when friends hit 30. Back then, I couldn’t imagine what it would be like to be 52, the age I am now.

It’s awesome!

First, I’ve maintained myself physically. In fact, I just had my best year in triathlon EVER. Not age adjusted or anything – ever:

  • My three fastest half Ironmans of all time
  • My two fastest Olympic distance tris of all time
  • My second-fastest full Ironman ever and highest age group placing ever (2nd, qualified for Kona – did I mention that? :-) )
  • My first overall win ever in multisport – a sprint duathlon back in March

Fitness aside, I also think I’m a better person. When I was younger I was very impatient in all kinds of ways. Impatient with people with whom I disagreed. Impatient with people I didn’t consider intellectual equals. I lacked empathy at times. I lacked perspective.

Not that I don’t still have a juvenile, sophomoric sense of humor. (My brothers can still send me into fits of uncontrollable laughter with the right look or insider reference.) But now when I’m disappointed or angry with someone – which happens, both in work and in life – instead of letting go of my emotional control, I try to examine where they’re coming from, what’s driving them. I find that taking that perspective often leads to quicker conflict resolution and fewer hurt feelings. Life’s too short to hold grudges.

I also examine failures more objectively. If it’s a sub-par race, I examine what went wrong, whether it was inadequate preparation, equipment issues or poor race execution, and come up with a plan to rectify the issue in my next race. If it’s a setback at work, it’s the same approach.

Physical and mental decline will hit all of us at some point, but I for one am not going to go down without a fight. A large part of it is attitude:

  • Never EVER let age be an excuse. Ask my training partners about my competitiveness. I don’t care if they’re 20+ years younger than I am – when I go hard, I’m going to make it hurt.
  • Learn from the past, but don’t live in it. I never think that my best days are behind me. I’m going to make today the best day of my life, and tomorrow even better. It doesn’t always work out, but I get up each day and try again.
  • Have audacious goals, and work towards them. My goal is to be the first 90 year old to finish an Ironman. Plain and simple. But that goal entails a lot: living that long, and having immense physical vitality that long. Plus a host of other things, some of which are luck of the draw. Someone may beat me to the feat, but in that case I’ll just have to raise the bar. Maybe it’s 95. Maybe 100. :-)

Anyway, enough motivational speeches. But if you’re in Kona in 2052 and see me cross the finish line, buy me a margarita. I’ll likely be sodium depleted.

Oh, and the house with the tombstones and black balloons? They were all gone when I ran by this morning.

I guess the party’s over. Let the downward spiral begin. :-)

IRONMAN-Arizona

Ironman Arizona: Coffee’s for Closers!

This was my fourth Ironman Arizona and – assuming I finished – would be my 15th IM overall.  But it came at the end of a very long season: I had some nice volume coming into the year, thanks to the mild Bay Area winter, but I started a new job (at Saffron) in February and went into Ironman Los Cabos without my usual focus. I had a disappointing race there, “running” 4:51 and deciding then and there to quit chasing Kona for 2014. Instead, I did lower volume but some higher intensity, and raced my ass off at Olympic and 70.3 distances – that training was much more compatible with the new gig and with re-establishing a sense of fun. And I managed to break my Olympic-distance PR twice and do my three-fastest 70.3s ever (StG, Honu, Vineman). For an “old man” of 52, I was pretty happy with that.

But then IMAZ loomed. Even if my shorter races indicated great fitness, my training volume numbers were way lower than I would have liked. I’m talking under 10 hours per week for all but 5 weeks in the past 6 months; biggest week just under 15 hours. By mid September I knew there wasn’t much to be done – you can’t cram a bunch of volume in, but you can do some focused volume, so I did one key 100-mile ride that I probably did 10 times before my breakthrough IMAZ 2012, and it went well enough to convince me I could do this thing. The race is also a qualifier for the 2015 Hawaii Ironman, and I figured, based on past years, that I would need to finish in the top 3 or 4 of my age group to get a Kona slot.

I wasn’t getting a lot of pool time (like 1x per week), but I did a lot of sessions on my Vasa to try to at least build some swim-specific muscular endurance in the upper body. It appeared to work, because when I did make the noon masters swim (I am not a morning person, unlike most triathletes), I was able to swim in my usual lane and sometimes up a lane with no problem. Also did our team’s “hour swim” and got 3800 yards in, drafting about 1000 of those, so I figured I was good for my usual 1:10-1:15 range.

Hydration issues in IM aside, the run has historically been my strength, so my only worry there was proper pacing – oh, and having the old body hold up. A last-minute equipment change was to run in Hoka Cliftons (not brand new – had run in them a number of times) rather than the Newtons I normally wear. The IMAZ run is pretty flat, but the surface is hard, so I figured the extra cushioning would come in handy. To that end, I also decided the night before the race to wear compression socks (really “sleeves,” since they didn’t cover the foot), but the only pair I’d brought was a non-kit-matching green. Oh well – going fast isn’t about fashion. :-)

The final component of my race that I had to get ready was my head. The long season had taken its toll on me – mentally, I was ready for it to be over. Physically, I felt tired, and also got sick for the first time in two years, just prior to Challenge Rancho Cordova, which I was forced to turn into an aquabike because I felt so bad. The Wednesday before IMAZ, the congestion made its return – rut roh! I tried to remain upbeat and positive, and I was determined not to repeat my biggest mistake at Cabo: not having my head in the game.

Much as I tried to be relaxed about it, I did have the goal of getting a Kona slot, so there was the competition to consider. I had peeked at the bib list coming in, and the one name that stood out was Bill MacLeod – I’d met him at Malibu and knew he was out of my league. He also always shows up to races prepared, so that was one slot likely gone. Anything can happen in IM, of course, but he isn’t a guy who “blows up.” Beyond him, I didn’t really know anyone else to be a “heavy hitter,” which didn’t mean that anything was in the bag but simply that I had as good a shot as anyone else at a KQ if I executed well. Or so I told myself.

Anyway, the race:

Swim: I hate this swim. Not because of the water or anything – just way too many people. I’ve tried both sides but had my best luck on the left, so I headed that way again, and it was the right call. Other than some of the paddlers trying to move us right too early (no way I’m moving into that melee, pal!), I was moving along pretty well, with the normal bunching up at the turn buoys. I got right in the scrum there, but people were pretty good in general, and after the second one I moved over to the shore like a guy on Slowtwitch had suggested. Boom! No one other than a couple of other caps – everyone else was following the buoy line. My only regret was not staying right for longer; the buoys kept moving right, and I could have stayed near the shore almost all the way to the Mill Ave Bridge. Anyway, I looked at my watch on exit and saw 1:11, which equals my best swim here, so I was pleased enough. Score one for the Vasa!

Bike: I rode 5:04 here in 2012, but as soon as I hit the road it became apparent from the winds that that was going to be challenging to repeat. I had my wattage plan anyway – basically average between 190 and 195W, which is what I did to get that time before. My first problem was my Garmin 510 bike computer – for some reason the display wasn’t showing power, and the only thing I had changed before race day was to set alarms every 15 minutes to remind me to drink. This clearly wasn’t going to work – if your plan involves sticking to power but you can’t see power numbers, you’ve got a problem – but luckily it’s easy enough to change the data fields on the fly, which I did once things had settled down a little and I wasn’t surrounded by other riders. From there it was just a matter of being patient; I let myself go up to 205-210W uphill and into the wind and occasionally spike above that if I needed to pass someone quickly to avoid drafting, but otherwise I was Steady Eddie. I made sure to drink a lot. The first lap was a 1:42 – already a couple of minutes slower than I’d done in 2012, but it would get worse from there. I think my second loop was 1:45 or 1:46, but I was still mostly passing people. I didn’t see much, if any, drafting where I was. The real key was avoiding collisions with riders I was lapping, some of whom didn’t heed instructions to ride right. I did my best to announce myself as I was passing, but it was hard to hear with the wind out there.

IMAZ bike

IMAZ bike 2

My Garmin crapped out on the power data (and HR) around mile 80, so the last loop I was “riding blind.” This may have been a blessing in disguise, because it forced me to go by feel, knowing that I had a run that I really wanted to nail. Nail in a “don’t cramp up and lose a bunch of time” kind of way. I couldn’t wait to make that final turn at the top of Beeline, and once I did I really relaxed on the downhill and made sure to get a bunch of nutrition in. I was ready for the ride to be done, which was a good indication that my long-distance bike fitness wasn’t as good as it should have been. Still, I executed a decent flying dismount into T2 with a split of 5:19, my second fastest. A far cry from 5:04, but I’ll take it on the day.

For data geeks, luckily I was also running my 910xt, which didn’t crap out, so I got the stats. NP of 188W (5W less than in 2012), TSS of 286, avg HR of 127, VI of 1.03 – not 1.01 like in 2012, but with the winds and all this is pretty even).

Glad to be off the bike!

Glad to be off the bike!

Run: I felt ok running into T2, made a quick pee break (why don’t people push the locks when they’re in the portapotties??), and got out on the run course at 6:39ish into the race. I was pretty sure there would be no sub 10 at that point; my fastest IM run ever is 3:32 (from IMAZ 2008). That didn’t mean I wasn’t going to try, but I’ve gone out at 7:00 pace in the past and that didn’t work out so well. Plus, I didn’t feel particularly punchy in my running, so I figured I’d just settle in. First couple of miles were 7:40ish, then on the return with a tailwind I hit a 7:15 mile 3 and told myself to simmer the f*** down. This would turn out to be a run in which I never felt really good, nor really bad. I was trading places off and on with an Executive Challenge guy I know – he would stop and I would pass him, then when he was running he would blow past me again. The two-loop course was new to me yet had a lot of familiar stretches from the three-loop course, including the climb up East Curry, but for Bay Area types it’s not much of a climb.

High-fiving my good luck charm Alexa

High-fiving my good luck charm Alexa

I was glad I had the Hokas, but after the first 10 miles or so even they didn’t feel that cushioned. I just kept focusing on nutrition and every once in a while on other runners (former world-class marathoner Colleen de Reuck flew past me at mile 16 with some guy in tow, so she was hard to miss). At mile 17, my wife told me that I’d come off the bike in 4th in the AG and might be as high as 2nd now, but that 1st was “out of reach” (that’s putting it mildly). That was the first update I had had all day, and to be frank I was kind of shocked. I thought I had blown it on the bike and was maybe running for top 10. Knowing how unreliable the live tracker can be, I didn’t fully trust the intell, but all the same my focus was now on maintaining – no way I was catching 1st, but if I blew up I could lose 2nd. Or whatever place I was actually in.

My mile splits were consistently in the 8:30 range, and I had had no cramping yet, so once I hit that East Curry hill the second time to get to mile 23, I started my push for the finish. I had no idea where anyone was at that point, and I’d had no updates since mile 17, so my job became simply to make it very hard for any geezer to come by me. Those last 3 miles hurt. A lot. One or two younger dudes went by me in the last mile, but just before the final turn into the chute my friend told me he was pretty sure I was 2nd. I crossed the line in 10:15:50 (3:36 run), my second-fastest IM ever and indeed 2nd in M50-54. Kona, baby!

Glad to be done!

Glad to be done!

With Jeanne, my biggest supporter

With Jeanne, my biggest supporter

To say I’m ecstatic with this result would be an understatement. I was worried I didn’t have enough volume coming in; I knew early on in the bike that my sub 10 goal was likely out the window, yet I got my best Ironman AG and overall (117th) placing ever. And I’m old. :-)

So what did we learn?

Well, sports cliches are used in business for a reason – days like this are a metaphor for life. Here’s what I took away from the day:

  • Have a plan, but be prepared for things not to go to plan. I had time goals for each discipline, but the heavy winds changed things on the bike, so I adapted. I also had to adapt to not having power data throughout the entire ride, and just go by feel.
  • It’s tough for everyone, not just you. When you encounter tough conditions and get into a negative frame of mind, it can turn into a pity party. I tried to turn it around and revel in the conditions by telling myself that others were having it worse, that faster guys were going to overbike (trying to hit a time goal) and blow up on the run – basically, make lemonade out of lemons.
  • Don’t count yourself out, even if you think you know the score. I had no idea what my position in the age group was (and therefore what my chances of a Kona slot were) until mile 17 of the run, and even then I didn’t know for sure. I just kept trying to run my own race, and it worked out.
  • Mental toughness is equally important as physical preparation. I was in better physical shape going into Cabo than I was going into Arizona, but my head was in the game in Arizona – I paced myself well, and executed on nutrition and hydration better than I ever had before.

So my way-better-than-expected day really came down to execution. One of my favorite movie scenes of all time (and I joke about it all the time with the sales guys I work with) is this one from Glengarry Glen Ross. It’s harsh (as is the language), but I sometimes use it to toughen up and remind myself – especially in the last part of the marathon, where everything hurts – that I want to finish the race with no regrets. No regrets that I didn’t push when I could have, that I let up and someone else came by me. In other words, I needed to seal the deal, run “like I stole it” – in short, close.

results

Second place? I think I earned more than a set of steak knives.

Who's going to Kona? *These* four guys!

Who’s going to Kona? *These* four guys!

Thanks to my great support crew of Jeanne, Greg and Alexa, and to my awesome Team Sheeper teammates and training partners, who are not only great friends but who also push me every day to be better.

Coach, heed thyself!

Giving advice is easy; taking the advice you so freely give is a lot more difficult when it applies to yourself.

My lead-up to Challenge Rancho Cordova was a week of a nasty cold – my first in at least two years – along with two airplane trips across the country, and not the best diet or sleep. Wednesday through Friday were the “height of misery” days, which made me dubious that I would even drive up to Sacramento on Saturday to pick up my race packet.

But as these things go, I woke up Saturday morning feeling human enough to go on an easy spin with the team and test out my race setup on the bike. So the drive up to Rancho Cordova (a suburb of Sacramento that looks like a technology park with housing developments and color-coordinated strip malls thrown in) was on; the plan was to see how I felt on Sunday morning before deciding to dive in and actually start the race. IF I did end up racing, I told myself, I would do it at Ironman race pace instead of the higher intensity I would normally do in a half Ironman. The objective of even doing this race, I reminded myself, was to mimic Ironman Arizona conditions and race setup.

Sunday morning had me feeling decent enough to start the race, even though I still sounded terrible. My coach Tim was there to spectate and questioned why I was even doing this. “I feel better than I sound” was the only thing I could come up with. Conditions were really nice, actually: calm 68F water, perfect for a fast wetsuit-aided swim, and though the day would get very warm indeed by the run, the first couple of hours of the bike were doing to feature ideal air temps.

A relatively small field combined with age group waves made for a very civilized start, and after the first couple of hundred meters of adrenaline-fueled strong pace, I settled into a moderate, Ironman-type effort. Swimming when your nasal passages are congested is quite an interesting experience – the activity itself already produces enough hypoxia that you don’t really want any additional difficulty getting oxygen in. I didn’t feel exactly panicked at any point, but I did stop briefly a couple of times to clear my nose out a little (no further detail necessary). My left calf also cramped a few times, which I guessed was due to the dehydrating effect of all the decongestant I’d been taking. Fortunately, I swam a pretty straight line, so I exited the water with an average swim time for me that turned out to be 34:02 (I wasn’t clocking it on my watch).

I spent too much time in T1 fumbling to get into my tight long-sleeve top (sun protection), so that was a good lesson and “opportunity for improvement” for Arizona. Once on the bike, I felt pretty good other than fatigued arms and shoulders (note to self: more swim time!). The first half of the ride was mostly rolling and a net uphill, with a couple of climbs that forced me into the small chainring. I was averaging around 215 watts for that part, which is slightly above my Ironman target effort. I did allow myself to spike well above that for short sections on the steeper climbs but otherwise held myself in check. The first aid station was, uh, interesting – for some inexplicable reason they had set it up near the bottom of a long downhill, so the chances of successful bottle handoff when riders are going 30 mph was practically nil. Oh well – I still had plenty of fluids at that point.

After 25 miles, the climbing was pretty much over, and the course had a net descent of about 600 ft over the remaining 31 miles, which meant fast riding for less wattage – I averaged over 23 mph on this part with only 186W of average power. That allowed me to focus on hydration and electrolytes, and I came to the end of the bike feeling reasonably good, although a little hungry (the aid stations only had enough volunteers to hand out bottles, so my only calories came from the one gel I had in on me). My bike split was 2:35, which I think equals my best half-Ironman split ever, even though my average power was Ironman effort. All that says is that the course was fast. :-)

I had debated about ending my race as soon as I got to T2, but I decided to see how I felt. Since the course was two 6.5-mile loops, I told myself I could always stop after the first loop. Here’s where the voice of the coach and the voice of the athlete were at odds – if it were one of the athletes whom I advise, I would have told them in no uncertain terms to stop after the bike. The competitor in me, though, doesn’t like DNFs. The competitor won round one.

rancho cordova bike

Once out on the running course, I tried to run relaxed. The legs felt good and wanted me to do some quick turnover, so I started out at around 7:00 pace. Pretty soon, though, I felt as though I should back off – I was still pretty congested and coughing a bit. Through 3 miles I was averaging 7:15s, but I also realized that I was violating my rule about not digging a hole for myself. Right then and there I decided I was going to be done after the first lap, and at that point I started running an easy 8:15ish pace and walking the aid stations.

What did we learn? A few things:

  • Work out how to more quickly put on that long sleeve top after the swim.
  • Take more calories than one gel per 2.5 hours on the bike.
  • Slightly alter the angles on my saddle and aerobar pads/extensions for more comfort and weight balance.
  • Learn to listen to the coach in me sometimes and not the athlete!

As somewhat of a sliver lining to the DNF cloud, the organizers let me switch to the Aquabike division after the fact, which I apparently “won” (they still gave the official awards to those originally entered in the division, which is fair enough). I love customer-friendly flexibility! Thanks to Challenge for creating the event, and special thanks to USA Productions and SVE Timing, who actually made the event happen.

I have some work to do before Ironman Arizona. The first “to do” is to get healthy! The second is to listen more to my inner coach. :-)

The longest season ever isn’t over yet!

Every season I like to experiment with something – sometimes to see whether little changes lead to improvement, status quo, or degradation, and sometimes just to challenge myself in different ways than I have in the past. After a 2013 in which I – thanks to taking a sabbatical from full-time work – had higher training volume than ever, 2014 has seen my return to the working world and a corresponding decrease in training volume.

However, my results – other than a poor performance at Ironman Los Cabos – have been better than ever:

  • My three fastest 70.3 races of all time: St. George in 4:58, Honu in 5:03, and Vineman in 4:47, all thanks to better bike-run combos (in other words, with my usual mediocre swim times)
  • My two fastest Olympic-distance races of all time: Folsom in 2:14 and Age Group Nationals in 2:12, again with the usual swim times.

Oh, and I turned 52 this year and have been doing triathlons since 1983. So what gives?

No, I didn’t start taking PEDs. :-)

Everyone’s an experiment of one, and as such I don’t have a control group, but here’s what I think worked for me:

  • I had a great volume base from last year, so I was able to “sharpen” off of that base by increasing intensity as I decreased volume.
  • No matter what was going on with work or other aspects of my life, I made sure to get the key sessions in: “big gears” on the bike, threshold on the bike, long ride, extended fast run (marathon race pace or faster for 4+ miles), long run, and occasional long swims. Most of these were weekly; others bi-weekly.
  • I squeezed in frequent-but-short swim and bike sessions whenever I could. Sometimes this meant catching 20 or 30 minutes of a 60-minute masters swim session; other times it meant getting on the bike trainer at 10 pm after a business dinner with a couple of glasses of wine (these weren’t quality sessions but weren’t super easy, either).
  • I went to my ART “miracle worker” almost weekly and was pretty good about doing the exercises he gave me. And I also regularly use “the poofy pants” – my NormaTec graduated compression boots (which I paid for, btw, lest the reader think I’m shilling for them) – to help my legs recover between workouts.
  • I raced often – once or twice per month – which not only got me fitter but also took the pressure off of any particular race. This is much easier to do with shorter races than it is with Ironman, which is more “all or nothing” since that distance necessitates longer taper and recovery times.
  • I traded off run volume in favor of bike volume. Perhaps I get away with this because I have a running background and am of a lighter build, but I also find as an older athlete that quality runs take longer to recover from than quality bike sessions do.

Also, it has to be said that the biggest factor of all in my ability to continue to set PRs is that my PRs weren’t that good to begin with. So my best asset is my longevity – I’m still competing, and I’ve just slowed down less than others. And avoided catastrophic injury.

Not everything has gone perfectly:

  • I neglected my swim strength for a while during a phase in which I was using my precious little swim volume to focus on technique, and it showed in my swim times. I’ve since added back a lot of basic upper-body strengthening, including regular sessions (as long as 90 minutes) on the Vasa Ergometer.
  • I “trained through” a couple of races, including doing hard rides the day or two before the actual races, which ended up costing me a couple of minutes and podium places in those events. I adjusted by adding in three-day “mini-tapers” to allow myself to be fresh, even if not really tapered in the classical sense.
  • I occasionally dug myself into a “training hole” with workouts that had a combination of high volume and intensity. After the fact, of course, I could see this numerically in TrainingPeaks through TSS numbers – when you do a session whose TSS is 50% or more of your average weekly volume, you’re gonna feel it! These big sessions are necessary, of course, but the lesson I took for my current year of lower overall volume is that I need to rest before these big sessions and make sure I recover for a bit longer after them.

I’ve got two races left in the season: Challenge Rancho Cordova (a half Ironman) this weekend, and Ironman Arizona in mid November, in which the goal is to re-create the magical race I had there in 2012, where I managed to get 3rd in M50-54 and a Kona slot. It’s going to require solid race execution and a good deal of luck, but all I can do is focus on the former, since that’s under my control, and hope for the latter.

A former boss of mine once said, “It’s better to be lucky than good.” There’s something to that…

Age Group Nationals: small fish in a big pond

My binge-racing campaign of 2014 continued with a trip to Milwaukee for the USA Triathlon Age Group National Championship in the Olympic distance. It’s relatively straightforward to qualify for this event – finish in the top 10% of your age group in a sanctioned race – but the event itself is anything but. Like Kona, it’s similar to my freshman year at Rice, where I had to adapt to being a small fish in a big pond – going from being at the top of my class in high school to being one of many who had been at the top of their classes in high school.

But blows to one’s ego aside, it’s good to face tougher competition – it tells you where you really are. So I stood ready to take my licks, especially at a distance that doesn’t really play to my strengths. The problem for me at the Olympic distance is the swim: it’s barely shorter than the swim at a half Ironman, but both the bike and run are less than half the distance, so I don’t have as much ground to make up time on the really fast swimmers – I run out of “real estate.”

On the other hand, the Olympic distance is fun! You don’t have to worry about nutrition or even pacing that much – you just go hard for 2ish hours. The key for long course athletes is to be able to go into that higher-intensity zone; to that end, a group from my team had been organizing a weekly tempo run to force us to push into that uncomfortable zone for a sustained period.

Milwaukee turned out its best for the weekend: spectacular weather and a nice race venue, with the bike course completely closed to cars. Registration and bike checkin were a breeze.

All's quiet at the finish line the day before the race

All’s quiet at the finish line the day before the race

 

The race steed is checked in and ready to go!

The race steed is checked in and ready to go!

The race was split into age group waves, with a healthy gap of 10 minutes or so between the waves – this meant you wouldn’t be catching a ton of people from earlier waves, and also that no one would be catching you. Mine left at 8:04 a.m., which was enough time to rid myself of any fog from the previous evening’s wine bar, and soon all 200ish of us were off. It was pretty crowded, as we all had to funnel through a narrow gap after a couple hundred meters.

I almost always feel tentative in the first part of the swim when it’s crowded, but as things thin out I’m able to focus on stroke mechanics, so in the second half of the swim I started reeling a few guys in (as well as women from a previous wave). I wasn’t clocking my swim, so as I hit the exit ramp I didn’t know what the time was – the ramp was steep and slippery, so all I worried about was getting up without taking a spill. It was a fairly long run to T1, whereupon I had trouble finding my bike – I was in the right row but passed it before realizing my mistake. That cost me about 30 seconds, which is nothing in an Ironman but costly at this distance.

Out on the bike course, and it was hammer time. Well, initially it was time to pass a bunch of slower riders from prior waves and also faster swimmers from mine without drafting or blocking. The speeds were amazing on this flat course – I was over 25 mph on a lot of sections. The first slow section was a bridge, and that’s where I started a little age group battle with a few guys who were riding in kind of a pack. I passed them on the uphill, then they re-passed me on a sketchy section where they had us zigzag to the left for a while. Per the rules, I had to drop back beyond the draft zone, which I did, but then I just kept the gap for a while and watched them continue to ride as a pack. This was starting to piss me off, but I was also reeling them in by just holding my power numbers, so I amped it up in order to pass all of them quickly – went from about 240W to 350W or so for that period – and that pass held for the rest of the bike leg.

Once more up the bridge on the way back, and T2 was just around the corner. I did a nice dismount and hit the line in just over 1:02, which is my fastest 40K split in a triathlon by about 2 minutes. No time to celebrate, though – there was a run to do!

My T2 was decent – I opted not to put on socks to save time – and I was off and running, hunting down every 50-54 calf I could find. I looked at my watch a half mile in and was running about 6:15 pace, and I could hear footsteps and breathing behind me. The guy came up next to me and asked what the race time was and what pace I was targeting. I could see that we were 1:34 into the race at that point, which meant around a 2:12 if we could run a 40-minute 10K. The guy acknowledged that and moved ahead slightly, going a pace I wasn’t comfortable in challenging at that point.

I noticed, though, after mile 3 that the guy was coming back to me, and somewhere around 3.5 miles I pulled up next to him. He seemed a little surprised. I gasped out a laugh and said, “yeah, I’ve been tailing you.” Then we ran together and were flying past women and 60+ guys from earlier waves, and only occasionally passing a fellow M50-54 guy. I had no idea where I was in the age group, so I told myself just to keep redlining it. The field was getting pretty thin as we approached mile 5, and by this time I was leading the other guy and looked back to make sure I wasn’t pulling anyone else along.

At mile 5 I decided it was “go time.” Just go hard – if the guy comes by you, so be it, I told myself. The discomfort level was high, but I could see some more guys in my age group ahead, and I reeled each of them in. We were getting close the end, and with maybe 200m to go, I saw one more guy in my age group and surged hard to pass him. He tried to go with me for a moment, but I was going a lot faster, and I hit the line in 2:12:57 with a 40:05 10K split. A PR for the Olympic distance by almost 2 minutes – YES!

My body’s initial reaction was to almost heave in the finisher’s chute, but that urge quickly subsided, and I realized I felt fine. I headed over to the VIP tent (for some reason unknown to me, I had been given access to the whole VIP experience, which was awesome and completely unexpected) to refuel and sit in some NormaTec compression boots.

My finish time would win or at least get top 3 in a lot of local triathlons, but in the national champs it was good for 32nd out of 192 finishers in M50-54. The top 25 got Team USA slots to compete in the World Championship in Chicago next year, and I was about 2 minutes shy of the mark there thanks to my swim:

AGNats results

I’m happy with the result; I raced as hard as I could and as well as my fitness allowed. My rookie mistake in T1 wouldn’t have changed much – it might have cost me 4 or 5 places but not a Team USA slot. And I know what I need to work on if I want to be competitive at the shorter distances (hint: it involves water).

And it was a great weekend in Milwaukee hanging out with friends and teammates, eating German food and frequenting the Indulge Wine Bar. The championship is returning there in 2015, so until next year, I hope!