I grew up watching my dad, a runner, track his miles. He always took the time to note how far he ran, the day’s temperature, wind direction, and a few other details about his run. It seemed only natural, then, when I started running (and later riding) to keep a mileage log.
I recently read a few pieces about the limitations of tracking miles (Bicycle Bug recently penned a good one), and I agree that ultimately the overall ride experience is most important. It can also be toxic when counting miles morphs into an obsessive pursuit.
Overall, though, I like tabulating the miles I ride and run. My mileage logs have also taught me a thing or two, which is something I did not expect when I first began jotting down my workouts.
I keep my mileage log simple, possibly too simple for many people. I use one of those small paper datebook calendars. Yes, it’s old school. I prefer to keep track of these things on paper.
In the space provided for each day, I jot down my ride or run with a brief summary, e.g., “ride to work plus trip to Whole Foods and back - 11 miles.” I will also write down those times where I find my energy to be low or if a ride or run went exceptionally well. Other than that, it’s basic mileage and route. If my activity for the day included a workout at the gym, I’ll also note that.
For a year or so, I tried Daily Mile, but it didn’t work for me. I liked the social networking side of it, but disliked storing my information on-line. It also brought out this unhealthy competitive side of me where I started pressuring myself to chase miles so that I would show up on leaderboards. I retreated from that and went back to my paper-based ways.
Even by tracking the most basic data, I’ve been surprised by the patterns that have emerged from it over time and seeing how it correlates with how I’m feeling.
For example, I’ve noticed that my riding typically trails off in September. Both September of this year and last year I felt burnt out from cycling. A review of my logs from 2012 and 2011 showed that April through August are usually my biggest months for cycling. The higher miles and greater focus on cycling during those months probably contribute to my September burnout.
During September of this year I also felt exceptionally tired. It seemed like I was getting enough sleep each night so what was up? In looking at my mileage, I realized that my running miles are up and trips to the gym more frequent this year. Those two activities, in addition to the bicycling, have probably built up some fatigue in me.
Mileage logs also help with figuring out how to train. I disregarded my running base when increasing my mileage earlier this year, and now I’m dealing with knee pain which I believe was caused by my doing too much too fast too soon after our big months of bike riding. Mileage log fail? No, the mileage log clearly shows where I went awry.
As I reflect more on my mileage, I realize I’m not tracking enough information regarding my strength workouts. I have a sense of my progress (or decline) in this area but would like to know more about it on paper. Tracking my strength workouts better would also help me combat plateaus and figure out if I’m missing any muscle groups.
I’m having fun supplementing my cycling and running with weights, but would like to be a little more strategic about what I’m doing when I’m at the gym. If you have any suggestions for a good and easy way to track weight workouts, please let me know in the comments or send me a note.
For some people, mileage logs might not be viewed as a good use of time, and I agree that it is not critical to have numbers support how your feeling, physically or otherwise. If you’re tired, you’re tired. If your knee hurts, a mileage log won’t change that. However, mileage logs have helped me understand why I might be feeling a particular way and have also been useful in shaping my future physical activities.
I like seeing how my rides and runs fit into all of the competing priorities of any particular year. Watching how my activity levels ebb and flow over time and why is fascinating. As long as I continue to glean these kinds of additional insights, I will probably continue to use one.
What did I miss? Other good reasons for keeping a log and/or other information that might be helpful to track?