Last night, I decided today’s run would begin at the park. The park trailhead begins/ends right beside a track, which is perfect for strides at the run’s end.
This area is full of runners and bikers. It seems every other week there’s a 5k/10k and the like. There was one last Saturday, and just to be on the safe side, I checked for this Saturday. Nothing on tap! All clear!
Yet I arrived at the park shortly after 6:15 a.m., greeted by a tell-tale Start banner.
I drove around to investigate. Yes, a race would be underway in little over an hour. And worse, the track served as a staging area. I could be done with the main course before the race began, but the track was off limits, and the track was the only reason I came to the park.
Wasting no time, I headed to my usual spot and got my miles. Three slow miles culminating in three strides. I felt good overall, and it was fun to note how easy it was to lock into my target pace. It’s definitely familiar and comfortable.
Tomorrow’s run is 6 miles steady – 11:00-11:45 target pace. Looking forward to locking in on a pretty spring morning.
Most of my recent runs have been at conversation pace. My plan sets this as 11:15-11:30 minutes per mile. That’s a comfortable pace, especially once I’ve warmed up.
Blue gifted me a Garmin for my birthday, and I program it as a training partner. It alerts me elapsed distance and/or time, and it signals when I’m not running within a specified target.
Today’s run felt good early. I locked into what seemed to be an 11:00-11:15 pace (a little faster than target). But my Garmin didn’t agree. In fact, it alerted me several times that I was much too slow. I refused to speed up because I’ve gotten to know just what this range feels like.
I waited for my Garmin to smarten up.
As I approached the first mile marker, it still clocked me at 13 minutes a mile. At the marker, I stopped running and stopped my watch. No surprise – the satellite was wrong. Again. Thanks to my love of routine and familiarity, I know all the mile markers between the trailhead and 2.5 miles. I’d run one mile. Garmin thought it .89. Amount of time? 11 minutes, 3 seconds. I knew I’d locked into 11!
Once I resumed my run, it seemed to track me just fine. I have a theory as to why it was off this morning and last Thursday as well. I’m going to make some adjustments based on the theory, and we’ll see what happens.
A couple of other things to note…I ran with a water bottle today. I don’t really water mid-run for short bouts, but I do for anything 5 miles or longer.
Every Sunday from here on out I have a 5 mile or longer run. I’m preparing now.
Hydration belts constrict my breathing when they’re strapped on tight enough to stay in place. In general, holding a water bottle isn’t ideal, but the right one will be fine.
Today’s was the wrong one. It wasn’t soft enough in my hand and didn’t fit ergonomically. Perhaps more importantly, it was too hard to get water! Mid-stride, there’s no time or energy to undergo strenuous efforts or multiple steps to pull water. So I’ll have to find another one.
My new running shoes feel good overall, but I’m dealing with some foot fatigue. The ball of my right foot gets tired after 35 minutes or so of exercise. This is not a new challenge, and it’s not limited to running, but it has been more noticeable the past couple of weeks (before and after new shoes) and it will make longer runs intolerable. I ran with new insoles today to see if they’d help. I can’t say they did. So for that, back to the drawing board as well.
Don’t misunderstand me, it was my usual place, the closest trailhead of two nearby. The overwhelming majority of my runs start from here, but it wasn’t ideal for today.
Unless it’s the middle of a storm, I’ve decided to run rain or shine. Last night, it rained. For a slow or steady run, old faithful doesn’t pose a problem when wet. But today’s run was three slow miles with strides. The strides (sprints) are best done on dry land, or at the very least, on ground with strong traction. Most of the trail is wood, and slick when wet. The other trailhead? Right beside a track.
I realized my mistake within moments of arrival, but it was too late to relocate. The slow three would be fine, but I’d have to take it easy with the strides.
I ran the first of four strides on concrete, so I took it at a pretty good clip.
The remaining three landed on wet boardwalks. I ran those much slower, more deliberately.
I had the energy to give my best effort at the end. As it turned out, I gave the best I could based on the circumstances.
The truth is, I always have this choice. Circumstances are never stagnant, but I can choose to give my best effort, whatever that means at a moment in time.
Yesterday Blue and I ran two miles and strides. We arrived early to the park, ahead of the 5k racers. We got our two on the greenway and closed out the strides on the track. I wore new running shoes for the occasion, but I didn’t run long enough to see how my feet liked them.
Today’s long run was a 5-miler. An extra rest day Friday and carb loading yesterday proved great choices. I experimented with my pre-run fuel this morning as well, eating a little banana with almond butter before the left. The combination left me feeling energized and strong the entire run. My shoes also worked pretty well, and I’m looking forward to some good miles with them.
Next week I move into more vigorous runs and increased mileage. As it is, last month I set a personal record for most miles run in a month (58.4)! I am traveling to Colorado later this month. It takes me a few days to get used to the altitude, so I’m expecting a few days off then.
I planned to run rain or shine. It shined. After multiple forecasts predicting rain today, Mother Nature graced us with sun instead.
The agreeable weather did nothing to help my Garmin, which located me a quarter of a mile away from where I actually was. This is the first time I’ve experienced this malfunction, so hopefully it’s a rare occurrence.
The mistake confused me at first, and I invested plenty of energy troubleshooting and trying to adjust. Since I run the same trail most days, I knew where the first mile marker (not 1.20!) was. I restarted the Garmin from there and it had no trouble after that.
Muscle fatigue meant I worked harder to maintain my target pace, and although I had instant snapshots of my pace via my Garmin, I didn’t have my usual chirps warning me to speed up or slow down to stay on track.
All said, it was a taxing run.
Even with the challenges, I enjoyed myself, and the beauty of spring. Looking forward to stronger legs in the weeks ahead.
Not sure if it was vacay mode this weekend (and yesterday), or something else, but I was a tad bit slower overall today. Still on pace for the plan, but after so many runs at a consistent pace, it was surprising to see the numbers.
I tried something a little different this morning. I usually treat my first mile as my warm up, which means the first half mile I’m a little slower than target. Everything balances out after that. Today I did two short strides and a little bit of walking to begin. It helped me start the run faster than usual, and that could also have added to my slower pace later on. Rather than a half mile of adjustments, I was pretty close to my target range in half that distance.
In addition to everything else I’m doing, I’m actively working to increase my fruit and vegetable in-take. I like goddess foods, so it’s not a chore to eat them. But I do need some more recipes and meal-planning ideas. My medium term goal is to follow a pescatarian diet, with my long term goal to follow a mostly plant-based diet.
Right now I’m sipping a mason jar of infused water… orange slices and a cinnamon stick. I drink plenty of water daily, but it’ll be nice to play with the infusions this summer.
Today is Monday, an exercise rest day according to my running plan. It’s a good thing because I need it.
Before the plan, I alternated running, PiYo (“Pilates based yoga”), Pump (weights) and rest. I generally ran two-three days a week, did weights two days a week, one day of PiYo and one day of rest.
Last week I experimented with new things, including basic classical Pilates and a short kettle bell routine. The activities themselves may work with my running program, but I’ll have to be more intentional about planning which activities on which days (and to what degree). This week proved to be a little much.
Day Before: Cross-train or total rest
Day After: Cross-train or total rest
Day Before: Cross-train or easy run
Day After: Cross-train, easy run, or total rest
TEMPO RUN OR HILL REPEATS
Day Before: Strength train or easy run
Day After: Strength train or easy run
I have Monday, Wednesday and Friday as non-running days, and thus far my body is pretty firmly committed to Monday (today!) as a total rest day. I’m playing with strength training on Wednesdays, and PiYo on Fridays. For now at least. I’ll see how my body recovers this week.
Later on, I plan to incorporate swimming, and that will be an adventure all its own.
My plan calls for consecutive runs every weekend, with lighter mileage on Saturdays and long runs on Sundays. Yesterday we ran a 2-miler. Today’s long run was 5 miles slow.
Mother Nature provided another great morning for a run, and Blue provided great company. Blue trains for marathons when his schedule permits, but these days he’s kept it short and sweet. It’s been a treat to have him along for a couple of runs while he’s had a little down time.
Today I reached/exceeded my initial goal of 50 miles a month. And there’s still one more run on tap for May!
During my running season, I usually start light with 20-30 miles a month and increase the mileage to the 40-50 range. I haven’t calculated this plan’s monthly mileage yet, but this week, I’ve logged 14.
In another week or two, the volume climbs. I think I spotted a 20-mile week sometime in July…
It’s exciting to follow a plan, worrying only about weather interruptions. For years I ran with fibroids, which sidelined me a few days each month.
In 2015 in particular, I’d pretty much have to rest 6-7 days in a row, in addition to my standard rest days each week. Last November, after a lengthy decision-making process, I had a hysterectomy.
It’s freeing to run unencumbered now.
I’m curious to see how my body responds to the increased cardio, and I’ll be doing what I can to minimize injuries and stay strong, yet flexible in the coming weeks.
Today was an easy 2. Except it wasn’t exactly easy for me.
I invited Blue to run with me this morning, and because we live farther than 2 miles from the running trailhead, it made more sense to just run from home. In three years of running in this area, I’ve only “run from home” twice. Sidewalks are scattered here and there, while traffic and hills run rampant. Since I run for fun, and dodging cars while trekking uphill isn’t, I tend to avoid “running from home.”
That said, I knew it was only two miles, and Mother Nature provided a perfect spring morning for the occasion. We had a shaky start because I wanted to try Blue’s hydration belt/waist pack. I’ve worn it twice before, and both times slipped out of place. Irritating! But looking ahead to much longer runs this summer, I know I have to get a real water plan in place. I wanted to try the belt once more (on a short run) to rule out user error.
After a quick trial, I found it lacking, and Blue tried again, securing it lower and tighter. Then off we went.
Truth is, I felt nervous! I knew I’d have my usual trouble getting to the right pace initially, and now I’d have to contend with hills, too. We walked a few feet to clear my jitters, and *then* off we went.
The first quarter mile or so was about as tough as I thought it would be. And the uphill, sidewalk-deficient next half mile was, too. Soon, however, I locked into the comfortable 11:15-11:30 pace.
After a mile, we turned around and made the quick trip back home in plenty of time to catch the sunrise.
I’m supposed to complete quite a few of my training workouts at conversation pace – slow enough to talk to a friend. I wondered about the importance of running slowly so much of the time, especially when your overall goal is to train your body for speed and endurance.
I tend to take longer runs (5+ miles) slower, but, in general I run a moderate pace. For me that’s too fast to tell a story mid-stride, but slow enough to notice my surroundings and make an occasional quick joke.
Running at conversational pace (also called base running), has lots of benefits, including: helps create a more efficient running style; helps your muscles to learn to burn fat more efficiently, receive and process oxygen better, and deal better with lactic acid; trains your heart and lungs to become more efficient at absorbing, delivering, and utilizing oxygen.
All of those things sound important to me! Another writer emphasized the fat burning efficiency, and the fact that building a strong base is the key to faster, longer running. She even shared some interesting research about avoiding the moderate pace I usually run.
I love the way I feel on the longer, slower runs. The energy builds throughout the run, and by the end I feel so vibrant. But my uninformed approach was to run a moderate pace, especially on my shorter runs – nearly every run.
I’m curious to see how more conversation pace running will impact my overall ability to burn fat and run strong.
How about you? Do you run slow enough to hold a conversation, or do you go a bit faster?