I don’t post every day, but you can find me sharing my daily running and thoughts on Instagram!
I shared in my race recap that I ran Sunday mostly by feel – and not by pace. But how do I do this and what does it really mean?
So, I still race with my Garmin and GPS on – mostly because I want the data post-race but also because it does keep me honest about going out too fast. My Garmin will provide me my mile splits – if I want to see them, I just need to glance down when I feel the vibration. As I’m racing, I can only see the total time I’ve run. (On Sunday, I forgot to do this before the race, but was able to change the view so I only saw the current time.)
I did this for the first time two years ago for the NJ Marathon. After a series of sub-par marathons, I did some serious self evaluation and came to the conclusion that I was letting the pace dictate the race. Race goals and paces were controlling me during the race. I would spend almost the entire race staring at my watch, obsessing over the pace. I was forcing the pace rather than letting it come naturally. And if/when I started to see the paces slow down, it would psych me out.
Several years ago, I set a lofty (and unrealistic) goal of sub-3:10. I knew that I needed to average 7:15 per mile and so I ran the first 15 miles of the race staring at my Garmin to ensure that each mile beeped between 7:10 and 7:15. Anything over 7:15 and I started to panic.
Take it from me – this is not a fun way to race. Nor is it a smart way.
So I tried the new pace-free approach for the 2014 NJ Marathon, both Boston and Wineglass Marathons (this past fall) and then this past Sunday for the NYC Half. And each one was a success.
I’m not going to lie – it is a bit terrifying to line up at the start and know that you are just going to run without knowing the pace. There is always some self doubt – what if I end up starting way too slow? What if I go out too fast? The first time I tried this was immensely terrifying – but what was the worst that would happen? Blow up during a race? Already have done that. Not reach my time goal? Already done that too.
Running by effort is how I train. This is not something new on race day. I often hide my watch under my jacket or change the display on my long runs during marathon training. I need to run 18, 20, 23 miles, so what does it matter what pace I’m running? As long as I feel that the effort is mostly easy, it’s a successful run. Pace is secondary.
I’ve also taught myself to not obsess during tempo runs (doing these runs in the total darkness also helps prevent me from obsessing since it’s hard for me to see paces). I’ve learned to take cues from my body and learn what different efforts (and consequently, paces) feel like.
I speed up when my body wants to.
I slow down when it feels like it needs to.
Blissful ignorance from mile to mile.
And check-ins when I get the mile splits to reign it in if I start to get carried away.
It also eliminates the need to hit specific paces each mile. I still have a goal range for finish time, and thus overall paces for the race. But, it’s not a black or white number now.
Take Sunday, for example. My goal range was 1:29-1:30, which is about 6:47-6:52. But I never felt that I “needed” to be in that range when I was racing. I didn’t start calculating potential finish times until mile 10. There was zero obsessing over paces. Most miles ended up being under this range. Mile 4 was well over. And that not only is okay, but makes sense. Because I was racing by effort, mile 4 should have been slow since it was Harlem Hill. It was likely 7:30 or slower going up Harlem Hill – which is ~30 sec/off the slower range of the goal times my coach gave me. If I had been seeing my pace, I can almost guarantee I would have freaked out seeing those paces and/or would have pushed too hard going up the hill so that I was within the window from my coach. Short term, this would have been fine and I would have had a faster split for that mile. But I likely would have exerted too much energy on that one mile and paid for it later in the race.
Excluding the last segment (Garmin shows 8:16, but I didn’t stop my garmin immediately), my three slowest miles were in the first 4 miles of the race: Miles 1, 3 and 4. My fastest four miles were all in the second half of the race: Miles 7, 8, 9 and 12.
If you are struggling with pacing on race day, worrying about paces rather than truly enjoying yourself or constantly feel like you are coming up short despite having a good training cycle, I’d recommend to try going watchless to see what happens. Running by effort is certainly not for everyone, but it’s worth a shot, right? What’s the worst that can happen? But definitely try it during training first – get comfortable with what effort and paces feel like and then try it during a race.