900 miles is easy but running fast is hard

Hoping for 80 in December

Hello runners and the running adjacent! It's December 10th: the first night of Hanukah, the 12th day of the Advent and, most notably, national Dewey Decimal System Day. 

This is my first after-election post and while I try to stay non-political on this blog, I will say my faith in democracy has been restored by the 81 million people who voted for a return to trust, competence and decency. Let's move on, unify and hope that the next Attorney General puts the current president and his cadre of corrupt criminals in federal prison for a long time. If you don't like what I'm saying here, I invite you to comment below. But please share respectfully and don't put in a link to your stupid product website because I will delete that 🏃

Okay, now onto 2020. The pandemic is getting worse and we are "rounding the corner" into a horrible winter season (see what I did there?). So instead of not running the Seaford Hot Chocolate 5K in Seaford or the Ho-Ho-Ho Holiday run in Bethpage this year, I won't be running the virtual versions of those races. I don't want to race for a couple of reasons. First, I've slowed considerably and I'm self conscious about posting a pathetically weak finish time. Second, I don't really get virtual racing. The best thing about racing is being present with a a bunch of strangers and having the possibility of beating some random person over the line at the last minute. I've done it and I've had it happen to me. I'm talking to you TPP. 

I recently passed the 900 mile mark, my distance goal for 2020. I run between three and four miles every day except Mondays, and I could easily do a virtual 5K or 10K race. A couple of months ago I started looking at my running stats on Garmin Connect that go back to 2009. I saw that I'm running more miles than I ever had in any of the previous ten years. The difference of course is the quality of those miles. Back in 2011 most of my training runs were between 8:45 and 9:30 a mile, my average stride length was about .9 meters and my cadence was around 174. Things have changed.

A few months ago I decided to test the waters and see what would happen if I actually tried when I ran, rather than defaulting to a comfortable pace. Or as someone in the Running Lovers group in LinkedIn put it, "Slow mindful running." Up until that point I figured I'd just drop a couple of gears and roar back to when I was a mid-pack competitor. I set off on my next run with a pedal to the floor mindset, finished my run and checked my watch. Once my heart rate fell below the point where "vagal maneuvers" would be required, I saw the data.

I was nowhere near my past performance benchmarks but I did see a marked improvement against my running average. Yes, that's a pun. Subsequent runs at vagal imperiling speed brought marginal improvement. I started doing weekly speedwork hoping to unleash a little more speed but I finally reached my performance limit. I realized that in order to move to the next level, I would need to train longer and even harder. I'd have to do regular hill training, long distance runs and maybe even core work. I thought about it and decided to focus on holding the gains I'd recently made.

So now I go out and push myself a little harder than I had prior to this performance focus. I rate my  perceived effort for each run on Connect and most of the time it's between moderate (3) and hard (6). The scale goes to 10. Every once in a while I push myself to very hard (7) and my numbers reflect it. While it's nice to see the mirage of higher performance, it comes at the cost of pain and discomfort. If every run required a "no pain, no gain" mindset, I don't think it would be worth doing. Speed is a nice to have, but it isn't everything.

If you disagree please feel free to comment below 👇 

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 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.

Low volume this week but a decent run today

At least I didn't skip today

Today's run (street): 4.3 miles
Friday's run (street): 3.2 miles
Last Sunday's run (street): 3.2 miles

This has not been a good week for my running. I'm at that point in the year where business activity peaks for a few intense weeks in December before going quiet as everyone shifts into holiday mode. That's meant longer days and less inclination to work out when I get home. I know I should try to run a couple of miles in the morning before I start my day, but I can't get into that mode right now. Making things worse this week was a Saturday schedule that had me out the door before 6:00 AM. That kept me busy the rest of the day, so no Saturday run this week.

I did run on Friday and it was fine, but slower than I've been averaging. I don't know if it was due to my busy work schedule, but I felt tired throughout the run. I had no time to get out before my early start yesterday and thought I'd go for a late afternoon run when I got home. I ended up feeling too tired to run, but I did do a long neighborhood walk and ended up with over 10K steps for the day.

I turned in early last night and got a rare 8 hours of sleep. Even so, my energy level was low when I got up. After a small breakfast and a big cup of coffee I was feeling more energetic. I put on my new ASICS Men's Essential Pants that I got for a great price from Running Warehouse. The weight of these pants is lighter than my beloved City Sports track pants, but perfect for this morning's 39° weather. I added my ASICS thermal beanie and a winter weight half zip and my Balston wool socks. I looked in the mirror and realized I was head to toe in black like a very slow ninja.

I've lost a little speed over the past few weeks and I'm pacing about 5% slower than I had throughout November. My cadence hasn't dropped but my stride length has shortened a bit. I'm not too concerned about that. My heart rate has been averaging about 75% of max so I should be pushing harder. My running hasn't felt particularly easy so perceived effort is obviously higher than my real effort.

Today's runaround

Today's run was a meandering tour of my neighborhood. I enjoyed looking at the holiday decorations and laughed at the deflated Santas, snowmen, reindeer and elves laying across lawns, waiting to be filled with air after the sun goes down. There were a few hardy souls out walking their dogs, some walkers and a runner who suddenly appeared from a side road. I came close to overtaking him but he split to the left while I continued heading right.

I wanted to cover at least four miles and managed a little more than that. I did step up my pace as I got closer to home and proved to myself that I could move back into target range if I was willing to maintain the intensity. At this point I'm still running better than I have over the past two years but I need to decide how hard I'm willing to work to continue improving. The Runsketeers had planned to run a 5K on Saturday until we encountered scheduling conflicts. I didn't feel ready to race this weekend so it's probably for the best.

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.

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.

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.

The two dimensions of running speed

Sample combinations

Today's run (street): 3.4 miles

I was looking at the metrics of today's run on Garmin Connect and thinking about the factors that determine pace. I recently put a new battery into my foot pod so I can capture my cadence as well as time, pace, heart rate and elevation. Besides steps per minute (SPM), the foot pod also shows average stride length. After looking at new and past data, I'm seeing some correlation to pace.

When you think about it, running speed is controlled by two factors -- how far you are propelled with each step and the frequency of these steps. As an example, last year I ran the Hot Chocolate 5K averaging 178 SPM, but with an average stride length of 1.03 meters. That translated to an 8:46 pace. A month later I did the LIRCC Hangover Run averaging 172 SPM and .95 meter stride length and averaged 9:50. Fairly small differences translated into almost a minute difference in pace.

Interestingly, my data shows when I run intervals, my stride length drops to half a meter. However, average cadence jumps up to 188. That usually results in an 8:00 pace or better. I've read that, to improve performance, increasing cadence is a better approach than increasing stride length. I'm sure that's due to the danger of over striding which can put excessive pressure on the knees, tendons and ligaments.

Today both my cadence and stride length were middling and I ended up pacing in the mid 10's. That was by design as I wanted to minimize wear and tear on the muscles that may be aggravating my sciatica. Once I'm past this annoyance I'll start playing more with cadence and will try to make my way to the ideal (180 SPM). I'd like to run some intervals this week get that started, but I want to make sure I don't do more harm than good.

Hope for the Warriors, but not for my speed

Flag dedication at Hope for Warriors race

Today's run (street): 5.4 miles

This morning was spent at the Hope for the Warriors race in Lindenhurst, NY. For the first time in four years, I didn't participate, but I came to support my family who served again as race volunteers. Last year my wife and kids manned the registration desk while I ran the 10K race. I decided to skip the race this time, for the same reason I missed the 2014 Dirty Sock, Cow Harbor and TOB Supervisor's run. I've lost interest in competing.

I don't know exactly why the thrill of racing is no longer there for me. I used to love the experience of training for a race and reaching the point where I knew I could hold my own. Between 2009-2012, I generally finished in the top 25-30% of the field in 5Ks and usually in the top 50% at other distances. My performance has been steadily slipping since then. It's hard to get motivated to race under those circumstances.

The frustrating thing about it is that I can still run fast when I really try, but it takes much more effort than it used to. I'm sure my speed decline is partially due to training easier than in the past. When I was commuting into the city I would get up and run at 4:00 AM just about every day. Those runs focused on speed for practical purposes. I had only so much time to run my route so that I stayed on schedule to make my early train.

My weekly volume at that time was about 20 miles a week and I would regularly break 9 minutes a mile. Today, I am covering 15-20% less distance per week and 60% of that is done as longer, slower runs. Except for those rare times when I do a speed workout, I haven't broken 9:00 per mile in over a year.

Today, after we'd returned home from the race, I did a neighborhood run and pushed especially hard on my last mile. My split was 9:37 and it felt like I was running at 5K pace. In fact, 9:37 was my pace at my last 5K.

Due to the earlier activity, I didn't get out for my run until 10:30 AM this morning. While I ran, I thought about the experience of being at the race but not participating. At one point, three young guys had walked by me talking about the 5K they were about to run. I'd forgotten the 5K race was an option and, for a second, I regretted that I didn't just sign up for that.

Being among the runners this morning did not rekindle my excitement for racing as I'd hoped, but it did motivate me to try to train a little harder so I could put in a credible performance in a 5K before year's end. It's been a lot of months since I ran the Brooklyn Half, which is the last race I've run in 2014.

Congrats to TPP, who absolutely rocked it at Hope for the Warriors today, attaining a 10K PR and (yet another) age group placement!

Good with my running right now

Give me a Boost?

Tuesday's run (treadmill): 2.3 miles
Today's run (street): 4.3 miles

Happy Labor Day weekend. It's been a busy week, but I was able to get in a treadmill run on Tuesday. But after a long day at the office on Wednesday, I was in no shape for a Thursday run. That leads me to this morning, when I went out for a pleasant neighborhood run before starting a busy (though holiday-truncated) day working from home.

Conditions were superb at 7:00 AM - 60° and not very humid. With the sun still low in the sky, it felt a lot like fall. Friday morning I'd driven through Bayville and Seacliff and counted at least a dozen runners along the way. I envied their freedom as I made my way towards the Cross Island Parkway on the way to work. I appreciated that today I got to be one of the people running.

I covered no new ground on today's route, but still enjoyed the experience. I thought about my current state of running, definitely slower than it was a year ago. I usually beat myself up at the beginning of each run, thinking about this difference. Am I not trying as hard as I used to? The effort feels the same, even if the speed has dropped. After going through both a stress test and physical that revealed no underlying issues, I don't have much to blame it on besides age.

I decided today not to care. I'm not interested in competing right now, so speed isn't that important. I'd like to get back to my previous level of performance and I think I can if I focus seriously on speed. Right now, I like my running for what it is -- a way to maintain mental and physical fitness. I ended up running a little faster today than I have in recent weeks. I attribute that to the cool weather and a good night's sleep.

I cut my day short since the office closed early for the holiday. The Emerging Runner family went out to finish our back to school shopping. We stopped into Dick's and I tried on a pair of adidas Boost Response trainers. I've been curious about these shoes because they have adidas' Boost foam that supposedly returns 30% more energy than EVA.

The fit was great and the shoe had a nice rocking effect that facilitated a rolling gait. I'm not quite ready to replace my Virattas at this point, so I put the shoes back on the shelf. In a few months I'll be looking more seriously and will give them another go.

Great weekend runs despite the hills and rain

Today's run (street): 5.2 miles
Yesterday's run (Bethpage trail): 6.25 miles

It's been a good weekend for running, starting with Friday's morning's fall-like conditions. Yesterday I decided to break out of my neighborhood's boundaries and headed to Bethpage to run the bike trail. It was a little warmer than on Friday, but very comfortable in the shade. I got a late start and didn't arrive until 9:00 AM, and the trail was packed with happy looking cyclists, runners and walkers. I picked the northern direction, running towards Sunnyside Boulevard.

It's been some weeks since I've run the undulating hills at Bethpage and I felt every one. The stretch between Washington Ave and Sunnyside was the toughest section of my route and I felt some relief once I reached the top of the last hill. The rest of the run was easy and I was almost sorry to stop when I reached my endpoint.

Later in the day we hosted a dinner for friends and, by the end of the evening, I was ready to sleep where I stood. I worried that I overdid it on my run and that I wouldn't be able to go long today. I ended up getting an earlier start this morning and took off under dark cloudy skies. Around the two mile point it started to rain, and I thought about turning back home. I decided to keep going in the hope that it would soon clear up.

My gamble paid off, and the rain stopped about ten minutes later. I ran another 20 minutes before completing 5.25 miles. Running only four times a week (these days) requires that I cover at least ten miles on weekends. Less days mean longer distances per run, and his has helped me establish a pretty good base. My speed is still well below target and I think that's due to an utter lack of anaerobic training on my part. I plan for a speed workout some time next week and try to get  that back on track.

The paradox of high humidity and faster running

Part of today's route. Pretty. Humid.

Today's run (street): 4.5 miles

Happy 7th of July. For some reason, the company I work for has made both the 4th of July and today company holidays. That, plus working from home last Thursday, allowed me to run for five consecutive days. Counting this morning, I've covered 21 miles in that period. I wish I could do that every week.

Even though I was up before 6:00 AM today, I managed to squander the early hours and didn't start my run until a little after 8:00 AM. When I stepped outside it didn't seem all that humid. There was a slight breeze from the north that combined with the mid-70's temperature, creating what seemed to be comfortable conditions. That was an illusion.

The neighborhood looked very nice under sunny skies and the first mile of my route was fairly shady. From then on, the temperature seemed to rise by the minute, along with the humidity. I mixed up my route in an attempt to break the boredom of my local streets and found myself running up what passes for a long hill in my neighborhood. Between the treeless road and the thickening air, I moved into direct drive mode. That's when I put all resources toward getting through the distance.

I often forget that when I put a little more power into my stride, my running efficiency (speed benefit as a function of expended energy) increases. This is the trick I occasionally use when a faster runner begins to overtake me in the neighborhood or on the Bethpage trail. By lengthening my stride and increasing cadence a little, I can lower my pace by a mile per minute for short periods without feeling like I'm working that much harder. 

About half the time I can hold back speedy challengers until one of us turns off to another road. Running harder, despite the humidity, helped get me to the 4 mile mark faster than I expected. The only issue is that I usually reach a point where I can no longer sustain the greater speed. Fortunately, I was able to maintain the pace and I even took it up a gear for the final 200 meters.

When I went inside to cool off before my shower, I realized that my level of sweat was equivalent to having jumped into the pool. In fact my running clothes looked like I had just done that. I have a different schedule this week that will involve some travel, so I don't know when I'll get a chance to run again before the weekend. If the timing works out favorably, I may be able to fit in a couple of mid week runs.

Addressing my need for more speed

My experience today

Today's run (street): 5.1 miles

I'm back into a three day running cycle and I ran in the neighborhood yesterday and today. My morning schedule was tight, so I needed to get outside early. Fortunately, it was still relatively cool and (bonus) not as humid as Friday. I had no route or distance in mind, but I did want to cover at least five miles.

Like yesterday, I started with good energy and tried to establish a faster pace from the start. It seemed a lot faster than it was. I still find it curious that putting in the same effort compared to a year ago will typically yield a 30 sec/mile slower pace. I'm not planning on doing any races before Dirty Sock, so I'm not really upset about that. Still, I'd like to gain that time back if I can.

Tomorrow the Runsketeers will get together for our first group track workout. I look forward to seeing how fast these two speedsters can run when they don't need to reserve energy. I'm not going to be able to cover as much distance tomorrow as I would on a typical Sunday, so this week's mileage total will be extra low. But track miles are quality miles. If I can figure out a way to add one more workout a week to my running schedule, I can get back to pre-commuting weekly volumes.

Not a step back, but not what you'd call progress

Disappointing cadence

Today's run (street): 4.6 miles

I wasn't sure what to expect on today's run but I hoped I would find it easier to reach my targeted performance numbers after seeing some improvement yesterday. To my dismay, I felt less energy this morning and I hoped that I'd rebound during the run. Although I did quickly get into rhythm, I found even the first couple of miles difficult. I wasn't sure if I'd started too fast, or if I was simply too tired.

I've read numerous times that an ideal (non-competitive) pace will allow a runner to maintain a conversation while still providing some level of challenge. For most people, that's 75-85% of max heart rate. A check of the data from today's run showed that I stayed primarily between 76 and 79% of max for the first 3.75 miles. Even though I was primarily at the lower end of the HR scale, the going felt difficult.

My response was to pick up the pace and, for the last 3/4 of a mile, I kept heart rate between 80-86% of max. In terms of technique, I adopted an almost bouncing stride that I hoped would translate to greater speed. It did, but it still fell short of today's expectations. My cadence, even after using my new form, never got out of the middling range. The one upside is that getting my HR into the higher 80% range is good preparation for harder workouts.

I don't know if I can return to doing 8:00 minute range training paces, but even if I can't, I still have lots of room for improvement.

And all this time I thought I was running!

 It's official!

This past Sunday I wrote a post about my declining pace performance. I showed a graph with speeds in MPH based on GPS watch data. My Garmin often under-counts my distance, so the speeds on the graph are probably 3.2-4% slower than my actual average speed. I was a little surprised to see a comment that seemed targeted to the lowest pace on my graph. The comment said, "The official name of anything below 5.5 is 'walking.'''

This is good to know, because all this time when I was running 10-something paces for ten or more miles on the Bethpage trail, I thought I was actually running. But what about those race-walkers that reach paces in the 6:00/mile range? Very confusing. Technically, I believe it is considered running when both feet leave the ground, versus walking, where one foot always remains on the ground.

I know this commenter was just being sarcastic (if a little mean). Perhaps he/she can clear up some other questions for me, such as, "What's the official difference between rapping and singing?" In the meantime, I'm declaring anyone who calls themselves a runner to be one. And no matter what speed they actually run, it's still running.

The history of my running speed

Directional declines

Today's run (street): 3.6 miles

I decided to do some data mining on Garmin Connect to compare my historical averages with my current performance. In order to keep the information consistent, I only used data captured from one source, my Garmin 210 that I bought in 2010. I know I've lost a lot of speed over the past year and my interest was in seeing whether my recent history is an aberration, or if it merely reflects a long term decline.

Charting the trends reveals a changing relationship between race speed and overall speed. My average pace has followed a linear decline, but my race paces have dropped measurably since 2012. Up to 2012, I generally paced 7.5% better in races compared to my overall average. After 2012, that gap has closed and is now almost equal to my training run times.

As I often say when working with business data, these findings are only directional. The Garmin data, acquired by GPS, has a variable margin of error. I tried to correct for that as much as I could, but the numbers do have some skew. I only selected runs I'd tagged as "street running" to filter out slower trail paces and faster track paces. It's also important to note that the 2014 data is only through May 25, not a full year.

In terms of these findings, I'm not happy to see declines, but at least the drop-off has not been as sharp as I'd suspected. I did today's run as a tempo, taking it easy through the majority of the distance and picking up the pace more at the end. The last mile was a minute faster than the prior few, and I finished feeling great. I wish I could tap into that speed more often, but based on my recent race performances, it's a little more complicated than just trying a little harder.

The elusive convergence of speed and distance

 

Today's run (street): 6.4 miles

I was channeling Chicken Little yesterday as I made my way through my 4:00 AM run. All the hard training I've done up to this point seemed to be for naught and I struggled to get through 25 minutes of moderately paced treadmill running. Some of that was likely due to the very early hour and fatigue from my abrupt change in daily routine. Today's run was far longer, and much better than yesterday's, but it wasn't particularly fast.

My new work engagement provides a lot of scheduling flexibility and today I was able to work from my home office. That let me fit in a medium length base run and cover my longest distance since last Friday's 9.7 miles. This spring weather is puzzling, but I won't complain because there's no snow on the roads and temperatures haven't yet reached oppressive levels. However, my decision to wear shorts and short sleeves made me feel chilly throughout much of today's run.

I was concerned that I'd suddenly lost some endurance, but I could tell from the first few steps off my driveway that I would easily cover my targeted miles. That was good news. What isn't so good is that once I go beyond 85% of HR max, my stamina starts to slip. I can handle endurance or speed, but not both together. With only a couple of weeks until the Brooklyn half, I should be farther along in terms of performance. I don't expect to PR on the 17th, and I'm not even confident that I can break 2:10. I'm going to continue to focus on base because, while speed is desirable, endurance is what gets us over the finish line.