Tag Archives: speed run

More on the Nike+ Running Club Experiment

As I progress through the marathon training programme concocted by the Nike+ app, I am enjoying the challenging runs that it is assigning me. 

After last week’s benchmark run it has started to add pace requirements to the runs that I do. Currently, they are all well below the pace that I generally run at which seems a little strange. Perhaps this will adjust as the programme continues?

On Sunday I decided that I didn’t want to do the suggested exercise which was to tryout the Nike+ Fitness Club application. Instead, I opted to run 12 miles. 

The run went well and was an enjoyable run on the Perkiomen Trail from Schwencksville. 

On completing the run, I chose to categorise it as an ‘Other’ event as I had already competed all the runs for that week. 

Come Monday morning and a new training week and guess what? The app tells me I need to do an 11.5 mile run. On a Monday morning. After doing 12 miles the day before. Bugger off!

I tried to reclassify the previous day’s run so that it would count as this one, but to no avail. There’s no way to edit the assignment of previous runs; even the website doesn’t offer a way to do this. Boo. 

Because of this, the app thinks I bailed on the long run for the week. :-(. 

I did actually go out and do a four miler but that isn’t twelve miles!

Roll on to Wednesday morning and the prescribed run was a speed run with 8x800m intervals and 2:45 recovery (strangely specific). 

I wasn’t too happy about this as that’s a lot of intervals but opted to hit the streets. Running track intervals on the road is tough as you have to allow for traffic and the ground is not flat; hills in fast intervals. Yuck. 

For the recovery periods I simply jogged a little and ended up running a total of around 7.5 miles. 

Did you notice how vague that was?

Why? Well, the speed test only counts the distance you run during the speed intervals and not what you cover in the recovery. 

Four miles is all that counted from the 7.5 I covered. Grrr. Not best pleased. 

Any way, one useful thing you can do with these 800s is use them to calculate your estimated marathon time using the “Yasso 800” approach. I know this is a correlation prediction rather than a causation, but it is fun to play with numbers. 

After some finagling of the numbers I worked out that my marathon time would be 3 hours 43 minutes. That’s pretty close to my current expectations of my performance. 

Back to the Nike+ stuff: I’m not best pleased that I have to run the speed tests with the phone in my hands. As I got sweaty I was worried I’d drop my phone. I think I’m going to stick some strong magnets inside my gloves so that they will grip the metal plate in my phone case and take some of my worry away… I’ll let you know how that works out. 

Have a fun week running. 🙂

Nike+ Run Club Experiment

I have been an avid user of mapmyrun for many, many years, but with my purchase of the Apple Watch Nike+, I’m trying out that app for a while.

My trial with Nike+ continues with the third week of my plan and some variations on the types of run it is having me do.

Firstly, it had me run a speed test this week. This wasn’t a great experience. The speed test is laid out as running 400 meters five time, with a two minute rest break in between. If you try to start this from your Apple Watch Nike+ it will tell you to use the phone. When you use the phone you will quickly realize that you’ll have to keep your phone in your hand while you do the run! 

After you start the run, you need to watch the screen to see when you pass the 400 meter mark, then you have to press a button. This starts the two minute rest timer. Once it passes two minutes you need to press the button again to start the next 400 meter section… there are no audio prompts, no guidelines and no feedback. 

Again there is no integration to the watch whatsoever.

At the end of the run, the disembodied voice of Kevin Hart blasted through my brain congratulating me on the run.

My feeling about this exercise routine is that it was very poorly implemented.

The second run type was a benchmark run. This was really well implemented. A benchmark run is a seven minute gentle warm-up, followed by three minutes of all-out effort and five minutes cool-down time.

When you start the run, a calm-voiced trainer gentle talks to you about what you are about to do. They introduce the form of the run, why you are here and give you good general coaching encouragement. Throughout the warm-up the coach builds your enthusiasm for the coming effort.

There’s a count down to the theee minutes and you’re off! The coach chimes in a couple of times during this hard effort encouraging you to push harder and letting you know how far through you are. Then, all too soon, the hard effort is over and you are in the cool down phase.

Here the coach tells you what you achieved, massages your ego a little and reminds you why you are doing this.

Once you complete the run, that disembodied Kevin Hart voice comes back to award you a gold star.

What a difference between the implementations! 2/10 for the speed routine. 9/10 for the benchmark. 

I’ll fill you in with more details as I move through the program.