OR - You're ready for a good one this weekend, just go out there and do your thing. Consider the following an homage to the flyer...
Gordon Tremeshko wrote:
GoFaMiAnHo - I know you mentioned non GPS watch only, but doesn't running the same tried and true loops and knowing how long it takes you to complete them today versus a previous week/month/year kinda function the same way? Or do you block that out? I think I'd still be comparing to times I've previously run "Robert's Hill easy" even if unintentionally.
Interesting question, Gordon - gave me something to think about on my run around Robert's Hill yesterday! Picking up on what you said about different approaches to training being partly a matter of personality, it would probably be fair to say that my own approach, over time, has tended to go back and forth between "worrywart GoFaMiAnHo" and "space cadet GoFaMiAnHo." So, an honest answer to your question would have to acknowledge that sometimes I have tended to lean more one way, and sometimes I have tended to lean more the other. That being said, I've come to recognize that running like a space cadet works a lot better for me than running like a worrywart. (Just to be clear, the space cadet vs. worrywart thing is intended strictly as a description of my own personality, not as a knock on anyone else's approach to running, whether more structured or less. And nothing that I say below is intended as a knock on anyone else's approach, either - it's just an attempt to describe what has worked best for me.)
So, speaking from the perspective of space cadet GFMAH, when I go for an easy run, and especially an easy trail run, comparing times in the way that you're talking about is something that I just don't worry about that much, even if I'm doing a route that I run on a regular basis. It's not that I block it out, exactly - that suggests a level of mental effort that's not really taking place, and the fact is that I do have a pretty good idea of how long a given route will take if it's something that I run regularly. So, for example, I can tell you that if I'm running my usual route in the Sawmill Hills, it's something like 8-10 minutes to the top of the first climb, 15-17 minutes to the brook, 22-24 minutes to the cliff, 28-30 minutes to the flat rock, and so on. But it's not like I'm really thinking that I want to hit checkpoint x in time y or faster. It's more like, "I want to run for about an hour, so if I go to the flat rock and back that should work out about right." Sometimes I'll go slower, sometimes I'll go faster, but as long as I get in what feels like the right effort for the day, whether a given run ends up taking a few minutes shorter or longer just isn't something I worry or even really think about.
Of course, "run your easy runs easy" is something that many people do, even in the context of approaches that are much more structured than my space cadet training. With that in mind, I think the bigger difference may be that I try to run primarily by feel for more demanding runs/workouts as well - and in fact, the more demanding a workout is, the more I try to consciously emphasize running by feel, to the point that the most demanding parts of the most demanding workouts would be the least planned out ahead of time.
How does this work in practice? Let's say I felt like doing a workout. I would decide what general kind of workout I felt like doing. Very often I would make the decision during or after my warmup. I would then try to start the workout at the kind of effort that too hot calls "comfortably hard" and look to sustain or build from there, depending on how things went. A lot of the time the effort would pretty much stay in the comfortably hard range. Workouts of that kind tend to fall into a fairly predictable pattern (trolley track steady, trolley track fartlek, 4 x park loop, whatever), and I tend not to worry about the details with them much more than I would with an easy run, say. It's just get the work in and whatever it is is whatever it is. But if I'm feeling really good, and it seems like a good day to go a little harder, then sometimes I will go ahead and do something a little harder, and occasionally quite a lot harder.
To give a concrete example, when I was training for my second marathon, I did a workout of 8 x mile with a 400 jog recovery. The first one, which I ran with some guys with my club, was something like 6:10 or 6:15. From there they got progressively faster until I finished the last one, solo, in 5:08. I realize that's not very fast for a lot of people, but it was for me - my mile PR at the time was 4:59, and that was a time that I had struggled for years to achieve. I didn't go into the workout planning to run any specific number of repeats, or any specific pace or progression of paces, I just went with the flow. To borrow OR's term, it was a flyer in mile repeat form, and it blew the roof off of what I thought I was capable of. And the thing is, while the effort was very intense, it wasn't like I was suffering - it was more like I couldn't help myself, like I was being consumed by some kind of animal appetite. To put it another way, it was less like baking cookies and more like becoming Cookie Monster. Most of my best races have been the same way.
So, in short, for space cadet GFMAH, running by feel isn't just something to do while preparing for/recovering from more structured workouts, it's a path to more and more intensely running by feel. And again, it's not so much about "blocking out" external data or training an internal clock (as Stone Cutter has talked about in the past) as it is about tuning in to my own body, gradually training it for progressively stronger efforts, and getting the Cookie Monster good and hungry so that he's ready when his time comes. In my experience, that's the approach that has worked the best for me.
Go get yourself some cookies, OR!