Running with the Mothership: My Garmin Olathe Marathon Experience
I hadn’t planned on running a spring marathon this year, and hence haven’t done marathon-specific training during the last half-year. But when I returned to the U.S. from Spain for my dad’s upcoming birthday and saw that the Garmin Olathe Marathon was happening during my visit, I couldn’t resist. Having become something of a Garmin fanboy of late, running a marathon that starts and finishes at Garmin’s worldwide headquarters—a.k.a. the Garmin mothership—was too intriguing to pass up.
My Garmin Journey
Garmin has been a constant in my life since the 2000s, starting with an in-car GPS that replaced my reliance on MapQuest printouts.
Around 2009, I upgraded to the bulky but functional Forerunner 305—my first wrist-based device that provided meaningful data beyond simple timekeeping. Later, I moved on to the sleeker Forerunner 110. Both of those early GPS trackers occasionally “bricked”–froze up where no amount of resetting would get them to work again. But Garmin’s world-class support always came through, quickly sending me replacements even when they were out of warranty.
There was a brief interlude from 2014 to 2016 when I was deep in Microsoft fandom and wore the Microsoft Band 1 and 2. When Microsoft abandoned the Band after the second generation, I returned to Garmin and have kept one on my wrist ever since. Currently, I wear a Garmin Epix Pro (Gen 2) that I affectionately refer to as “my coach.”
Garmin is a fascinating company. Unlike other tech giants headquartered in, say, Silicon Valley or Seattle, Garmin operates out of Kansas—a unique location for a company that is a leader in sports technology. While the Sunflower State is otherwise not at all known for high technology, it is home to one of (or the) most prestigious gravel cycling races in the world, Unbound (née Dirty Kanza). That is simply a happy coincidence, but Garmin has become a major sponsor of the event and has helped elevate its profile.
Why This Marathon?
In addition to my Garmin fandom, I had another reason for choosing this race: I had completed marathons in all 50 states but hadn’t broken four hours in Kansas yet. This race was my shot at fixing that. Plus, Kansas City is only a short, direct flight from Denver—perfect for a weekend trip.
The Race Experience
The day started early. I woke at 5:00 a.m. and arrived at the start by 6:00 a.m. to grab my bib and race t-shirt. Parking close to the start line was plentiful, thanks to Garmin’s multi-level parking lot, which made a bag drop unnecessary.
In the start area, pacers were available for 10-minute increments. Predicting to finish around 3:28 but considering 3:20 within reach, I joined the 3:20 pace group—eight runners in total, five men and three women.
Taylor Swift songs played at the start, a nod to her relationship with Travis Kelce, the Kansas City Chiefs’ All-Pro tight-end. As the race got underway, I chatted briefly with the pacer, who had done this course four times and the Boston Marathon once. She likened this course to Boston’s, noting that the toughest hills came around Mile 18.
With fewer than 500 full-marathon participants, congestion was never an issue—unlike the Vig Bay Half Marathon I’d run a few weeks prior.
Fueling Strategy and Course Challenges
I tried something new this race: drinking Gatorade earlier than usual, starting at Mile 4 instead of Mile 6. Additionally, I carried four Honey Stinger wafers, intending to eat one at 1h30m, 2h00m, 2h30m, and 3h00m. The reason I brought those was because I couldn’t find sports gels at the King Soopers supermarket I went to the day before.
Unfortunately, while easy to eat under normal circumstances, Honey Stingers were difficult to chew during a race effort, so I ended up only consuming two: one at 1h30m and another at 2h00. Next time, I’ll ensure I have gels instead.
The first half-marathon went smoothly, crossing the halfway point in under 1h39m. But the second half was tougher, with a net altitude gain and rolling hills.
By Mile 16, all the men in my group had dropped off, leaving only three women beside me. When the hills arrived at Mile 18, I struggled to stay on pace, slipping back but fighting to rejoin.
At Mile 19 with yet another climb, I started to lose contact with the group again, and I thought of Filippo Ganna’s tenacity at Milan-San Remo when he clawed back to the leaders. I wanted to do the same, keeping the 3:20 pace group within sight.
However, from Mile 20 to the end, I was battling cramps in my left calf and both quadriceps, surely due to not having done a long run over 15 miles this year. The last 5K was a grind—gradual uphill, slower splits, and pure focus on preventing complete muscle failure. By this point, I had completely lost sight of the three remaining runners from my pace group, who all ultimately finished in 3:20 as the #3, #4, and #5 women overall.
The Finish and Post-Race
Ultimately, I crossed the line in 3:26:48, with lots of time lost in the final 5K. Still, it was enough to podium in my division: third in age group.
Though I felt woozy post-race, I stayed only ten minutes before heading to my hotel for a shower before its 11:00 a.m. checkout time. Next time, I should request a late checkout, regardless of how confident I am in finishing before regular checkout.
Later, I returned to explore Garmin’s massive campus before heading to Kansas City for a well-earned barbecue feast. Too bad none of the buildings were unlocked (I checked)—I would have loved to have a tour of its main lobby, its large employee gym, and its workplaces.
It was a spontaneous decision, but the Garmin Olathe Marathon turned out to be a fantastic experience—hilly, challenging, and rewarding. If you’re looking for a well-organized race backed by a great American company, this one delivers.
Race Data
Final time: 3:26:48 (7:50/mile pace or 4:54/km) official
Division place: 3 / 29
Male place: 41 / 282
Overall place: 49 / 454
Official results
There are 2 comments.
Good job! I don’t recognize the shoes in the last photo. Did you try wearing a plated shoe for this race?
Good eye, Adam! What happened was almost immediately after the race, I went back to the hotel to shower before checkout time. Then, I returned to the race to take photos and explore the Garmin campus. So the shoes I was wearing in the photo--classic Saucony Jazz--were not the carbon-plated, Saucony Endorphin Pro 3 shoes I used in the race.
It also explains why I am wearing jeans in the photo. I did not run the race in jeans like the guy who did so during the Boston Marathon two weeks ago.
By the way, the Endorphin Pro 3 shoes in size 10 felt both comfortable and speedy. I didn't get any black toenails like I did wearing size 9.5 of those shoes at the Marine Corps Marathon.