Post-marathon thoughts: Running without my Garmin

Faithful for training, takes a nap on race day.

I talked in my race report for the recent Detroit Free Press Marathon that my Garmin crashed, lost its charge, and died less than 1.5 miles into the race. How did that affect my race overall?

My Garmin and I are pretty faithful to each other in training. I like to use it to keep myself at a steady pace, both when I need to pick it up a bit and when I need to take it down a notch. Of course I also try to take feel into account, but sometimes if you're feeling overly lousy or amazing, your biofeedback might be a bit off.

I know I started the race a bit slower than I would have liked, but I attributed that to getting into a groove and dodging discarded sweatshirts. I did try to stay in between the 4:15 and 4:20 finishing time pace groups, but with the start of the race being dark and hectic, I lost them pretty early on.

As I looked back at my official results, I hit the 5-mile marker at a pace of 10:21, about 30 seconds per mile slower than I was hoping for. Yech. But, at the time that felt like a sustainable pace. If I'd had my Garmin, would I have pushed myself harder than I could have sustained?

Of course, there's no way to tell, other than running a bunch of marathons and switching off using my Garmin or not — ha! I also have no way to tell how consistent I was able to keep my mile splits, but my 5-mile splits from the results suggest I started out steadily, slowed down a lot in the mile-20-ish range, and then picked it back up for the finish. I could have told them that.

I don't think not having my Garmin caused me to run too slowly. If that were the case, the wheels wouldn't have fallen off around mile 18. And looking at my splits from the results, I don't think not having it caused me to run too quickly, as the paces registered were still below my goal.

Lesson learned? Double-check that you don't need a hard start on race day, I guess, and be OK with the feedback your body is giving you... just in case.

Post-marathon thoughts: Training

Miles, miles and more miles.

In case you missed it, I finished the Detroit Free Press Marathon on Sunday. It's always something of a feat to run 26.2 miles, but I'd be lying if I said I wasn't at least a little disappointed I didn't finish with a better time.

But, let's be honest: My training just didn't support a faster marathon. Even the Yasso 800s I ran a few months ago suggested a 4:30 finish time. When it came down to it, the mileage and speed just wasn't there.

So, what happened?

First off, the Freep wasn't this year's "A" race, believe it or not. My main goal was my first 70.3, Michigan Titanium in August. Some of that extra time that could have gone to running went to swimming or biking instead. And when I was tired at the end of the day, it was most likely my run that got skipped.

I did do a tri last August, and it was only a week earlier in the year than my 70.3. But the difference in time spent on the bike on Saturdays was significant. A regular day for me last year was three laps of the park in about 2.5 hours; this year, I regularly did four and five laps and spent close to 4 hours on the bike. I'm sure this didn't help my energy levels.

My swimming volume was about the same this year compared to last year, and my run volume was a little less this year. I nailed all my long runs, but, like I said above, if I were to skip a workout it was most likely the run.

So, what to take away? If the marathon is my A race, I need to prioritize running miles and speed work. If it's not, and I'm still OK with a 4:30 marathon, then what I did worked perfectly fine. I would have liked to run faster, but I only have so many hours in the day. And the 70.3 was my first priority.

My race reflected my training, and I'm OK with both. I feel like I did the best with what I had at the time. And in the end, that makes for a successful marathon in my book.

Detroit Free Press Marathon 2014 race report

You might have seen this already, but here it is again, just in case. =)

Marathon No. 6 is in the books. It wasn't anything spectacular, and I was far from a new personal record, but ultimately it was a good time. And running 26.2 is always an accomplishment, no matter how long it takes you.

The excitement started at packet pick-up Friday afternoon. I got down there pretty early and drove around downtown for WAY too long trying to find a stupid parking spot. Walking there, I passed the 26 mile marker painted on the street and immediately got goosebumps. The expo was huge and there were a million things I wanted to buy, but I stuck to picking up my packet and buying only a bunch of Gu and Sport Beans.

Saturday was pretty quiet. I loaded up on carbs and tried to rest and relax my legs for most of the day. I got to bed at a decent hour and didn't toss and turn too much. The alarm went off at 5:15, which was plenty of time to get up, get dressed, choke down some breakfast and coffee, and have my husband drive me as close to the starting line as he could get about 20 minutes before the start gun. (Living nearby sure has its advantages on race day.)

I started walking toward my corral, putting on my hat, gloves and Garmin at the same time. Then I realized my Garmin wasn't beeping on. F---! I had charged it fully the night before, so why wasn't it working?!?!? I tried again. No beeping. I frantically started trying to remember how to do a hard start. Whatever combination I pressed worked and I heard it beep to life. Yes! Then I heard another beep -- the "batteries low" beep. ARE YOU KIDDING ME??? I had charged this thing all night long! I began to panic, shutting it off and on over and over again. No luck. The charge had not held. I had no idea how long I would have with pace feedback. I was going to have to run this by feel.

I tried to let myself get caught up in the excitement of the starting line. I planted myself between the 4:20 and 4:15 pace groups, hoping to stay somewhere in between. Some gal was jumping up and down to stay warm, and landed on the edge of my shoes. "I am NOT going to DNF this race because some dumb b---- broke my foot at the starting line," I thought, and moved away. We quieted down for the invocation and the singing of both national anthems -- since we run through Canada, we get both, and pretty much every Detroiter knows the Canadian anthem because of hockey. Then they blared Eminem's "Lose Yourself," to a cheering crowd. The countdown for the first wave started, and finally, we were off.

Around and around the city we go.

I ended up crossing the start line about 12 minutes after the first gun, and broke into a trot. I find it very hard to keep a steady pace for the first mile, as you're dodging slower people, jumping over discarded sweatshirts and gloves, and getting into a groove. My Garmin beeped for the first mile -- OK! We plodded toward the bridge to Canada and I took another glimpse at my wrist. Nothing. I had gotten less than two miles of info. Ugh! I couldn't see the pace groups anymore, so I tried to settle into something sustainable.

Losing use of my Garmin also tested my fueling strategy. I typically drink every two miles and eat a Gu or handful of Sport Beans and drink every four miles. Without the steady beeping, and not knowing at first what I was looking for in a mile marker, I switched to a strategy of Gatorade every aid station, fuel and Gatorade every other.

We crossed over the bridge into Canada just as the sun was rising. It was gorgeous! It's worth doing this race just for this moment. Some trucks honked at us, and the border patrol officers were making jokes and giving high-fives once we officially crossed. The crowd support in Windsor is always great. I saw my favorite sign of the race here: something like, "Runners only have to put in 90% effort in Canada." I laughed about this for the rest of the race. Around downtown we go and before I knew it I was in the tunnel, heading back to the States.

I tried not to think about that I was actually running under the Detroit River and just kept my head down and ran. It was pretty hot in there -- I ended up taking off my hat, and never put it back on. Before I knew it we passed over the border, marked with the countries' flags, and were heading back up into the fresh air. There was a good crowd and lots of cheering, which was nice. We headed out to Mexicantown, Corktown, and back into downtown. The half runners split off, and all I could think was, "Wow, I have to do this again!" Still, the first half felt like it flew by.

The second half of this race is where runners have to dig in, even more so than other races, I think. We run for a few miles on a straightaway, without much to break it up. I was starting to realize that my pace was unsustainable for too much longer, but I knew that my husband was at a friend's house cheering, just before the mile 18 marker. I told myself I could take a walk break to talk to him and then I would reassess. Sure enough, I spotted him and asked him to walk with me for a little. I ranted about my Garmin (and practically threw it at him) and how I was starting to falter. He also forgot my sunglasses, so I was mad about that for the next few miles. After a quick kiss, I was off again heading toward the bridge to the city's island park.

I walked up the incline, and that was about when the wheels fell off. I just could not get back into a groove. I alternated walking and jogging, stopping to stretch a few times. Ugh -- this wasn't good. I felt nauseated and just couldn't get my legs to move. Jog, walk, stop to stretch, repeat. It was cold and windy on the island, and there were lots of us death marching. I started taking only water at the aid stations. I thought about throwing in the towel and just walking the rest of the way. But I kept on, and after about three miles around the eastern half of the island, I felt a little better. A couple more walk/jog intervals and I knew I'd be able to shuffle it in for the rest of the way.

Mile 23 and we turned onto the Riverwalk, one of my regular running routes. Mile 24 and we passed a cheer station with beer, and the smell almost made me barf. Mile 25 and we approached one of the final turns to head back into downtown. My current power song, "Bulletproof" by La Roux, came on my iPod. I turned it up and picked up the pace a bit. I listed to the song twice and then turned off the music. I wanted to hear every cheer. One last turn -- where the 26th mile marker I had seen Friday was painted on the road -- and the finish line was ahead. I ran and ran. And then I was under the finish line! It had been tough, but I had done it again. Yes!

A kind volunteer confirmed that I was finished and that I could stop running. I'm pretty sure he was evaluating my mental state -- ha! He gave me my medal and I shuffled down the line, immediately starting to hurt. I chugged a bottle of water but still didn't feel like eating anything. I found my husband shortly afterward and after a sweaty hug and a few pictures, I shuffled to the car. By this time, my muscles were starting to tighten up and I needed his arm for support. Thank goodness for his car's seat warmers. Since I didn't have my Garmin at the race, I didn't know what my finish time was, but in the car I was able to look up my result. I was pleasantly surprised to see a 4:28:54. I had squeaked in under 4:30.

It was a quick drive home (again, an advantage to living close by) and then started the age-old question: Shower, eat or nap first? I went for a long, hot shower first, then a giant plate of pumpkin-spiced pancakes, and then a nap. The rest of the day was spent eating cookies, pizza and cheese and doing squat.

It wasn't the race I envisioned, but even when I had curve balls thrown at me, I pushed on and got it done. And I have my sixth marathon medal to show for it. Not too shabby.