Running watches I have known

I've tried a number of running watches over the years in pursuit of the perfect watch. My watches over the past 10 years or so, in the order I adopted them:

- Nike Triax C6
- Nike Triax CV10
- Suunto T6C
- Garmin FR60 (my current watch)

I still haven't found the perfect running watch - here is what I think of the ones I've run with so far.

I liked the style of my first Nike Triax - the angled design of the watch face was nice. I used it to capture splits and total run time, including using countdown timers for managing interval workouts. I could see my heart rate data in real-time.  For a running log, I entered summary data by hand into a spreadsheet.   It was a nice running watch, with all the timing capability I needed.

Moving on to the Nike Triax CV10 let me add a shoe pod to the heart rate monitor (HRM) to measure speed and distance. If you've seen some of my older blogs, you know I'm a fan of the statement "you can't manage what you don't measure." Running by 'feel' is OK, but at some point it is good to have actual data that shows what heart rate and running pace actually corresponds with perceived level of effort. After running a lot of miles with a HRM on, I've definitely changed my idea of how hard it should feel like I'm working on my long runs.

A running buddy then adopted a Suunto T3, and the concept of training effect (TE) was interesting. In my typical need-to-know-it-all fashion, I downloaded all the Suunto training materials and read and re-read everything. I eventually wound up buying a Suunto T6C for myself, with the Suunto HRM and shoe pod. I also adopted a running software package called Firstbeat Athlete to log my watch data and monitor my progress.

At this point in running watch evolution, it's clear to me that a big part of the total functionality of a watch now lies in the software you use with it and ability of that software to load and use data from the watch. This software is typically PC (or Mac) or web based. The Suunto T6C and Firstbeat software gave me new insight into the effect of workouts of different durations and intensities.

I moved away from the Suunto T6C/Firstbeat Athlete combination for a couple of reasons. Part of the appeal of capturing heart rate data at the R-R level was the promise that you could get feedback when you are over-training. I never really thought I benefited from this capability. The Suunto watches capture the data needed for heart rate variability analysis, but rely on external software (and a person) to do the analysis. And this software is typically owned and used only by professional trainers. The fee to have some data looked at on a one-off basis is prohibitive to do on a regular basis. Note that some Polar watches, and some iPhone apps will now do this sort of analysis.

Firstbeat Athlete is showing it's age a bit. It has some long standing issues with not always syncing a users profile (things like height and weight) with the data stored in the watch. And as a running log, it had a long standing bug with not adding up your weekly mileage correctly.  A recent update to Firstbeat Athlete actually added the ability to import data from a Garmin 610 using the wireless USB stick but not much else changed. I think the Firstbeat folks are first class exercise physiologists, but I'm not sure what their plan is for future PC and web based software.

Finally, I become frustrated with the finicky-ness of the Suunto T6C computer data connection, a small clip that uses a set of dimpled electrical contacts on the back of the watch to connect the watch to a USB port. The future of data connections is of course wireless.  Both Suunto and Garmin seem to be using very similar technology for wireless data connections on their newest watches.

The new Suunto Quest seems like it might have been a good follow-on to my T6C, but my search for my next watch and software combination led me to the Garmin FR60 and SportTracks 3 software (from Zone 5). I've basically traded training effect for TRIMP (a numerical method of summarizing duration and intensity), and gained a very reliable and convenient way of transferring watch data to my PC. A new data-point the Garmin FR60 provides is running cadence, which I've been watching pretty closely lately.  I've previously blogged about SportTracks 3 and some of the plug-ins I use

Thoughts on GPS - I do study maps (and take maps with me) on new trails the first time out. I might benefit from a capability to enter a planned run into the watch, but frankly it wouldn't help - I do a lot of backtracking out there. Besides, most of the time I'm on a trail where I know where I'm going, and where all the wrong turns would take me. Finally, the power requirements (read: short battery life, and need for constant charging), and the physical size of the watches almost rule out using a GPS watch as an everyday watch. The Garmin 610 looks pretty good though if you're willing to do the trade-off.

Finally, I tend to wear my running watch as my everyday watch to work and when travelling. I always use the alternate time zone and depend on alarms working when I'm on the road. I found each of these watches are suitable for all but 'dress up' occasions (they all make a statement that I'm a runner, but I'm almost always willing to talk about that).