What’s behind a default running pace?

Today’s run (street) 2.5 miles

Paces are a funny thing. I often find it difficult to gauge my speed as I run. There’s a default pace that I maintain when I’m not thinking about performance. That’s usually my starting point for taking it up a notch in a tempo run or slowing down to conserve energy on a longer run. I’m still not sure why my stride and cadence always seem to lock in around 9:30 per mile. Why not 9:00 or 8:30? When I run I sometimes imagine that I’m in a race with other runners. I do this because in races my pace usually drops into the 8:00 range. The theory is good but the practice is usually unsuccessful. Just imagining competition doesn’t seem to help my performance. I’m sure there’s much more to it than simply having others (real or imagined) by your side.

This morning I took off on a very cold morning with no regard to my speed. When my Garmin chirped at the first mile I looked at the watch to see that I’d paced it at 10:06. This was a surprise and even a shock because I’d felt like I was moving faster than that. I picked things up and by the 1.5 mile mark I was running closer to 9:40 per mile. Still not fast but definitely faster. I wasn’t thinking about my speed but I was concentrating on where my feet were landing. My average cadence has increased about 3% since last year which I thought should yield faster paces overall.

I think my focus on mid-foot landing might actually be preventing progress on speed because, while my steps per minute may have increased, my stride length has probably decreased. I’m okay with that because as I build my base I’m expecting to continue increasing cadence to the point where my speed does increase. Since I can rarely tell how fast I’m actually running I should probably look more often at my watch to see how I’m performing. I’ve always resisted that because I don’t like the pressure to maintain a specific speed. I guess I need to decide what’s most important.

Some new perspective on performance goals

Today’s run (street): 2.75 miles

I’ve been thinking about my running focus for 2011 and my goals for next year. I’d like to increase the length of my runs and also work on tactical performance. In terms of distance, I’ve been averaging between 6 and 7 miles for my weekly “long” runs and in the last month I’ve done some runs exceeding 8 miles. Lately my weekend distances have been closer to six miles due to my running 10K’s twice in November. My hope is to soon cover more distance than that – 9 or 10 miles – as often as I can. The toughest part of that is finding the time to run for 90+ minutes and to find interesting routes that provide enough distance.

In terms of tactical performance, I’ve thought about the way I’ve trained over the last month, with easy runs at easy paces preparing for races where I go all-out. It seems to be working. My average training runs have been on the middle and high side of 9:00 per miles but I’ve managed 9:05 and 8:53 respectively on my recent 10K’s. I’d like to continue the easy runs (like this morning’s steady run at 9:30/mile) but in place of races (I’m not sure if I’ll compete again this year) I might try some “Run as fast as you can for two miles” workouts. Rather than suffering the complexities of speed drills I’m thinking this might accomplish the mission of recruiting fast twitch muscles along with the slow. I’m going to make it a goal to run two miles under 8:00 per mile. That seems like a challenging but viable goal. Right now I’m not sure I can break 8:00 for one mile although my experience at the Long Beach 10K tells me I’m close.

Sitting at the top of the bell

Running with the fast pack yesterday was bittersweet. On one hand I was thrilled to be maintaining a pace that was almost two minutes faster than my recent training runs. My elation was mitigated by the steady flow of runners catching up and passing me throughout the race. As I ran I thought about how these people were able to glide by me so easily while I was running fairly hard. I wondered how many I would find walking along side of the road during the last miles of the race. That was the case at both the Dirty Sock and Cow Harbor 10K’s. As it turned out, there were few people to pass, even at the end of yesterday’s race. It was a fit bunch of runners on the boardwalk.

Race results typically group in a bell shaped curve with a small segment of the fastest and slowest runners on each tail. With one exception, where I placed second in my age category, I’ve usually been the person sitting near the top of the bell. I’m actually fine with that because I’m only racing myself. When I came over the line I was happy to know I’d likely PR’d but also hopeful that Dave, who finished well in front of me, also had a better time than last week (he did). I think the strategy of running easy and long with some tempo runs in the mix is the best approach to date. My pace at the halfway point in yesterday’s race was 8:36 but I lost 2 minutes on the second 5K. If I can maintain my speed across an entire 10K I’ll have a chance of achieving another PR at that distance. No matter what, I’ll still be at the top of the bell, but happily I enjoy the view from there.

Pace expectations and the online calculator

Your guess is as good as mine

Today’s workout (elliptical): 25 minutes

Thinking about two of my planned races in November, both 10K’s, I decided to analyze my performance at other race distances to help me manage my expectations. My PR for a 5K is 25:50, or 8:19 per mile. Both times I’ve run 8K’s I’ve averaged 9:00 per mile. That means that adding 3K (1.86 miles) caused my speed to degrade by 8.2%. That’s a big drop for not much incremental distance. Averaging all my 5K’s, my pace is 8:31 meaning that I generally lose 6% when going from 5K to 8K. My 10K track record is spotty because I’ve only run one of them on pavement but my overall pace averages 9:32, or almost 12% higher than my 5K average. According to the calculators that you can find online that factor in age grading, V02 Max and other formulations, I should be averaging 8:50 per mile on 10Ks. That pace is based on my 5K average. It’s a nice thought but I’m not sure how to get there.

For now I continue to focus on distance first and speed second. One thing that seems obvious is that adding more length to my runs and maintaining a consistent pace will bring my power curve forward, past the 3 mile mile mark. I’ve run 8 miles at 9:15 so I know I can improve on my current performance. I’ll keep that in mind this weekend when I rerun the Cow Harbor course in Northport.

Memo to self: Check elapsed time on the Garmin

Today’s run (street): 3 miles at 10:14

I don’t know how it happened but I ended up running for much longer than I’d intended this morning. My heel problem seemed much less noticeable last night and I gave little thought to it this morning until I took my first steps running. Once again I felt the pain — not sharply — but there it was. I briefly considered turning back but I chose to keep going at a much slower pace than I normally run. I wore my Brooks that offer great protection and focused on landing on my mid foot and avoiding direct heel strikes. This is easier to do with the Kinvaras that are almost the same height between heel and forefoot but I’d chosen to wear the Brooks  this morning for their superior cushioning.

I knew I was running slower than usual but I didn’t want to exacerbate my injury. I mapped out (in my head) the route I would follow and figured that I’d cover a little less distance than usual given my slower speed. Somehow I got caught up in the rhythm of my run and didn’t pay any attention to my time or distance. When I finally arrived home I looked at my Garmin and saw that I’d covered 3 miles in a little over 30 minutes. This actually shocked me because I didn’t notice that I’d run eight minutes longer than usual. I was not surprised to see that my pace was a minute slower than average. It was the trade-off I made for protecting my foot this morning. I was disappointed that I lost eight minutes of recovery time between my run and my shower but I still had enough time to finish my coffee. I’ll probably do an elliptical session tomorrow. That will be kinder to my foot and hopefully I’ll recover from this heel problem before the weekend.

Running and sailing — how’s that for a duathlon?

Setting sail on the Eisenhower Park pond

Today’s run (Eisenhower Park): 4 miles at 8:32

This morning me and my friend KWL headed early to Eisenhower Park for a training run. We’re both competing next weekend — me in the Dirty Sock 10K and he will be running a 10K on Saturday and participating in a 100 mile cycling event on Sunday. Our plan for today was to cover about four miles around the park and then meet up with my wife and kids for a little remote control sailing. More on that below.

KWL has only been running for about a year. In fact it was just a year ago that he participated in a Fun Run that I’d organized in Central Park and, without any prior training, he beat a handful of experienced runners. He’s an avid cyclist and that athleticism carries over to other activities. Our run together was well timed (for me) because KWL set a quick pace and we ran the 4 miles with split times of 8:28, 8:18, 8:31 and 8:48. We started with a couple of laps around the southern paved trails and finished with a lap and a half around the big pond. At least that was my 4 miles. KWL continued to run another mile while I waited for my family to arrive. I was very happy with my pace but less happy with my stamina. I could have run another mile when I stopped because I began to tire. I didn’t want to overdo things since I’d run hard the preceding week and I’m planning to keep up the pace in my final runs prior to race day.

Tall Ships ready to set sail

After the running was completed we met up with my family. KWL opened the back of his car and showed the kids the two remote control sailboats that he and a friend had made. The kids were surprised to see that the boats stood higher than their own height. These sailboats were impressive and as I watched them glide over the water I was amazed by their speed and maneuverability. The fact that the boats had no motor for propulsion (only a small servo for turning the sails and the rudder) made it both a serene and exciting activity. Near the end my son handed over the controls of his boat and I got to do a little sailing myself. We ended our Eisenhower Park activities by 10:00 AM and still had plenty of day left. It was a great way to spend our Sunday morning with a good friend and I had yet another great training run.

Training is paying off with two speedy runs despite the hills

Friday’s run (Central Park): 3.25 miles at 8:39
Today’s run (street): 4.5 miles at 8:36

We have guests coming over today so I set out early to get in my run. My focus, both today and yesterday, was on maintaining a brisk pace over routes that presented some hill challenges. Yesterday I headed to Central Park around noon and followed a route that started by following the lower and upper loop on the east side. I crossed to the west north of the Great Lawn and finished my run down the loops along the west side. The temperature was around 75 degrees and that helped at the start. I ran the first mile, that has a couple of noticeable elevations, at around 8:05 per mile, which is fast for me. My split speed decreased for miles 2 and 3 but I did keep my pace well under nine minutes the whole way through. A focus on speed has definitely improved my performance and I’m happy with the numbers but I do wish I could just go out there and run for fun. But running for fun does not contribute enough to conditioning and I only have one week before the Dirty Sock 10K.

My run this morning mostly took place in a business park located near my house. it’s not the most visually interesting place to run but the wide open streets and a loop that is 2/3 uphill and 1/3 downhill makes for a great training ground. I ran the loop two times and tried to maintain a rapid cadence. I averaged 88 SPM for the first mile and gradually fell to 83 SPM by the last half mile. Even so, I bettered the 80 SPM that I have averaged most of this summer. I finished my training cycle by ducking into neighborhood #3 which is mostly flat and provided a welcome relief from uphill running. From there I headed home, tired but still remaining under the 9:00 threshold.

Last night my wife told me about a 5K race that was being held at Sand’s Point this morning. She suggested I run it because it’s a beautiful place right on the water. I decided that I needed to do the hill training instead, to prepare for next week’s race. It would have been fun to spontaneously run a 5K but part of my enjoyment of racing is the anticipation of the event and the strategy and training that precedes it. I’m really curious about how I’ll do next Sunday. Will my performance training pay off or will I end up close to my time from last year? I thought I’d trained better and incorporated better strategy before the New Hyde Park 8K in June but I ended up no faster (or slower) than my 2009 run. I’m planning to run with my friend KWL tomorrow and then run on Monday through Wednesday during the week. I’ll finish my taper with an elliptical session and rest for Sunday. At least that’s the plan for now.

7:04 pace for 2.8 miles? All it takes is a little math

Today’s run (street): 2.8 miles at 8:59

Once again I managed to squeak under the 9:00 per mile threshold for my early morning run. While I haven’t been all out sprinting during my runs I have been putting a lot more effort into the process. It makes me wonder how far I could really push it without my heart rate moving into dangerous territory. 8:59 makes me happier than 9:00 but, regardless, that pace range was characterized as “pedestrian” in an article I recently read in a running magazine. How insulting! I may run at a pedestrian pace but  according to other articles I’m really much faster than that. Based on what I’ve also recently read, here is the Emerging Runner Guide to rationalizing your pace:

1. Every 5 degrees above 60 adds 20-30 seconds per mile to pace
@ 75 degrees (3 x -15 seconds) =  8:59 – 45 seconds = 8:14

2. Every 10 degree difference above 60 at the same relative humidity = 35 seconds per mile
@ 75 degrees (1.5 x 30) = 8:14 – 45 seconds = 7:29

3. Age compensation (compared to fit 20-something runners) and 4:00 AM start time
Lets just subtract another 25 seconds…

Using the above guide I see that I’d actually achieved an average pace at 7:04 per mile this morning. How about that?! I guess I’ll need to work a little harder or find more formulas to get me into the 6:00 range.

Doing what it takes to stay under 9:00 per mile

Today’s run (street) 2.5 miles at 8:59

I’ll admit that I like my current focus on speed and pace and I’ve been looking forward to my early morning runs even more than usual. I’m not running fast at 4:00 AM but compared to the paces I maintained throughout most of July, I am running much faster. My definition of a decent pace begins at around 9:05 per mile. I’m generally pleased when I meet or exceed that time. My psychological threshold is 9:00 minutes and that’s when I feel like I’ve accomplished more than merely covering my distance. Right now, in the midst of summer, 9:00 per mile is much harder for me to break than when I’m running in 20-30 degree temperatures. I want to do better on the Dirty Sock run this year and I believe that consistently training at paces around 9:00 per mile will get me there. However, trails can become more difficult based on their condition. If it rains close to start time all bets are off.

I managed to break my psychological threshold this morning, clocking an 8:59 pace for two and a half miles. It was already close to 80 degrees when I left but without the sun I felt like I could push without straining. I’m focusing primarily on form (vertical alignment, arm positioning) and cadence. On my slow days in July, I hovered around 80 SPM and on longer runs would fall as low as 78. These days, as I run, I think about how quickly I’m turning over my stride, how high my trailing leg is going and how much time I can spend off the ground. Higher cadence does influence stride length but I think that’s okay. In Born to Run, Christopher McDougal writes about the advantages of a shorter stride for mid-foot running and I agree that it does provide a feeling of moving along well.

My friend BJS sent me some notes that he made from his Cow Harbor 10K training last year. They are extremely helpful in understanding the course and setting expectations. He mentions a couple of big hills that must be respected. I think that will be the theme for one of my upcoming weekend training runs. The Dirty Sock course has no measurable elevations but, even so, I’m expecting that hill training will help me.

Yet another shoe buying experience at Jackrabbit Sports

Today’s run (street): 2.5 miles at 9:09

Yesterday afternoon I paid a visit to Union Square with my friend KWL for noodles at Republic and a visit to Jackrabbit Sports. KWL is participating in a two day event later this month, running a 10K on one day and cycling 100 miles the next. His New Balance running shoes needed replacing so he thought it would be good to have his gait analyzed to help him choose the right shoe. Jackrabbit’s staff are knowledgeable but they can be a bit arrogant. The person who rang up our purchases was downright nasty, enough so that I’d reconsider returning there. The person who helped KWL was fine though and after confirming that my friend is a neutral strider, he provided pairs of Brooks Ghosts, Saucony Triumphs, New Balance 759 and the ASICS Nimbus, along with the ASICS Cumulus pair that he used for gait analysis on the treadmill. KWL ended up choosing the Cumulus and he ran with them last night and gave them a good review this morning.

Today’s run was done under extremely humid conditions but without the sun or oppressive heat it wasn’t too bad. I continued my focus on form and cadence but today I was unable to keep to under 9:00 per mile. I did wake up feeling more tired than I normally do and worried that I was fighting off a cold. I thought about staying indoors with an elliptical session but I went with the original plan and ran. I wore my Saucony Grid Tangent 4’s but they didn’t give me much help on performance today. In my conversation with the Jackrabbit salesperson yesterday he mentioned that the Grid Tangents and other light stability shoes don’t sell well and a few models of that type (like the Grid Tangents) are no longer sold in their stores. The only shoe in that category that does sell well is the DS Trainer. I don’t expect my shoes to do the work to make me a better performer, that’s up to me. So far I’m pleased with my progress this week. A little extra effort has gone a long way.