Running Faster but Gait's A Disaster

In other words, I'm limping

In my April 14 post, I wrote about the way my blood pressure medicine was negatively affecting my running performance. A change in dosage made such a difference that I'm now running about 2 minutes per mile faster than my pace prior to March. 

While that's great, my lower back is not on board with it. Running harder seems to have triggered an old disc issue and on most runs my stride starts slightly unbalanced. This is likely due to nerve aggravation. This irritation has gone on for a few weeks and my aggravated nerves are beginning to aggravate me.
 

The problem minimizes after about 8 minutes into the run but it doesn't completely disappear and my antalgic gait appears to be costing me 30 to 45 seconds on my first mile. I really want that time back. I'm applying heat and ice to my lower back and have been doing active leg swings on the advice of Runsketeer TPP. It's helping, but recovery has been slow. 

In terms of performance, I looked at my running history on Garmin Connect and the data revealed a sharp drop-off in my pace that started in June 2017. 

This coincided with two interesting data points:

• My stride length shortened 8.5% compared to the prior six months. 
• My average cadence/SPM fell 8.6% over the same period.

I usually prefer downhill, but not in this case

Something caused this and I wanted to know what it was. Looking at my medical history at that time, I saw two things that happened around June 2017 that could explain it. 

• My doctor put me on blood pressure medication. 
• My ophthalmologist put me on a carbonic anhydrase inhibitor to address an eye pressure condition. 

I suspected that these drugs were negatively affecting my running, but I didn't know to what extent. Now that my BP medication is at the correct dosage and I'm no longer on that eye medication, my cadence and speed have returned to May 2017 levels. As great as that is, my stride length has not dramatically improved. I attribute that to my current back issue, so I still have a problem to solve.

I'm going to keep heating, icing and dynamic stretching and hopefully the nerve issues in my lower back will recede. If that happens, I think I may be able to improve my average pace by at least 30 seconds per mile. Will I ever get back to running well enough to credibly compete again? Well, that's the subject for another post.

A Virtual Pacer with Real Results

Today's run on the Bethpage trail

Last February an ignorant orange man told the country that COVID-19 would soon disappear with the heat, "like a miracle." The only miracle is that, seven months later, 42% of the country still believes him. Sadly, we're pretty much where we were the last time I posted (April 28). If there's anything positive I can say about this, it's that on the road things are pretty much the same as they were pre-COVID. Socially distanced outdoor runs don't require runners to wear masks as long as the six foot rule is rigorously maintained. It's really not that hard to do.

It's been about sixteen months since I've had to commute to a job and my time is structured very differently these days. I now get 8 hours sleep every night and my stress level is pretty low. I give a lot of credit to my 6 day a week runs for keeping me healthy. However, I've recently realized that while daily cardio may be great for my vitals and heart health, it doesn't necessarily mean I'm actually in good athletic shape. Can I run five miles without stopping? Yes. Can I run five miles in 42 minutes like I used to? No. Nein. Nyet. 没有.  

During my last checkup in August I asked my doctor why my pace has gone from age group competitive to pathetically slow over the last five years. I'm running a lot more than I was back then and I couldn't understand why all this running wasn't making me any faster. My doctor looked at my chart and said, "Physically there's no reason. You must not be trying hard enough." I knew he was right. I was so inspired that I went out the next morning and did absolutely nothing different because trying was harder than floating through my run.

Since that doctor visit I did try making some changes to my technique that yielded modest speed increases. I focused on cadence and stride length intermittently during runs. The improvement was not dramatic but I did pick up about 30 seconds per mile. Knowing that a little extra effort yielded a marginal performance benefit, I started thinking about ways to really move the needle.

I did a search to see if there was anything online that would inspire me to try harder and I came upon an article about virtual pacers. My old Garmin 210 had alerts that beeped when your pace slowed below a set speed and I was surprised to find a video from DC Rainmaker that showed how to use the virtual pacer feature on my FR35. I had no idea that my watch even had this feature because getting to the menu is not intuitive. But I was able to configure it to beep if my pace went out of range.

Just hit Run > Run Mode > Virtual Pacer > Edit > Set...

My first run was scary because I was so afraid my watch would be beeping like an EKG, with each tone broadcasting my failure to keep on pace. But a funny thing happened. The only time it beeped was to indicate I was ahead or on pace. I was so fearful of the watch's judgement that I ran 1:20 faster than the threshold I'd set. It was like the movie Speed when Sandra Bullock needed to drive over 50 MPH or the bus would blow up. My run was like that but more stressful.

I've been using the virtual pacer (VP) feature on every run I've done since Friday and my pace has been over two minutes per mile faster on each of those runs. The VP is a great motivator but I needed to own the effort. It's a different experience going out with the gas pedal down from start to finish rather than wending my way through my route at a comfortable speed. The sad part is that I'm pushing very hard to run almost three minutes per mile slower than my former everyday running pace.

I'm determined to run 3+ miles at a 9-something pace by the end of the year. I went out to Bethpage this morning to torture myself on the hills and was pleased that I still paced well, even with my bête noire, the big hill that crests near the parking area. If I can keep this up, maybe I can again run alongside the cool kids: SIOR, KWL, Professor Mike and TPP.  Who knew that listening to the doctor could be so helpful!

Pace matters, until it doesn't

Not exactly a blistering pace but I did get a blister.

 Most of 2019 has gone by and we will soon start another new decade. The idea that we will begin our own Roaring Twenties (roaring good or roaring bad? Discuss.) is both exciting and scary. From a running perspective it's an important milestone for this blog which began in the aughts (does anyone actually use that term?) and will, in 18 days, limp gracelessly into its third decade. That's right haters, I'm still standing!

I started blogging in late 2008, around the time that I started running seriously. Seriously did not mean well or fast, but that's when I started. Like most runners, I had simple objectives: run faster and longer. Something about health and piece of mind. But mostly run faster. That was a reasonable goal and I did make progress. Running also led to many great friendships and experiences, blah blah blah. You can read all about them in the almost 2,200 Emerging Runner posts. But let's get back to pace..

No one is ever satisfied with the speed they run. Sure, in the short term, runners celebrate their PRs and PBs. Aside from that, we are always castigating ourselves for falling short of our perceived potential. Don't agree? Tell me how many times you've told yourself that you are so satisfied with your current performance that you wouldn't wish to change a thing. Speed matters, until it doesn't.

When I first began running I had no benchmarks for speed, so I focused on increasing my distance. Running my first non-stop mile was a big deal. My pace at that time was almost inconsequential. I remember someone telling me, "If you run 8:59 a mile or faster you're a runner and if you run 9:00 or more you're a jogger." I took that as gospel and was pleased when I recorded my first run after purchasing a Nike+ foot pod and confirmed I was a runner. I soon dismissed that definition when my results showed I ran in the 9's as often as in the 8s.

I competed in a lot of races between 2009 - 2014 and probably hit my high water mark in 2012. Pace mattered then because PRs and age group podium-ing were both reasonable aspirations. A few things happened after that, including suffering a herniated disc and changing my work commute. This disrupted my workouts and hindered my performance. I watched my pace balloon to the point of near embarrassment. If 9:00 per mile was a jogger, what was I at this point?

I made the decision to stop working in early 2019 and since May I've had much more time to run. Five years ago I probably would have taken this opportunity to run at lots of different places and get back to 6+ mile runs on a regular basis. In reality, I've found it easier to commit to near daily runs by sticking close to home, running 3-4 mile routes in my neighborhood. I'm covering 70-80 miles a month, but my average pace has only improved 4.8% over the last seven months.

Hardly moving the bar on speed was disheartening, and I worried that I had a physical issue that was affecting my pace. My Garmin's heart rate monitor reported some erratic data that was hard to dismiss. I tested its accuracy in a few different ways and moved to a chest strap that showed a more stable range. But still...

Without going through all the details, I had a full day of lab testing -- cardio echo, carotid artery Doppler and even a nuclear stress test (super fun, here's a post I wrote about a prior stress test I did in 2014). I even had a couple of neurological tests for blood flow, just for good measure. The results of all that were clear, I couldn't blame my slow pace on my heart or arterial system.

I was happy to get confirmation from my doctors that I was physically fit, but I felt like I had no excuse for my slowness. I decided I had license to push harder on my runs and there has been a small improvement in my performance. However, it occurred to me that one of the reasons my test results came out so positively is due to the way I run.

I don't look at my pace readout on my Garmin anymore. My objective is primarily to follow my route and enjoy the experience. This seems to be the right thing for me. If I have to choose between healthy, active meditation or a minute per mile improvement, it's hardly a choice.

When it comes to pace, some things are obvious

Dare to believe

Some things are so obvious that we ignore what's right in front of us. I think I may have figured out something that could get me out of the performance stasis that I have struggled with for a very long time.

I've worked hard over the past 3.5 months to get back to my old running self. Since May, I've been consistently running six days a week. This has resulted in a 4X increase in mileage per month compared to what I was doing prior to May. My runs are peaceful, almost meditative. Compared to where I was, this all seems great. But it's not all great.

 According to Garmin Connect, almost every one of my performance metrics are at their lowest points in over a year. Speed, cadence and stride length are down compared to last summer and way down from where they were when I last competed (2014). I know I'm five years older, but I don't accept this level of decline. Some of it may relate to the medication I take, but I'm now rethinking that theory.

Back to the obvious. Most runners who focus on performance understand the basics. The harder the effort, the higher your heart rate. The higher your heart rate, the faster you go. Higher effort yields more steps per minute. A longer stride gets you there faster. So if your average heart rate on a run is 60% of max, your runs will be peaceful and meditative. But your cadence will be low and your pace will be awful.

I've always been a little suspicious of HR monitors because they occasionally give readings that would trigger a trip to the ER if they were real. It's a known issue across all brands, Garmin, Polar, Suunto, etc. I noticed that my heart rate on most runs was pretty low but I chose to believe the monitor wasn't accurate. If I thought about it more, I would have realized that I had fallen into cruise control running and I had no one but myself to blame for my poor pacing.

I decided to run 10 x 160 meter intervals to see if I could match my performance from years ago. I couldn't hit those numbers, but the times were faster than anything I've recorded since 2015. More importantly, my heart rate, cadence and stride length for those ten repeats were strongly correlated to the fast paces. One might say that was an obvious result, but I still didn't connect it to my daily runs.

It wasn't until I started tracking my all-day heart rate that I concluded that the HR monitor was fairly consistent from day to day. I realized that I should believe the readings I was seeing on my run. And if those readings were barely cracking 60% of max HR, I needed to ramp up my effort.

I look good in blue

So I did. Starting Monday, I focused solely on my HR on my runs with a goal of 70-85% max. The results have not been dramatic, but I'm running almost 2 mins per mile faster than I was a week ago. It's no piece of cake and I can feel the effort, but it's tolerable. Per Garmin Connect, my V0₂ max has moved from good to excellent for my age.

My challenge going forward will be to continue pushing on every run in hopes of making a higher HR my new normal. I don't think I'll be getting back to 9:00 paces too soon, but at least I know what I need to do to get there.

When your pace is slow, focus on the statistics

Saw this on a car in the REI parking lot today

Happy Father's Day. My goal of more frequent postings has been stymied (only six this year including today) but I'm definitely on track for running frequency. Over the 44 days since I finished up work on May 3rd, I've run 36 times (82% of days). Just to compare, I only did 33 runs from January 1st through April 30th (28% of days). So run frequency is good. End of statistical report.

June so far - 14 runs in 16 days

It's not all good news in the running department however. The three measures of progress I'm using are frequency, distance and speed. My plan is to meet a target for each point, hold that target and start focusing on the next point. I'm tracking just about 6 runs a week and have started to focus on increasing average distance per run. I'm going in the right direction, but the increase is small, up about 8% from May's average.

The third measure, speed, is my biggest challenge and I have done very little to address it. My pace is abysmal, but I'm hoping that by maintaining high run frequency and increasing distance, my fitness will unlock some of my old speed. I don't like being slow, but forcing my pace turns happy running into a dreaded chore. I guess I could go back to doing intervals which compartmentalize the discomfort. Once I reach my average distance goal, I'll start putting weekly track visits into my schedule.

I've been planning to buy a new hybrid bike to cross train. I'd like to ride some of the great bike trails on Long Island. Two of the other Runsketeers (TPP and KLM) are serious cyclists and I'm pretty sure Professor Mike knows his way around a bike. SIOR has a bike so she has one leg up on me. KLM has been giving me expert advice and will be helping me make a purchase in July. When that happens I'm I'll be looking to do the inaugural Runsketeer ride.

A race happened in the middle of my run

Today's colorful route

Today's run (street): 5.1 miles

For no obvious reason, my performance took a small dip this weekend. I hit my average pace on Friday, but came up about 20 seconds per mile slower yesterday and this morning. Saturday was chilly and the wind made it feel like 35°. I know there were points during the run when running directly into the wind slowed me down. Overall, I felt like I moved along fairly well.

The good news, I guess, is that this 20 second penalty still put me a minute and half per mile faster than my abysmal August average. I had plenty of rest over the last two days so I'm puzzled by these numbers. It's not like I've returned to the "running by rote" style that I'd defaulted to after my lower back disc injury in late 2014. It may simply be a case where some runs just go slower than others.

Setting up for the 5K

This morning's conditions felt a little warmer, but there was still some wind. That made the real feel temperature closer to 41°. I dressed appropriately and felt like I was running okay. I started with a loop around the business park where I noticed a bunch of traffic cones on the road and concluded that the were setting up for a race. It turned out to be the Blue Ribbon Run for Prostate Cancer® 5K that goes through both this business park and Syosset-Woodbury Park. I briefly considered running the race, but I was already a couple of miles into my run.

My route today turned out to be interestingly circuitous. After completing my loop of the park that traced miles 1 and 2 of the 5K course, I ducked into an adjacent neighborhood and ran to Woodbury Road where I picked up the tail end of the Bethpage bike trail. I followed that to Froehlich Farm Boulevard and ran through the office park, where both my dentist and my opioid dealing orthopedist practice. I doubled back along Woodbury Road, through the other half of the neighborhood, and finally back home.

I really pushed on the last mile, but the numbers don't reflect my perceived effort. The important thing was that I tried and my heart rate confirmed that. Garmin Connect showed that my cadence was good, but my stride length was about 10% shorter than where it should be to get the speed I want to run. My dad sent me a link to this video in the NYTimes that looks really interesting. I'll try it and see if it yields any performance benefits. I'm going to skip the barefoot requirement because I'm not Tarahumaran.

Denial of both service and stimulation

Treadmill data more stimulating than treadmill

Today's run (treadmill): 4 miles
Yesterday's run (street): 3.1 miles

This weekend's weather isn't great for running, but I managed to get in a couple of workouts today and Friday. Yesterday my friend and portfolio advisor (Steve) came by for one of our periodic financial reviews. Before we got down to business, we hit my neighborhood roads for a tidy 5K run.

Steve is a Crossfit guy whose workouts focus primarily on strength training and high intensity activities. Cross-fitters incorporate running into their training, but it's typically 400 meter intervals between squats, push ups and other dynamic stationary exercises. I imagine it would be hard to adapt from intensely anaerobic workouts to an aerobic training event like running. Steve said the first mile is always his slowest. I'm guessing that's due to the heavy cardio aspect of running.

Steve and I ran my typical Friday route and the pace we set seemed challenging to us both. We were surprised to discover that our speed did not reflect our perceived efforts. After Gmapping the route, I calculated that we'd averaged about 10:30 a mile. We did talk the entire time and that's an indicator that we weren't pushing all that hard. According to Garmin Connect, I averaged 76% max HR which is about nine percentage points lower than what I've recorded on recent high 9:00 runs.

After Steve and I finished up, I settled into my work, only to discover that my company's email system was down due to the massive DDoS attack on Dyn. That was fine as I had plenty of non-email work to do and, fortunately, our other systems were accessible through the VPN. By 5:00 PM, our mail server started pushing through messages. I caught up with the most important stuff and left the rest for Monday morning.

This morning the weather had taken a turn for the worse. I'm willing to run in sub-optimal conditions but the howling winds, steady rain and chilly temperatures forced me to accept the treadmill as my only real option. My enthusiasm for today's run dropped a few levels, but I dutifully got on board.  I set the speed to 5.6 MPH and edged it up to 6.1 throughout the run. Unlike running outdoors where you can see your progress, the treadmill provides very little sensory stimulation. I spent the entire time thinking about the wonderful moment when I would hit the stop button.

With humidity close to 100%, I felt all used up at the end. I've been hoping for more dramatic improvement in my performance but I'm leveling right now. Still, at this level, I'm running almost a minute per mile faster than I did in September. Yesterday's humidity was 94% and today's was worse, so I'll blame that for not pushing any harder.

I'm excited that I'm going to see the Runsketeers tomorrow. Per my opening reference to the weather, the winds on Sunday are supposed to be fierce, with gusts up to 40 MPH and a real feel in the high 30's. Should be fun.

Back to the track, two years later

Run fast, repeat

Today's run (track): 1 mile warm-up, 1 mile intervals, 1 mile cool down (total 3.1 miles)

Unlike most weekend mornings, I woke up knowing exactly what my workout would be. I knew it had been some time since I did speed work, but it wasn't until I looked at Garmin Connect that I realized I hadn't run a full set of intervals since June 15, 2014. I've been noticeably improving my performance over the past few weeks and I figured doing repeats would be a good way to end a great week of running.

It was cool but humid when I started this morning. I did a mile warm-up at 9:53 and followed that with 10 x 110 and 4 x 125 meter sprints, separated by 30 second rest periods. I'd read that rest time for short intervals should be three times the run duration, but I was impatient. Surprisingly, my speed remained pretty consistent from start to finish, and even improved a little by the end. The other surprise was that my heart rate stayed at around 77% max while running. I would have expected it to spike a lot higher.

After I finished my speed work, I thought my cool down would feel easy. That was not the case, although it started feeling easier by lap two. I ran the last mile at 10:27 which was faster than it felt. I'd averaged 6:32 for the interval mile.

I was fortunate to be home for three days last week and got in six total workouts. I always perform better when I run with greater frequency. I'm concerned that I'll fall back to three to four workouts a week. In any case, I'm hoping I'll be able to hold the gains I've made this week.

Breaking the nine minute ceiling

Can you tell I ran faster?

Today's run (street): 3.2 miles
Monday's run (street): 3.25 miles

Two very different holidays this week provided me opportunities for weekday runs. My company was closed for Columbus day so I had a nice three day weekend and was able to fit in an extra workout. I took advantage of being home and accompanied my daughter to her college to hang out before her classes started. It was great spending time with my her. Even with that, I got home early enough to get out for a run before 8:30.

Conditions were chilly, 50° with 14 MPH winds, making it feel like low 40's. With those strong winds, I kept my expectations moderate, but I found the conditions energizing. I haven't radically changed my approach to my running, but I'm increasing my effort a lot more right now. Over the past few years I've slipped into an easy running style. Some of this was due to carrying extra weight, making any level of effort feel hard. I'm now at the same weight that I was when I was running faster. There's definitely a correlation between weight and performance.

I finished my run and calculated my true pace (elapsed time and Gmap'd distance) and saw that I'd averaged 10:08 per mile. On many people's scale that might look slow, but for me it was a big improvement over where I was a month ago. My goal right now is to run consistently in the 9's (9:59 is okay) but according to Garmin Connect, I haven't broken 10 minutes on a run since December 2014. That was the Jingle All the Way 5K that I ran shortly before I suffered a herniated disc.

Today was a different holiday, Yom Kippur. This is a day when the observant fast and atone and the non-observant think about life and get in a few miles. I didn't go out with expectations of speed and would have been glad just to come close to Monday's pace. The weather was cool but a little humid (87%) and I gave no thought to my performance until I came through my first mile a few ticks over ten minutes. That made me think I had a real chance of breaking the 9:00 ceiling.

I maintained this level of effort and noticed that my heart rate was still at 75% of max so I stepped it up to 81% through the second mile and did the last mile (my fastest) at 86%. The highest I got was 88% so I know I have  more to draw on. I ended up breaking into the 9 minute range on this run, with an overall pace of 9:48.

I'm going to try to consistently hit high 9's before I start thinking about even greater performance. Getting in some extra runs and miles has helped. My biggest challenge right now is to keep that going. Tomorrow Adventure Girl and I will do a trail run near my office. I can't remember the last time we ran together, but it's been years. Me and my family are excited to see her and catch up on her wild life in Montana. AG taught me almost everything I needed to know about running when I took it up in 2008. I look forward to more lessons tomorrow.

Good running beats treadmill tedium

Oh, hello deer

Today's run (treadmill): 4.1 miles

Mother nature can be thoughtless when it comes to my running preferences. I woke up this morning to driving rain that wouldn't stop no matter how many times I looked out the window. Once I started to believe the weather reports, it became clear that my only option would be to run inside on the treadmill. I really didn't want to do that, and thought one more time about braving the rain and the accompanying high winds. Ultimately, I decided that running outside in those conditions while wearing glasses would not work too well.

I stalled as long as I could by setting up the floor fan and gearing up for my treadmill session. As I did all that, I thought about the performance gains I've made in recent weeks and hoped they would translate to this type of workout. I finally hit the start button and set my speed to what I averaged for pace on yesterday's outdoor run.

I know I keep mentioning the Garmin FR 35, but that's because it surprises me (in a good way) every time I use it. This morning I selected "indoor run" and hit start. Once I got going, I saw that it was tracking my pace and distance (and of course heart rate). That's a huge upgrade from my old FR 210 that required a foot pod to capture any run data. As I went along, I compared my speed and distance between the treadmill and watch display that were roughly equivalent.

The tedium of the treadmill experience motivated me to dial up my speed throughout my run. I ended up pacing only 19 seconds per mile slower than my next big performance target. I would have hit that had I done today's run one minute faster. Still, it was my fastest pace on the treadmill since I ran intervals on it earlier this year. My cadence and stride length were also captured and showed improvement from yesterday.

Later in the day, the ER family went out to lunch and then stopped into Dick's in Mellvile. This store has just doubled in size with the addition of a Field & Stream store. My efforts to find some decent lightweight track pants went nowhere (and by the way Dick's, have you heard of any other clothing brands besides Nike, Under Armor and Adidas?) but it was fun to explore the adjacent Field & Stream store.

I don't do guns and have only fished a few times, so I wasn't interested in any of that stuff. However, the outdoor clothing was fun to look at and I always want to buy one of those Carhartt heavy duty hooded sweatshirts when I see them. The showroom had a big display with a bunch of real (stuffed) animals, including elk, moose, wild turkeys and this caribou (see picture at the top) that took a selfie with me.

Tomorrow is Columbus day and that will give me another weekend day to get in a run. There's no rain expected for tomorrow, so I'll be doing that outside. Today's treadmill experience was mostly positive and I was pleased with my performance. But ten times out of ten, I'd rather run outside.

Performance gains from running by heart

Getting to the heart of the matter

Today's run (street): 4.4 miles
Yesterday's run (street): 3.2 miles
Monday's run (street): 2.1 miles
Sunday's run (Bethpage bike trail): 4.2 miles

I've been doing more running than blogging these days, with four workouts since my last post. Every time I've gone out since last weekend, I quietly thank KWL for sending me my FR35. While I have made stamina gains resulting from cutting out most processed sugar in my diet (and losing a few pounds in the process), it hadn't done much for my performance. The FR35 has been a real catalyst for some measurable gains in that area. So thank you once again KWL.

Last Sunday I went to Bethpage to run the bike trail and ended up covering a little more than 4 miles. I ran it about 9% faster than my average pace over the past six months. Having my heart rate showing in real time helped me apply more effort that resulted in better performance. I respond to HR feedback positively, while tracking pace tends to discourage me.

I went home from work early on Monday and went out for a rare afternoon run. It was only two miles, but it was the fastest two miles I've run all year. Yesterday morning I did my usual Friday route. I didn't get around as fast as I had on my prior three runs, but it was fast compared to a couple of weeks ago.

This morning I aimed for a little more distance and headed out with performance running on my mind. Performance is relative of course, but my perceived exertion matched the 80%-92% max HR that my Garmin recorded. I ended up pacing around my new average, but I'd hoped for more.

In terms of performance, I'm still 5% slower than the top end of my current target and I'm 10% away from where I really want to be. More significantly, I'm running 30 seconds to a minute per mile faster than just a few weeks ago. When I get to the pace range I'm aiming for, I'll consider racing again.

Labor Day running and waiting for Hermine

Just keep heading east

Today's run (street): 3.8 miles
Yesterday's run (street): 5.1 miles

Happy Labor Day! After experiencing Irene and Sandy, we Long Islanders take tropical storm warnings pretty seriously. Since Friday, we've been planning for disaster and doing things like moving outdoor furniture and pool toys into the storage shed. The Nassau County Office of Emergency Management has broadcast messages warning people to take precautions due to anticipated 55+ MPH winds and flooding. Happily, the storm has taken a more eastern direction that will (hopefully) minimize impact. That said, we could still get rocked with strong winds tonight.

By Saturday morning I'd expected the rest of the weekend to be a washout. I resigned myself to a few boring treadmill runs and was really happy to see clear skies on Sunday morning. I didn't get out until about 8:00 AM, but the 66° weather and 8 MPH breeze made for pleasant conditions. My prior two runs were three milers, so I felt like I should add some distance. I came up with a route that had me going around the neighborhood and through some roads that I don't normally follow.

Since my Garmin's strap separated from the watch, I've been hanging it off my SPIbelt. Without easy access to the watch's display, I have to estimate how far I've ran. Occasionally I'll hear the chirp notifying me that I've passed another mile. Most of the time I'm just guessing. I've probably done over 1,300 runs around my neighborhood over the last 7 years, so my guessing is usually pretty accurate.

Sunday: 5.1 miles by pure guestimation

I'd hoped to get out for 5 miles on Sunday. I ended up running 5.1 without looking once at my watch display. This morning I had no route plan or targeted distance. The skies were gray and conditions were cool and breezy. Once I got going, I decided I'd run about four miles, but I actually did 3.8. I could have restarted the watch and run the extra fifth of a mile, but I'd really poured it on towards the end and was happy with my results.

Monday: lower for distance, higher for speed

Although the temperature was 64° with a 13 MPH wind, I felt a lot of humidity. That could have been due to running the last mile at 9:15. While that may not sound very impressive, it's a pace I haven't run in a very long time. If I do end up getting a new Garmin, I will opt for the the FR235 with built-in optical heart rate monitor. Having that real-time feedback will force me to pay attention to my training zones and will hopefully ease me back to performance running.

The data behind the pace

Open the stride and quicken the cadence

Today's run (street): 5.5 miles

Conditions were chilly this morning and I had to dress like I was going out for a winter run. I feel like it's payback for all those weeks of unseasonably warm weather that we had in March. Somehow I picked the right combination of gear and set out for a run in a nearby neighborhood. I started out with a loop around a local business park that has one hill that I always dread. I did another half loop before moving on to run in what I call neighborhood #3.

Once around the park

My run was fine and, although I thought I was doing a good job introducing speed at times, I ended up running fairly slowly. When I looked at the data from today's run, I noticed that my current pace hasn't degraded that much since mid-2014. It was interesting to see that my training paces were often 2 minutes per mile slower than my race paces. That gave me hope that I could get back into race shape if I wanted to start focusing on performance.

I decided to do an analysis that compared three data points from my run history: pace, stride length and cadence. I randomly selected thirteen runs between 2013 and today that had data captured via my Garmin foot pod. Pace is measured in xx:xx time format, stride length is typically between .8 and 1.1 meters and cadence usually falls (for me) between 160-180 SPM. Those disparities required me to index the metrics so they could all be displayed on the same scale.

My first reaction when the data was visualized was that faster paces are clearly correlated to longer stride length and faster cadence. Not a surprise. I know that 13 data points doesn't yield statistically significant findings, but it's enough information to be directional. It shows that if I want to get back to 9:30 training paces, I'll need to average between 172-176 SPM and stride lengths between .98 to 1.0 meters.

I have work to do to get to those numbers but at least it's a baseline target. I need to decide whether to focus on cadence and let my stride adapt as needed, or if I should try to open my stride before taking on the tougher metric. I'd prefer the latter, but messing with stride length is tricky because over-striding is the gateway to injury.

Making strides on the track

Part one of today's workout

Today's run (track): 4 miles plus 4 x 200s

My legs exploded off the line, firing my fast twitch muscles and propelling me 200 meters at breakneck speed. That was the experience I was hoping for, but not quite my reality. My plan this morning was to do some speed work so I headed over to the high school to run measured intervals. I did get in some repeats, but most of my workout was track mileage.

When I arrived at the school I was excited to see that I had the place to myself. I decided to take advantage of the clear lanes and do a two mile warm-up before switching to strides. The flat track helped my performance and provided me a half minute per mile improvement over yesterday's pace. I wore my new buff around my neck and pulled it over my head when I encountered strong winds.

The track doesn't provide a lot of visual stimulation, but I liked watching the bright sun coming up over the horizon while I made my way around. I decided to keep running after I'd covered my first two miles and ended up doing a full four before moving over to speed work.

I only ended up doing 4 x 200s with 30 second recoveries, averaging 59 seconds per repeat. Not exactly explosive speed, but I haven't done anaerobic training in a long time. Still, it worked out to 8:00 per mile, a pace I haven't seen for months. If I could sustain that speed for more than 200 meters, I'd be pretty happy. The answer is clearly more intervals, more often,

Marathon day but not a marathon run

I ran 1/6th of this distance today 

Today's run (street): 4.25 miles

After yesterday's horrible run I was a little gun shy about going out again this morning. Daylight Savings Time allowed me to sleep until 6:30 AM and still get up at 5:30 and I was hoping the extra rest would help. I think it did. I told my wife that I was worried about having another bad running experience but she dismissed the thought, saying every run is different. I managed to get out of the house early and my Garmin quickly acquired its signal. I wasted no more time thinking about how I'd feel once I got going.

I usually think out my route and distance before I run. Today I took off in a random direction thinking I'd figure it out as I went. I soon determined that yesterday's struggles wouldn't carry over to today and I focused on getting through the run as quickly as possible. I was anxious to get home so I could watch the NYC marathon coverage on TV and track a number of friends who were running.

I felt much better today and it was enough to improve my overall pace by 42 seconds per mile. There was a pronounced wind that both helped and hurt depending on which direction I was going. The temperature was 59° but I began to feel the heat due to the 72% humidity. I'd paid no attention to my time or distance and thought I'd only gone about 3.5 miles when I got back to my house. I was surprised to see that I'd run more than 4 miles.

It was fun to watch the the coverage of the elite runners when I got back. I had a half dozen people that I wanted to track and I was excited to find that FS was also running when I looked her up. I enjoyed being able to follow people's progress by laptop and wished that the network spent more time covering non-elite participants.

Watching the marathon was fun and I keep waiting for the racing bug to return for me. For now I'm happy to run on my own terms. I'm more interested in training to beat my PB for distance in a single run (13.1 miles) and I plan to start on that next weekend. Once I get my base up, I might be looking at 10Ks a little differently.

Kenyans are faster than my commute

These cars were new when I started my commute

Today's run (street): 3.4 miles

If you took every car on Long Island and laid them end to end, it would stretch all the way to my exit off the Long Island Expressway. That is the reality of my daily commute home. 35 miles in 150 minutes is an average of 14 MPH. An elite runner could run home faster. This is the reason I like Fridays, because working from home saves me one day of all that aggravation.

Last night it took 2 1/2 hours to get from my office to my house. I had every intention of doing a post-work elliptical session, but my night was getting short and I decided to forgo it. Today I had no excuses. I was pleased to see the below 70° temperature and feel the cool dry air when I stepped outside this morning. I felt good from the start and that continued throughout the run.

It's getting close to fall, my favorite running season, and I'm wondering if I'm finally turning the corner on my lethargic performance. Little by little, I've increased my effort on my runs and have started to see incremental improvements to my pace. Today I focused on increasing cadence and a more dynamic leg motion.

The end result was a substantial improvement in my pace compared to a few weeks ago. As impressive as that sounds, I'm still over a minute per mile slower than I was last year. On the other hand, today's pace was half a minute faster than last Sunday. This type of progress is very encouraging. If it continues, I might get fast enough to out run the Expressway traffic.

Happy on the Bethpage trail

Trail appreciation day

Today's run (Bethpage trail): 5.4 miles

The best part of today's run came during the last half mile. I'd spent the previous five moving at my usual pace (slow) but opened up the throttle on the last stretch of the path. I ended up with a final split in the range of my old normal pace. That contrasted with the rest of my data and really highlighted how much my performance has dropped off over the past few years.

I wanted to break out of my typical 3 to 4 mile rut and I knew the best way to do that was to run the Bethpage bike trail. There was partial sun breaking through the clouds and the humidity didn't seem too bad. But humidity can be deceiving and, a few miles in, I began to regret leaving my water bottle in my car. Garmin data says humidity was 83%. On the other hand, there was a steady breeze coming from the west that acted like a cooling fan, especially when I was heading south.

Rather than go north as usual, I decided to run south to Bethpage State Park, turn around there and head north to Old Country Road. I figured that would get me my targeted five and then some. Soon after I'd started, I saw a couple of people running ahead of me at about the same pace that I was running. Well the guy was running my pace and the woman was running faster and looping back periodically to run with him. It reminded me of running with TPP and SIOR!

I eventually caught up to them, but they kept going south while I turned around. I was feeling good and took the time to look around and appreciate how fortunate I am to have this beautiful trail ten minutes from my home. The abundant trees and well maintained paths make it a happy place. I noticed that they've put in water coolers near the end of the first section of the northern path. Very civilized. I wish I'd drank from it when I had the chance.

For some reason, I expected that my run north would feel short because I'd covered 2.75 miles by the time I'd looped back to where I'd started. It wasn't a slog covering the remaining distance, but it seemed to take longer to cover slightly less distance. As it turned out, I went much faster during the second half. That was probably due to my more urgent pace towards the end.

The fact that I could hold a much faster pace for a fairly long stretch reinforced that my speed issue isn't physical. I've definitely fallen into the habit of running comfortably rather than with a performance goal. My absence from racing explains that to some degree. I'm not sure that I want to start folding in faster paces in all my runs, but with cooler weather coming, it might be a nice thing to try.

Finally, I want to give a shout out to SIOR who finished in the top 8% of the Suffolk County Half Marathon this morning. It makes me proud to be a Runsketeer. Even if I'm the slowest one.

Getting my head around running faster

 

Today's run (street): 3.4 miles

I missed my mid week workout and hadn't been on a run since Sunday. Working from home on Fridays provides an opportunity to get in a few miles in the morning. An early business call provided a scheduling challenge. Despite my chronic tendency to procrastinate before running, I managed to get out before 7:00 AM and was rewarded with a cloudy sky that kept the temperature down. The humidity was another story.

My running experiences have gone from being exciting efforts that occasionally produced performance breakthroughs to embarrassingly slow cookie cutter efforts. I've used the excuse that I have to watch my speed to prevent further issues with my lower back. Even I don't buy that anymore. I think it's come down to the fact that I've lost the will and the knack for running fast.

The thing is, I haven't consciously backed off on the throttle. Most of the runs I do today feel as difficult as the ones I did three years ago. The difference between now and then is measured in minutes per mile. Every time I go out for a run, I think about going to the track and running repeats. I don't have any hope of managing 52 second 200's as I've done in the past, but it would be great to break a nine minute mile once in a while.

I keep telling myself that increasing base past 6 miles will make it easier to maintain speed on shorter runs. I know from half marathon training that there's some truth to that. But I haven't felt the motivation to push beyond a certain perceived effort. The mind has to accept the challenge before the body can perform.

Goodbye pain, hello speed

Illustration by Mr. Emerging Runner Jr. 

Today's run (street): 3.9 miles
Yesterday's run (street): 3.6 miles

Happy Mother's Day. We did most of our celebrating yesterday because we had a lot of stuff to do today. That meant family time during the day, followed by an early dinner at our favorite place. This weekend also included a couple of sunny outdoor runs for me that felt close to normal. The gating (or gaiting : ) factor is my stride that feels constrained on my left side. It's causing my left foot to land differently, so that it jams up against the front of my shoe.

Both of my weekend runs were pretty much the same, although they were tougher than they should have been. The issue wasn't my disc problem. Part of it came from an extremely heavy pollen count and high humidity, especially today. I'll also blame the minimal road work I've done over the past couple of months. My street runs are generally longer than the treadmill and elliptical workouts that I've been doing. Plus, these outside runs produce a lot more impact than fitness machines.

The bright spot in today's run happened near the end when I came down a long stretch and saw a couple walking in the distance. I picked up the pace to pass them and held it long enough to determine that I wouldn't cause a relapse of my upper thigh pain. My overall pace for the run was still very slow, but that last quarter mile was in the mid-8:00 range. No pain during or after.

Tomorrow I'll finish up the formal testing of alternative running machines. I want to keep the momentum of weekday workouts after this program finishes. I don't like using the locker room at my company's fitness center, but if I schedule my workouts for the end of the day, I can towel off with gym wipes and then head straight home. That's what I've been doing during this testing period.

Over the weekend, my son created a running graphic for me (above) that looks like some of the artwork I've created for this site. I like his running man (or woman!) and I think he nailed both the concept of running and a forward leaning stance in karate. I haven't had to combine those two things to date, but if I do, I'll have an icon to represent it!

You need to run 600 yards to run a mile

1,800 feet of hell

As far back as elementary school, I've struggled with running fast paces over long distances. I really did try. In fifth grade, I ran the 50 yard dash for the track team and even placed first in my town for the standing broad jump (still the apex of my athletic career). These events were part of the Presidential Physical Fitness test that every kid had to take to pass gym class. Running 150 feet and jumping six feet was relatively easy. It was the 600-yard timed run around the field that haunted me all the way through high school.

I wasn't alone. We all dreaded the “Six Hundred”, a seemingly endless distance. Now that I have some perspective, I realize that 600 yards is a mere third of a mile. One and a half quarter repeats! I actually remember my high school time (2:12, the temperature of boiling water : ) that put me right in the middle of the pack. What was regarded then as a mediocre time actually calculates to a 6:27 pace. If only I had more perspective back in those days. At the time, all I could think about was the painful burning in my throat and the relief that it was finally over.

A recent suggestion by my running and blogging buddy She Is Out Running brought back memories of the Six Hundred. SIOR proposed that she, TPP and I do a timed mile run. I thought that was a great idea. I've come to terms with my race times slipping over the past few years, but I’m still achieving credible times when I do repeats. A mile distance is a great way to see how far I can push my anaerobic capabilities.

Intervals (for most of us) are a combination of short but intense bursts of speed, followed by a similarly short jog or rest. The biggest challenge of running a flat-out mile will be to sustain that intensity for a much longer period. I can go full speed for 200 meters and maintain a 180 SPM cadence through a full quarter. After that I begin to fade. Maybe that was why running the 600 as a sprint was always so difficult.

The fastest mile I can remember running was a 7:51 at Long Beach that led to my 10K PR. I'd started at the front with all the hollow-eyed ectomorphs who took off at the gun like whippets. I was passed by a lot of people and thought I was having an off day. When I saw the Mile 1 timing clock, I realized those speedsters were running six and seven minute miles. So that's why people use pacers!

Maybe speedsters SIOR or TPP can do a pace lap for me when I do my timed mile. I'd return the favor, but I fear my 6:27 days are far behind me.