Effortless Thanksgiving run, but not in a good way

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

Happy Thanksgiving! I worked from home yesterday and have been feeling the holiday spirit since wrapping up work on Wednesday afternoon. SIOR is shaming encouraging everyone to do the Thanksgiving to New Year's streak that involves running at least a mile every day. So far, I'm good. I even ran yesterday, and I'm wondering if I can apply that to a day during the streak when I can't run.

Yesterday's run was fairly textbook. Usual route, usual pace. I'm hard pressed to recall anything interesting about it except that the roads were almost completely free of cars. Neighborhood running is much better when schools are out. No buses or parents doing drop offs. I enjoyed having the streets to myself.

During that run, my heart rate was hovering around 75% of max, which did not match my harder perceived effort. I found it interesting that I matched my usual pace with a 6% lower heart rate. Is that an indicator of improved fitness? If so, then why did it feel so challenging?

If you look carefully, today's route resembles a turkey

This morning I went out fairly early when the real feel temperature was 31°. I wore two top layers and track pants. At the last minute I added a fleece vest. That helped a lot, because running directly into the wind was pretty unpleasant. I originally thought about going to the track this morning but decided that a Thanksgiving run should happen closer to home. I chose a different route than normal and looked forward to another traffic free experience.

Like Wednesday, my perceived effort on today's run was greater than my actual heart rate indicated. I was puzzled to see that the Garmin showed my HR at around 71% of max. I felt like I was working a lot harder than that, closer to 80% range. By the time I finished, I'd managed to push it to 79%. My pace confirmed the data and I saw that I ran 50 seconds per mile slower than yesterday.

I'm not sure why my running is feeling a little tough right now. Last night we went out to dinner and saw a good friend. It was a big meal and maybe that bogged me down a bit this morning. If that's all it takes, tomorrow should be more of the same. We had quite the Thanksgiving feast today, put together with the team of Mrs ER and ER daughter. Feeling sleepy now, but I'm sure I'll get my second wind soon.

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.

Perceived effort was not enough

 

Today's run (street): 4.6 miles

Yesterday's run in Old Westbury provided a great hill workout. Today I thought I'd keep it simple and keep my running to my local roads. It wasn't as cold as Saturday, but it was still pretty chilly. I wore the Opedix again, along with three top layers. It wasn't until I took my first steps off the driveway that I knew my legs had recovered well. I had high hopes for a performance improvement and I sure gave it a try.

After we finished preparing for our runs this morning, my wife said, "Okay, let's get our runs on!" We were both ready to get going - she to the treadmill and me to the street. I was psyched knowing that I would be dealing with less distance and lower elevation today. My plan was a four mile run with negative splits.

The temperature was 35° and there wasn't much wind. I was comfortable in my gear and I felt good from the start. I'd left my HRM home and though I had my Garmin, I decided to run by feel instead. The first mile went by quickly and I was convinced that I was beating Friday's moderately brisk pace. I avoided looking at the readout on my watch because I didn't want to be discouraged, or overly encouraged, by what I saw.

I'd started around 7:30 AM and there were few cars or people around, although I kept crossing paths with two other runners. I felt like I was moving a lot faster than yesterday and was hoping to finish with a big surprise in terms of time and pace. I was surprised, but not in a good way, Running by feel did not generate the speed I'd hoped for. I did achieve negative splits, but my pace was 30 seconds off of Friday's.

On the positive side, I put in almost 20 miles this week, had some good workouts and got to run and hang with my friends. I'll take that over performance anytime.

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.

It's JavaScript's fault that I ran slow

What I've been staring at 

Today's run (street): 3.2 miles

I have a consulting practice that focuses on digital media business and technology. I'm in the process of expanding my portfolio of services. That involves including more strategic partners and re-branding my website. I'm spending time on the development site whenever I can fit it in. Although I get input from my partners, I'm handling both the web design and the technology. This is fun for me, but staring at HTML and JavaScript code for hours really wears me out.

I'm hoping that will explain the gap between my perceived effort (PE) on today's run and my actual performance. I didn't expect to see impressive numbers when I checked my Garmin after my run, but I ended up running over a minute slower than how the run felt. It was a more challenging workout than I'd anticipated. It was also a sign that I haven't gained back as much speed as I hoped I would by now.

It was interesting to see that the Garmin data showed that my average cadence was up measurably, compared to my last few runs (174 vs. 168 SPM). So my turnover was good. Had I opened up my stride a little more, my pace time would have likely reflected my PE. It's something to think about on my next run. But I won't be thinking about it until Saturday, because Hal gives me a rest day tomorrow. Great, more time to code my site.

A little snow can't stop a run

My view from the treadmill

Today's run (treadmill): 3.3 miles

This is the season for snow, although we really haven't seen too much this year. We knew we'd see some snow today and I planned to get outside before things got out of hand. My schedule was tight with some deadlines looming. By the time I was ready to run, there was a coating of snow on the road and I opted for the treadmill.

I hadn't run since Sunday when I went out for an easy four miles to recover from Saturday's race. The treadmill is my least favorite workout but I knew I had to step it up today. I decided to start fast and see how long I could sustain it. I was surprised how easy it felt and wondered if my legs were still tuned for racing speed.

Even with the TV to distract me, the run became increasingly tedious as time went on. My perception of easy running gave way to wishing I could get off the treadmill. I helped things along by increasing my speed for the last five minutes. It was a good run and a fairly hard effort. By the time I finished there were at least two inches of snow on the ground. With lots to do on Wednesday, I'm not sure if I'll have time to run tomorrow. I'm glad I got in a decent run today, even if was on the dreaded treadmill.

Is 93% of max the magic number?

Not far from 180spm, so where's the speed?

Today's run (street): 3.5 miles

I'm a little disappointed with today's run because I could not generate any speed. Despite clocking my first mile in 8:57 (easy for many, but hard for me lately), I ended up averaging an unremarkable 9:29 pace over 3.5 miles. After a good start, I'd lost time on mile 2 and then tried to make up for it over the last 1.5. I felt like I'd made a good effort, but according to Garmin Connect, my heart rate across the whole run ranged only between 77-85% of max.

I took a look at my race history and compared my pace performance with my average heart rate. Since I've only run about a dozen races using a heart monitor, this wasn't a statistically significant representation. Directionally, it seemed to indicate that my best times happened when my heart rate averaged 93% of max HR or greater.

Does this mean that I'm somehow holding back, even as I work to push my speed during a run? The numbers seem to point to an opportunity to unlock some speed by adding even more effort. My cadence rate has actually improved over the 5+ years since I've starting daily running, but that hasn't translated to speed. I will do my best to hold the effort on Saturday. I'm not asking for much, but beating 27:50 would be nice.

Alarming morning affects my run

Rude awakening

Today's run (street): 3.2 miles

This morning's fun started early. It was 2:39 AM to be exact. That was when we were woken up by an incessant beeping. It turned out that our alarm system was signaling that the backup battery was low. Apparently our street had lost power some time earlier. After a bleary-eyed call to LIPA's outrage line (that was a typo but I'm leaving it in), we went back to sleep, only to be awoken around 5:00 AM when the power came back and reactivated the alarm.

We had overnight guests down the hall and thankfully they slept through the craziness. Since I was up early, I decided to go out for my run sooner than I normally would. The skies were overcast, but there didn't appear to be any rainclouds in sight. I went out fairly fast (at least it felt that way) and hoped I could carry that urgency through my full distance.

My effort seemed moderately high and I tried to maintain a steady cadence. A check of my heart rate around mile 2 showed that I was 8 BPM below where I wanted to be. I hoped that was due to improved conditioning, but it was probably a case of perceived effort not matching actual effort. In the end I completed the run both pleased and disappointed. Pleased, because my time was better than average, but disappointed because I was still 15 seconds per mile slower than my last weekday run.

I'm aiming to improve on that tomorrow. Perhaps the disrupted sleep affected my performance. Yes, let's go with that.

Fast track to performance gains

Flow of the workout

Today's workout (track): 1 mile tempo, 12 x 100M, 1.25 mile cool-down = 3.1 miles

This morning I headed out early to the local track to run intervals and tempos. I took the Virratas out for their first run, and thought they responded well to fast pacing. My plan was to run one mile at 5K race pace, which I'd follow with intervals and a cool-down run.

The track had a few walkers and a couple of runners when I arrived. I got started quickly on my tempo warm up and found a pace that felt hard, but sustainable. I locked into that pace for four laps, guided by perceived effort. Along the way, I passed everyone including the other two runners on track. After last Sunday's low point of the race, when I was being passed left and right around mile five, it felt good to be the one who was doing the passing. I averaged 8:18 for the mile.

Next, I ran a set of 100 meter repeats, averaging 6:40 per mile. I was surprised when I later looked at heart rate data and saw that I'd averaged between 74-80% of MAX. Knowing that, I can probably get my pace down to 6:25, while still staying under 90% MAX. However, I'll probably keep it to 8 x 100's for that session.

I finished the workout with a 1.25 mile cool down, run at a moderate (9:21) pace. In total, it wasn't a lot of distance, but the intensity made up for that. I'm planning a long run tomorrow, either on the Bethpage path, or another route that will facilitate a 6+ mile distance better than my neighborhood roads. My performance has improved greatly for runs between 3-3.5 miles. It will be interesting to see how my pacing holds up, when I double that length tomorrow.

Perpetual motion running at Bethpage

Perpetual force plus PureDrift

Today's run (Bethpage State Park): 6.1 miles

Not that running six miles is particularly challenging, but when you add Bethpage's rolling bike path, the going can get tough. With a 10K race looming, I felt that I needed to break out of my 3 to 4 mile run habit and push my base closer to race distance. I expected today's run on the Bethpage trail to be difficult, but it wasn't. In fact, I could have easily added a couple of more miles when I got to the end.

Things didn't start out well this morning. I dressed for my run before noticing a steady rain outside. The weather reports indicated that things would clear up in an hour so I waited. It was drizzling when I left my house and the intensity of the rain increased along the way. When I arrived at the park, it was back to a drizzle and I was fine with that. I decided to follow the older path south - three miles out and three back.

I had trouble generating speed as I took on the first hill after the trail head. Even during the long downhill section that followed, I felt constrained. But shortly before the one mile point, I literally "hit my stride", taking on the rolling hills with little trouble. I wasn't moving that fast, but the activity felt friction-less. I remembered that Adventure Girl called this "perpetual motion running."

I kept waiting for my energy to drain as I burned off glycogen, anticipating the struggles that would come when my system turned to alternative sources of fuel. It began to rain at the same time that I started to tire. Perhaps it was the practical need to get out of the rain that changed my energy, but I stepped it up and returned to the perpetual motion stride.

The last mile of this route has a few short steep hills and one long one. I focused on shortening my stride length and maintaining my cadence. I wouldn't say it was easy, but after 5.5 miles I still felt strong getting through the last section. Once I crested the dreaded last hill, I realized that I was feeling strong enough to keep going.

I ended up turning left to return to my starting point. I'd cover my planned distance and confirmed that my conditioning was on track. My trail run with Chris will happen on Thursday and Mike and I are doing a Dirty Sock course practice on Saturday. Those workouts will help fine-tune my race readiness. I hope that perpetual motion stride will return when I need it.

A surprisingly decent time for a low PE run

Today's run (street): 3.6 miles

My Labor Day weekend started this morning, so I had an opportunity do a weekday run longer than my usual, time-constrained 2.5 miles. It's actually 2.53 miles, but who's counting? Well, I am. An extra three hundredths of a mile drops my average pace by six seconds per mile at that distance.

I targeted about 3.5 miles for today because it's a nice bump up from the 2.53 on a weekday, but short enough to get it done quickly. Although I didn't need to rush out the door when I returned home, the rest of the day was booked and I wanted a chance to relax before I headed to my first appointment.

My run was interesting. It was hot by the time I got outside and I wasn't really in the mood to push hard. I used only my heart rate as a way to gauge my performance and adjusted my speed to get into my targeted zone. Even while my pulse increased, I didn't feel like I was working as hard as I did last week, when I broke 9:00 four mornings in a row.

I ended up completing this run in the mid-9:00 range. Going only by perceived effort (PE), I expected that number to be 20 secs/mile slower. I was pleased with that performance on a hot day when I wasn't really working that hard. My average HR for the run was at the lower end of the anaerobic range. That tells me I have more on tap than I've been using on most runs.

Finally using my HRM (with good results)

Today's run (treadmill): 25 minutes

I knew it would be rainy this morning so I planned to do a treadmill run. I finally got around to setting up my heart rate monitor on Sunday and linked it to the Garmin, so I had that to play with. With the rain outside, it was very humid in my guest room. I put the fan in a fixed position and aimed it directly at the front of the treadmill. This reduces the heat, but the forced air causes dryness in my sinuses and throat.

It's been a long time since I've used an HRM. The treadmill has grips that allow you to capture your current heart rate, but read time takes a while and it's awkward to run that way at speed. The Garmin is much more convenient and it monitors in real time, providing important information as you run.

One important thing I learned was that my usual routine on the treadmill did not tax my heart as much as I'd thought. Since I despise this method of running it always feels hard, at any speed. What I thought was a good workout pace turned out to be on the threshold between the recovery and aerobic zones. To really get benefit I needed to push myself into the anaerobic zone (between 80-90% max HR).

I watched my heart rate as I increased the treadmill's speed and was surprised how hard it was to bump my HR higher on the aerobic zone. It may have been psychological, but I found it easier to sustain paces below 9:00 after seeing that my heart rate was still below 80% of max. I ended up running faster than I usually do on the treadmill without feeling much fatigue during or afterward. I'll be curious to see what kind of numbers I see when I take it to the streets tomorrow.

Speed takes effort, it's that simple

Today's run (street): 2.5 miles

The UPS truck mocked me as I drove into my driveway last night. The UPS driver usually does his deliveries in my neighborhood around the same time that I get home from work. I watched as he carried what looked like a shoebox-sized container, but he dropped it at a neighbor's house. Saucony is supposedly looking into what's happened to my pre-launch Kinvara 3's. I'm thinking I may never get them.

As much as I've anticipated the Saucony's, I'm still appreciating the Spira Stinger XLT's. I skipped yesterday's run, but went out this morning. Again I found the XLT's to be comfortable and responsive. I moved well during my run and, while my PE was relatively low, I felt like my pace was brisk. When I came to the end of my run I looked at my Garmin, only to see that I'd covered my route more than a minute slower than expected. So much for getting that bonus 15 seconds per mile from the XLT's.

I think the lesson I reinforced today is that, at my level, speed should feel hard. If I don't push it, I shouldn't expect to put up good numbers. Due to some scheduling issues this week, I'm swapping my Thursday elliptical session with a run tomorrow morning. I'll put in more effort and see whether that makes a difference. Perhaps the 15 second bonus only happens on harder runs.

Workouts, PE and relax-outs

Today's run (street): 2.5 miles
Yesterday's workout (elliptical): 25 minutes

My wife and I were comparing notes on our workouts this morning. We'd both had hard runs and I said that's the reason why it's called a workout and not a relax-out. She and I have very different training methods and I would be challenged to follow her routine. In turn, she would probably say the same of mine. But each day we congratulate each other (and ourselves) for getting it done. It's great reinforcement and it motivates us to continue.

Without a running watch I would have guessed that I ran today's route a minute per mile faster than I actually did. My perceived effort was high but I clearly fell short on performance. No matter, I recently read an article that said that perceived effort (PE) is a better gauge of how you should be running than holding rigidly to a targeted pace.

Every workout that I've done since returning to work has generated a high PE but performance on the low end of the scale. It could have to do with my adjustment back to 4:00 AM running because I feel very good overall. Maybe a long slow base run this weekend can get me back on track. Perhaps a relax-out is just what's needed.

Wearing the seagull proudly

Been there, done that, got the t-shirt

Today's run (street): 3.9 miles

The rain stopped this morning, so I took advantage of the clearing skies and went out for my run. I had no plan except to cover more miles than I normally do on weekdays, when I'm constrained for time. I was feeling slightly sluggish on my first steps out the door -- I think it had more to do with the humidity than my physical condition.

I ran easy for the most part, not minding my pace or even looking at my overall time. There were a few other runners out at the same time and I crossed paths with a young woman who appeared to be struggling with her workout. The weather was taking its toll on everyone. I completed my run feeling like I'd worked harder than my numbers showed. If it's more about perceived effort than actual pace then I did well today.

After my run I went for my six month checkup at the dentist. I was wearing my 2011 Cow Harbor t-shirt and my dentist (who is 8 months pregnant) joked that she'd skipped Cow Harbor this year because she'd gained too much weight. One of my daughter's teachers mentioned last week that he'd ran it on Saturday. I guess I shouldn't be surprised, around here, Cow Harbor is the race to run.