Triathlon Roadmaps

It's a Tuesday night and I am sitting here in a hotel room in Boston, MA, half listening to Man vs Food, eating a salad and longing for my running gear. Boston is such an awesome place to run. Little more than three blocks away from my hotel is a wonderful trail that runs along the river. Lots of runners, walkers and cyclists weave their way around each other on the tiny paved path in a dance of the fitness determined. Tonight, I wish I could count myself among them. 

SIGH.

I am here for the bi-annual Sales Meeting that my company has every year. Today I had to present my product and product updates for all the sales folks. It was nerve-wracking but fine. I don't like public speaking but it's a necessary evil in my job. Typically, all of the presenting participants are invited to dinner to mingle and press the flesh of the revenue generators they hardly ever get to see. Let's face it, they have better things to do than hang out with a bunch of product folks. Because of this, I decided not to pack running clothes or shoes because I figured (as has been the case in the past) that I'd go straight from the meeting to dinner. But this time, that was not the case. I ended up dateless for dinner with nothing but time on my hands.

UGH! I could have gotten a nice, long RUN in. 

Oh well, I guess there are just some things you can't account for. Not being "required" at dinner is one of them. I have to admit, I'm a little disappointed. I like our sales folks. They are fun, positive and vibrant. They keep the faith and add cheer to a company that sometimes has trouble seeing the opportunities for the risks. I love them for that. They believe!

So my thoughts turn from technical product roadmaps to the triathlon off season, my lackadaisical training regime as of late (sorry Coach Liz) and what the next season will hold. I have pondered another 70.3 race and when it's all said and done, I don't wanna. AND, I feel GUILTY about that. I did not have what I would call at GREAT race this year. I trained, stressed and really put the time in only to have it not work out on race day. STILL, I feel some sort of odd obligation. So as I sit here sort of pouting and pondering next year's race calendar, I realize that putting together next year's roster of races is not unlike certain aspects of product management. 

As a product manager, you consider your buyer and/or user (me), what characteristics, abilities and limitations she has and build a product that meets her needs or addresses her pain points. As the "user" I've had some good training experiences and some not so good ones this season. I have sensitive feet that need constant monitoring due to past injury and a longing to get more than two rest weekends of my summer back from relentless triathlon training. I love to train and combine my vacations with training and/or exercise (there is a difference). If I had a wish list for swimming, I'd swim in the sea every. SINGLE. day. Rivers freak me out and there are always those damn jellies! I am very busy with the day job and really need to race in events that "sharpen the spear" instead of build toward something big. 

When I consider myself as the "user" of my race season, the complexion changes. I become less emotional and more logical about what's best for my body, mind, spirit and life. 

I ponder the requirements list for a good race calendar:

• Not so short that's it's boring (sprint) but not so long that I am panic stricken if I miss a long brick (70.3 or over)
• Breaks the monotony
• Fewer jellyfish stings
• Allows for more pure run races
• Keeps my weekend training down to less than three hours

If I were to try to design a schedule for the me tri user based on these requirements I would choose Olympic distance tris and/or duathlons. And you know what else? I would NOT feel guilty. I would feel like I'd MET the requirements and answered the pain points. 

So as I sit here and type instead of run, maybe the best way to think about the new season and assuage my guilt is to see it through the lens of a product manager. Internalize what the requirements are instead of what I feel on emotional level is "not enough". I can then choose races and set goals around the time for those races that make me feel proud for having made the effort. 

The product approach, who would have thought?

Running Through

Yesterday was long run day. Typically on long run day, I anticipate mileage north of 10 that is slow and not particularly aggressive. I call it my "stroll". It's a good zone 2 workout without a lot of speed. A half and half builder of mental toughness and good running "base".

Yesterday was different. 

On Thursday, I logged into Training Peaks to see that the coach had posted this as my long run workout for Sunday: 14 miles/1:50. Followed by, "You have a good base coming off your Half Ironman." She had some other stuff in there too about pacing and for which mile but I looked right past all of that to what really mattered: 1:50.

RIGHT. Need I mention that during said 70.3 I dehydrated and had to WALK a good portion of the run? HMMM. Need I also mention that it's been a couple of weeks since I have done a long run (hello TAPER).  To say the least, I was a bit ..... incredulous.

But then, I asked, "What if?". What if I just hauled my ass out there and ran that long run like a race? Could I get close to 1:50? The weather was supposed to be perfect - 70 degrees and cloudy. My kind of day. SO why NOT? 

I drove to the Baltimore-Annapolis Trail. The only place I could think of that had already done the hard work of counting the miles (with mile markers). I knew the terrain (always a comfort) and there were enough hills to partially replicate what I would encounter on race day. I did a quick inventory. Hammergel, check. Water, check (there is water along the trail so dehydration would not be an issue). Sunscreen, check. Mental attitude in the positive, double check. 

I took off with the fancy Timex watch in tow. I wanted to get an idea of pace so I decided that equipment was in order for this long run. I decided to warm up for three miles and then build. After the build I would RACE the rest of the run. Despite ignoring most of her instructions, I knew my coach would get it. I needed to understand where I might blow up, how and under what sort of circumstances. I needed to see if I could come close to 1:50 without blowing up. But that's the rub. I had to be willing to blow up.

At the end of three miles, I felt great. Time to build. I looked at the fancy Timex. I was pleasantly surprised at my time. I was ahead of where I thought I would be. I was encouraged. Next up, the build. I kept reducing my time by 10 seconds per mile, then 15. I neared mile 6 and picked up the pace again. It was slightly uphill but I kept the increased pace. I covered the next mile, ate some Hammergel and turned around. Time to RACE. I set my sights on sub-nines. At this point in my healing adventure, this is a good time for me for a 14 mile run. When I looked at the fancy watch at mile 8, I couldn't believe it! I was doing FAR better than just sub-nines. I was crushing it. I picked up the pace again. Systemically, I felt fine. My glutes, however, were beginning to give way.

Mile 10. Always the hardest mile. It's in that middle place where you really have to focus. I was tired, my form was slipping and I was losing mental focus. STEADY PRESSURE on the HILLS, I kept repeating to myself (sometimes out loud) to bring my focus back to where I was. Here, running. NOW. FORM. KEEP the FORM.

By mile 11, it was all uphill. Steady pressure. As I ran, the sensation to stop and walk washed over me. I declared NO out loud. I began to run past the sensation. As I ran past it, I ran past what felt like a film of the former me - a diaphanous membrane with the texture of a bubble. The old me. The injured me. The me who has been holding me back. The fearful me. I ran through her. Through the bubble, the fatigue and doubt. I simply just ran through. I felt her trying to claw me back. As if she were saying "Wait, you don't know where this will go. You could fail or get hurt. You could...." I kept running. I slipped through the membrane and mile 13. 

ONE MILE TO GO. I was still running. As fast as I could go. Leg turnover, excellent. Speed, good. Glutes and hamstrings, OUCH.

As the "finish line" approached, I looked down at the display of the fancy Timex: 2:06. NOT bad. NOT bad at all. Sub nines for training means sub nines for the race. Tired, sore, achy and happy, I stretched and listened to the birds singing around me.

I glanced back up the trail, through the trees to the wooden bridge where legs burning and at their limit, I defied myself and ran through. I smiled. I didn't blow up. I made it. And I will again. Metric Marathon, here I come.