Running to the edge

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

I don’t know if I’d call it running fast but I am definitely running with more urgency this week. Instead of falling into my normal pace I’ve attempted to push myself a little harder, enough to feel like I’m running and not “jogging.” My expectations for performance are lower in the early morning, especially when it’s hot and humid. Most of the time my pace at 4:00 AM averages about 15-20 seconds per mile slower than when I run at 8:00 AM. I also run slower in the summer months and the combination of these two factors has put me into the mid to high 9:00 range for most of my weekday runs. After reading some recent articles in Runner’s World, Running Times and Men’s Journal about performance and race training I decided to break free of my default morning pace and run with a constant focus on speed and form. I’m not pushing past my comfort zone but I’m traveling on the edge.

The temperature on the local station said 75 when I went outside but I immediately sensed that the humidity was back in full force. Ignoring that, I set out quickly and managed to keep my pace brisk over the first street that goes slightly uphill before it connects to another road that descends at about the same rate. I noticed that, despite the humid air, the moderate temperature and the lack of sun made for decent running conditions. I pressed on experimenting slightly with my stride and form. I followed some different roads to alleviate the tedium of always keeping to the same streets and that made it interesting. The new route helped distract me enough to maintain a fairly energetic run.

Throughout the run, I concentrated of front foot landing which was not that easy in my Brooks but I managed to land that way more often han not. I also tried to get more lift on my ascending leg while keeping my stride shorter to increase cadence. Sounds pretty technical but it translated to a decent time, just barely under 9:00 minutes, better than almost any other run I’ve done of late. This weekend I’ll be doing a longer run in preparation for the Dirty Sock race and I don’t plan to incorporate any speed technique for that. Tomorrow and Friday I will continue to push to the limit — and hopefully push those limits even further.

Mid-foot running is great but where’s the speed?

Today’s run (street): 2.6 miles at 9:32

Stepping out in the Kinvaras for this morning’s run reminded me why real running shoes, even lightweight minimalist ones, serve an important purpose. I did well with my pool shoes on Sunday and had no residual aches or pains after my run but my feet felt far better during today’s run in the Sauconys. The Kinvaras are almost flat between heel and front foot but they aren’t built as low to the ground as some other lightweight trainers. The slightly higher platform allows for a little more cushioning and provides a comfortable ride. My longest run in them so far was 5.5 miles but I have no concerns about doubling that distance (except, of course, for my own limitations). It’s interesting that I’ve lost a lot of speed in the last couple of months. My first runs in the Kinvaras were under 9 minutes per mile. Now I’m averaging closer to 9:30 miles most days regardless of the shoes I wear.

It was 85 degrees and humid when I started my run at 4:05 AM today. With no sun and a slight breeze it wasn’t bad. For some reason the Garmin foot pod always over-counts distance on the Kinvaras, probably due to the flatter angle of the upper compared to my other shoes. This translates to faster paces on the FR60 display and more distance captured. I always check my route against Gmaps to find the margin of error and saw that the indicted distance and pace (2.67 mile & 9:18/mile respectively) were overstated by 3%. I can rarely tell while running at 4 AM whether I’m tracking mid 9:00 miles or high 8’s so I’m often disappointed (and occasionally delighted) when I calculate based on Gmaps. Regardless of pace or distance I got out there in the heat and covered some good ground while reinforcing my mid foot striking style. The speed will come. I keep telling myself that.

Consistently inconsistent

Today’s run (street): 2.45 miles at 9:07

I don’t think I’ll ever fully understand why some runs are faster than others. I know a person who has run the same 4 mile loop for years and can usually predict his finish time within 15 seconds. I may have opened a can of worms by suggesting that he throw in some tempos to bring down his overall pace. He did that and now he’s got a different perspective. Up until that point, the run itself was the accomplishment. Now, after all this time, he’s concerned about pace and performance. Did I do him a favor in helping him get more out of his runs? Or did I contribute to a mindset that replaces the joy of running with the obsession of metrics? I also told him he should think about getting lighter weight shoes for a performance bump. What have I done!?

Of course it’s not the shoes that make you faster. Or is it? Since switching over to the Saucony shoes last week I’ve had noticeable improvement in my pace, often beating my usual times by 20-30 seconds per mile. With nothing else to explain it I had to guess it was the shoes. After three runs in the 8:40-8:50 range I assumed I had moved to another stage in my running. I’d no longer be a 9-something pacer. The new normal is 8:45 and further improvement starts there. This morning I went out feeling good, equipped with the fast Kinvaras on a clear cool morning’s run. My pace felt steady and strong. At the point where I thought I’d covered a mile my Garmin said .78 miles. I felt like I was running well but I wasn’t covering the ground at the rate I’d assumed. I questioned whether the Garmin was properly calibrated because I had switched it from my Brooks this morning. Ultimately, I finished with an overall pace of 9:07 that is typical of runs at that time. I continue to wonder why the range of performance is as wide as it is. I don’t have any problems with today’s performance. It’s just that with all my tracking and even with the new lighter shoes, inconsistency is the only constant.

Saucony Tangent 4: Fast and comfortable

Saucony Grid Tangent 4

Today’s run (street): 2.45 miles at 8:40 per mile

After two runs in the Saucony Kinvaras I’m starting to believe that a shoe can really make a difference in performance. The Kinvaras are extremely light and have very little drop-off between the heel and forefoot. This makes mid foot striking easier than when running in a shoe with a higher heel. I closely track my performance and although I’m a 9 minute miler in spirit I’m more of a 9:10-9:20 miler in practice. So what am I supposed to think when I put together two consecutive runs under 8:50 per mile? Could I have improved that quickly — or is it the shoes?

That’s the question I asked myself this morning when I set out for a morning run wearing my new Saucony Grid Tangent 4’s. These are lightweight stability shoes that feel very good on the foot. Despite the light weight there was decent cushioning through both the heel and front foot. I took off and immediately noticed how quick they felt, my pace was more like a tempo run although I didn’t feel as though I was working that hard. But at 4:00 AM things can be deceiving. I’ve done runs at that time that felt fast but weren’t. I expected the same today but finished with an average pace of 8:40. That’s 5K race pace for me and almost unheard of at that early hour.

It may be too early to say for sure but these lightweight shoes from Saucony really deliver speed. I like the Kinvaras for the mid foot landing and the Grid Tangents seem sturdy enough to be a regular trainer for people like me who have a lighter build. So what’s to become of my beloved Brooks GTS 10’s? No worries, there will always be room for them in the rotation. They just may need to wait a little longer for their turn.

Walking for a cause and running just because

The Emerging Runner family walks for a good cause

Yesterday’s activities: 1.5 mile walk-a-thon plus  2.6 miles (street run) at 9:37/mile

Today’s run (street): 4.4 miles at 9:10/mile

It’s been an active weekend that started yesterday morning with the start of the Nassau County Red Cross Walk-a-Thon at Eisenhower Park. My wife works at the Red Cross as a volunteer so the Emerging Runner family spent from 8:00 – 11:00 AM helping to set up and manage participants who had come for the 1.5 mile walk. After Friday’s 6+ mile run in Central Park I was feeling the residual effects of the hills but I thought the walk would be easy and fast. It turned out that 1.5 miles seemed a lot longer than I’d imagined but I enjoyed every step. It was a strange morning for weather, alternating between overcast skies, bright sun and a 15 minute downpour that had crowds of people running for cover under makeshift tents.

My wife, son and daughter and I set out on the walk at a good pace and I enjoyed seeing the park from a different perspective. There were lots of runners out in the morning and I wished that I had worn running clothes but this was really about walking and family time. We had a lot of fun and the turnout was excellent considering all the bad weather that had been expected. Later on that day I decided to do an easy run around the neighborhood. The sun had stayed out and it had grown a little warmer but the winds grew increasingly stronger throughout my 25 minutes of running, I didn’t run fast but I wasn’t concerned about pace. It was nice to get a run in on Saturday, however short.

This morning I headed out early because it’s Mother’s Day and I wanted to be as available as I could for the rest of the day. My kids set up breakfast for my wife downstairs while she did her daily workout upstairs. I slipped out and did a neighborhood run going in the opposite direction of my usual loop so that I could fold in the longish hill on Jericho Turnpike. I still felt some residual tiredness from Friday but I decided to maintain a faster clip than yesterday and completed 4.4 miles at 9:10 per mile. I was very pleased with the pace because my effort level was low while my enjoyment level was high. It was still early when I returned home. So far, we’ve had a full day with plenty of time left to celebrate Mother’s Day.

Lengthening my long runs

Today’s workout: Rest day

A “long run” has different definitions based upon who is doing the running. For some, it’s runs over 13 miles with the half marathon length serving as the demarcation point. For others (like me less than two years ago) a 5K can be considered an aspirational length. I have been thinking about yesterday’s run and how it felt to break a personal distance record. Could I have gone on longer than the eight miles that I’d covered on Sunday? As a practical matter the answer is yes. I stopped when I did because I’d met my goal of eight miles – four out and four back. If my distance goal was nine or ten miles I probably could have accomplished that as well. I finished my run at eight because I had nothing more to prove on Sunday.

I have a goal of doing a 10 mile run this year. It’s a distance considered by some to be a nice training run while others view it as an impossibility. I’m happy that it is at least a possible distance for me at this point.. Looking at my splits for yesterday’s run, I noticed that my pace dropped measurably after an hour’s running. I ran the first 6.2 miles averaging 8:57 per mile but miles seven and eight were far slower, closer to 9:30. I really liked running for longer than an hour. It surprised me that I had enough energy to pass other runners even near the end. Perhaps I’ll look at increasing distance as my next focus point and worry less about pace. Well, maybe just a little less.

Pacing discovery on the treadmill

Today’s run (treadmill): 2.4 miles at 9:08/mile

Although I was fully prepared to run on the treadmill when I set up my gear last night I felt a little differently this morning. The alarm woke me up from a sound sleep and made me question whether a workout or thirty extra minutes of sleep would do me the most good. I would have liked the extra sleep but I knew if I didn’t run I’d feel guilty for the rest of the day. Despite its negative connotations, I truly believe that guilt has its good side. I had a little coffee and got on the machine, resigned to running a couple of miles.

As I started my run I compared the pace on the display to the pace on my Garmin that I knew was accurately calibrated. The two readings were closer than I’d expected them to be. I increased the tread speed and saw that the paces changed in sync with each other but once I got to target speed I found that I could achieve a faster pace on the Garmin, compared to the treadmill’s, just by quickening my cadence. When I resumed my default running rhythm the Garmin’s readout resumed duplicating the treadmill’s. It was an interesting discovery because now I know I can naturally speed up or slow down a little without needing to mess with the treadmill’s controls. That makes a big difference to me because much of my frustration with the treadmill is from the tedium that comes with being forced to maintain a hardwired pace.

Although I started off tired I did rebound and got through 2.4 miles at a decent pace. I don’t know why I find treadmill running so much harder than road or trail running but I do. Still, I rather it be that way than the other way around.

Sunday run with the Emerging Runner Girl

Yesterday’s runs (street): 4.4 miles at 9:02 + .75 mile fun run

Counting Friday’s run in the city, I managed to cover a little more than 12 miles this weekend. Out of those twelve my favorite experience was on a distance less than a mile (more below). With last Tuesday’s 4.8 miles in Central Park and another 2+ miles on Wednesday, I still fell short of my informal weekly goal of reaching 20 miles. Of course if I include the 2 miles covered on the elliptical last Thursday I’ll be able to claim that goal. Okay, done. 21 miles for the week!

As hoped, the rain slowed down by early Sunday afternoon and I took the opportunity to hit the neighborhood streets. I don’t generally do my best speed running at 1:30 in the afternoon but I tried to keep the pace as brisk as possible. Due to the wet roads I wore my Adidas Response 15 trail runners. That was less for protection on the slippery road service and more to keep my Brooks GTS 10’s from getting wet and dirty. I ran about 1.5 miles on local neighborhood streets and then cut over the neighborhood #2 for the bulk of the run. Since I was running in trail shoes I took advantage of a few areas alongside the road that had packed dirt and grass. It was pleasing to hear the chirp of the Garmin as I passed the two mile point. The third followed surprisingly soon after the second. At one point I looked at the watch and noticed that it was giving me readouts that said “00:15 ahead” which confused me. I then realized that when I updated the FR60’s firmware yesterday it switched to a default setup that included a virtual running partner. I would have had fun with the virtual partner if I better understood the interface. I again relied on my heart rate monitor to guide me in terms of effort. My pace seemed fast for those conditions but, after verifying on Gmaps, I confirmed that the Garmin was accurate.

When I got home from my run I was met by my 11 year old daughter who had been riding her scooter and waiting for me to return. We decided to run a loop around some of the local roads and covered .75 miles between 10-10:30 mins per mile. Though it had been months since we ran together she kept up very well. My daughter has near perfect running form and she lands on her front foot naturally. I think she was happy when I told her that I learn things by watching her run. Next weekend I hope we will be able to cover more distance.

It’s still very soggy in NYC and on Long Island so I’m not sure what outdoor running I’ll be able to do during the week. I’m planning to get at least one Central Park run in before next weekend, assuming we see clear skies this week.

A tale of two 3.5 mile runs

Yesterday’s run (Central Park): 3.5 miles at 9:12/mile

Today’s Run (street): 3.5 miles at 8:45/mile

Yesterday I was excited for the chance to do another run in Central Park. It was a busy Friday and I managed to wrap up morning meetings in time to change and meet up with my friend Steve for the jog up to the park. The skies were bright and the sun was out but the 57 degree temperatures felt cold on the building-shaded streets. We started our run at the 6th Ave. entrance on Central Park South and made our way to the lower loop to run counterclockwise to the north. Steve admitted to really feeling last Friday’s workout for a couple of days after our run but he said he could do six today. I told him that he may feel differently once he started to encounter the hills. We set off at a decent pace, low 9’s, and enjoyed watching all the activity in the park. At one point we were set upon by a group of tourists on bicycles who didn’t seem to understand the concept of sharing the road with pedestrians. We also saw a person running around wearing Kangoo Jumps that look like in-line skates with elliptically shaped spring devices on the bottom. He certainly got some energy response from the shoes. Looked like fun but I’ll stick to my Brooks for now.

Once we reached the reservoir we followed the path on the southern edge and then headed south. Steve was very glad at the 2 mile point that we weren’t really going to run six. He did a great job keeping up with me and I told him his reward would be downhill running to balance all the hills we’d hit on the way up. We ended up covering 3.5 miles and felt fresh, even at the end. Good thing too because we both had long afternoons ahead. We walked south back to our offices, energized for the rest of the work day.

I woke up this morning with a headache that I attributed to sinus pressure. Rather than hoping it would just go away on its own I took a Sudafed and ibuprofen and chased them with a strong cup of coffee. I headed out around 8:00 AM for my run. I warmed up after about a mile and covered a route that took me first around and then through the neighborhood. I was concerned that the effects of the Sudafed would impact my running and while I felt tired I still managed to keep a decent pace. I originally thought I’d go 40 minutes but I cut it short to ensure I’d be ready in time for this morning’s activity, an Arbor Day festival at a local preserve. I was pleased with today’s run. I’ve programed the Garmin to automatically roll through the various metrics as I run such as pace, distance, time and heart rate. I used the heart rate numbers rather than speed to guide me in terms of effort to expend. It paid off with a decent pace, close to what I achieved recently in a 5K race.

Tomorrow I have plans to meet my friend KWL at a local park for a run at 6:30 AM. The weather is supposed to be pretty bad so chances are we’ll need to postpone. That would be too bad but I can’t complain about all the great running weather (and great runs) I’ve enjoyed this week.

Time to calibrate the FR60

Today’s workout (street): 4.17 miles at 8:57/mile

Yesterday’s run felt so effortless that I wasn’t ready to stop when we reached the end. Business took priority over pleasure but I did feel great for the remainder of the work day. The run itself was work and I felt the effect of all those hills this morning when I woke up. Still, I was anxious to get out for another run. My wife and kids were volunteering at my son’s elementary school all morning. I had nothing on the calendar until after lunch so I headed out for my run around 9:00 AM with temperatures in the the high 30’s under overcast skies. My Garmin was fairly quiet so I knew I was within pace range although a check of the display showed my pace to be a little slower than it seemed. I stepped it up after the first mile and would periodically surge for 30 seconds to a minute before falling back to my default pace. I was running faster than yesterday’s city excursion and I felt the difference. All the same I didn’t feel that I was working that hard and the data from my heart rate monitor confirmed it. I felt like I had covered a lot of ground but I ended up only going a little more than four miles. It was just far enough to count as a good workout.

When I finished the run I checked my Garmin and saw it displayed 4.07 miles, averaging 9:10. 9:10 isn’t a bad pace and I figured that yesterday’s run had wore me out more than I’d thought. I then mapped the exact route using Gmaps and saw that the Garmin under-counted the distance by 2.3%. Adjusting my pace for that variance, my overall average was under 9:00 (8:57) and my splits were 8:54, 8:57, 9:03 and 8:59. Love the FR60! I’m going to try to calibrate it a little closer so I don’t have to do so much math. I haven’t messed with the calibration adjustment on the FR60 yet. The default accuracy is +/- 3%. It wasn’t all that easy to adjust the 50 so I’m hoping the 60’s controls are better. My problem with calibration is that I switch my foot pod often between my pairs of street and trail running shoes and every change affects the calibration accuracy. Overall, I’m happy with my recent runs and glad that I’ve made my way down to the low 9:00’s that I was running prior to my pneumonia disruption. I don’t know what I’ll run tomorrow. The skies are looking ominous but I’m hoping that this passes and that the trails are in good shape by Sunday.