I have had my running watch for nearly two years now. You would have thought that two years would be long enough to work out how it works. You clearly haven’t met me before.
Last week we ran the Delicious Dart. My watch gave me progress updates for the last third of the run in nautical miles.
Not only that, I am sure all of the runners in my readership will recognise this:
I worry that my watch has a bust-up with the satellites above our heads. I’m considering referring them to Relate.
This weekend, I uploaded some of the data from my watch onto the laptop. I don’t do this that often, but I was keen to find out why it thought I had been swimming the final five miles of the Delicious Dart. Sadly, it was less than illuminating.
But, on the back of this little exercise, I started to receive emails. The first was of the Dear-God-you’re-still-alive variety (I didn’t think it had been that long). The second worried me more.
“Hello,” it said. “Congratulations, you recently set a new threshold pace value. We recommend you update your zones in TrainingPeaks for optimal analysis.”
Sorry, you recommend I do what now? Please bear in mind that I struggle to turn the thing on at the best of times. What exactly are my zones and do I really want them to be optimally analysed?
Realising that they have to deal with idiots like me, they did include a link to some more information. If I’m honest, I’m not sure I understood that either – they should have had more pictures – but I do at least realise that there is more that I could understand about my performance. I now know that “if your ATL is greater than your CTL, [then] your TSB will be negative.” Which is nice.
Do I need to know this in order to go out for a run? Clearly not. But is it something I could find out more about? Possibly.
And I can rest assured that my watch will be keeping an eye on it all for me, even if I don’t understand what on earth it’s doing. Which is completely reassuring, right…