I spend a lot of time looking at what my heart does while I am running. Pace is easy to understand. Average heart rate is easy to obsess over. Distance gives me a clean number to point at afterward and say, there, I did that. This week, though, the number I kept coming back to was what happened after I stopped.
That started with Saturday’s 13-miler, which was memorable for all the wrong reasons. By the end of it, the heart-rate alert had become my mortal enemy, my mechanics were getting worse, and even when I slowed or walked, my heart was taking longer to settle. Late in that run, the recovery numbers deteriorated to drops of about 12 beats, 12 beats and finally only 4 beats. That matched the experience pretty well. I was cooked.
So I paid closer attention this week to something I usually treat as an afterthought: heart-rate recovery — how quickly my heart rate comes down once the work is over.
| Date | Run | Avg pace | Avg HR | Heart-rate recovery |
|---|---|---|---|---|
| Sept. 15 | 5.12 mi | 10:08/mi | 144 bpm | ~21 bpm at 1 min |
| Sept. 16 | 3.63 mi, hills | — | 130 bpm | ~22 bpm at 1 min · ~28 at 2 min |
| Sept. 17 | 4.19 mi | 10:16/mi | 146 bpm | ~25–26 bpm at 1 min · ~37–39 at 2 min |
That got my attention.
Three Different Runs
Tuesday was FootWorks. I spent much of the run doing what I tend to do in a group: acclimating to the people around me. I settled into the pace, let the run be social, and then naturally found another gear late. The result was 5.12 miles in 51:52, 10:08 per mile, average heart rate 144. Once I stopped, heart rate dropped about 21 beats in the first minute.
Wednesday was Rickenbacker, which is its own animal. Hills change the equation, and I was also coming into that run after lousy sleep. Even so, the 3.63 miles were controlled, with an average heart rate of only 130. More interestingly, the recovery was still solid: about 22 beats in the first minute and 28 by two minutes.
Thursday gave me the cleanest look because I deliberately left the watch running after I stopped. I wanted to see the recovery instead of cutting it off with the activity. The run itself was 4.19 miles in 43 minutes, 10:16 pace, average heart rate 146. Then I stopped and watched. About a minute later, heart rate was down roughly 25 or 26 beats. By two minutes, the drop was around 37 to 39.
Now that was interesting.
The Number After the Number
I have to be careful here because this is exactly how my lizard brain creates commandments out of Garmin data. Three days do not constitute a longitudinal study, and I am not about to decide that every run from now on must produce a 26-beat recovery or civilization has collapsed.
But telemetry is useful when it answers a question instead of creating one. Saturday felt terrible, and the recovery data agreed. This week felt different, and the recovery data agreed with that too. The pace changed. The terrain changed. The effort changed. But in all three cases, my heart was settling down well after the work ended.
That tells me something average pace alone cannot. Marathon training is not only about how much work I can produce. It is also about how much work I can absorb.
That distinction is starting to matter more to me. For a long time, I have judged fitness by whatever number Garmin happened to put in front of me while I was moving. Faster must be better. Higher heart rate must be bad. Lower heart rate must be good. Then I spent nearly three hours on Saturday letting an alert from the same watch bully me into a shuffling gait that made my joints hurt.
I turned the alarm off. The data stayed.
That may be the healthier relationship with the watch. I still want the numbers. God knows I am going to look at them. But increasingly I want them to tell me what happened, not tell me what to do.
Work. Recover. Adapt.
There is another reason the recovery numbers feel relevant now. The running is no longer the whole training program. Dr. Hale has me doing strength and mobility work twice a week. I am trying to respect easy running as actual easy running. I am paying more attention to sleep when life cooperates. The goal is not just to build load. It is to build a body capable of absorbing the load.
This three-day block is a small piece of evidence that the system may be responding. Tuesday I could run socially and still finish with something available. Wednesday I could handle the Rickenbacker hills without turning the workout into a cardiovascular drama. Thursday I could run again and then watch my heart rate fall nearly 40 beats over the next two minutes.
None of that means I am bulletproof. Saturday cured me of that fantasy quite effectively. But this is what I wanted from the rebuild: not one heroic run, but the ability to do the work, recover from it, and come back ready to do something different the next day.
For once, the most interesting number on the watch appeared after the running was already over.
Philadelphia is still the immediate race in front of me, and I’m running it as a Parkinson’s Foundation Champion. If you’d like to support that effort, you can donate through my Philadelphia Marathon fundraising page.