He got in the car still holding his spikes, didn’t put his seatbelt on right away, and said “I was point-eight off” before we’d even pulled out of the lot. Not “I ran a 68,” which is what the clock actually said. Point-eight off. Off from the 67.2 he’d run three weeks earlier, a time he’d apparently memorized down to the tenth and had been carrying around like a debt he owed himself. We’d watched the race. It looked like a good race. He didn’t see it that way at all.
Track does this to kids in a way other sports don’t. A basketball game ends and the score is the score, but nobody walks away with a number stamped to their identity for the season. Track times get posted publicly within the hour, ranked against every other kid at the meet and often against a season-long list on an app that everyone checks. Our son had one good race in September, and from that point on, every single race got measured against that one number instead of against where he’d actually started the season.
The instinct in the car was to say something like “times don’t matter, just do your best,” which is the kind of thing that sounds supportive and lands as completely dismissive to a kid who has spent an entire season caring very much about one specific number. He would have heard it as us not understanding the sport, or worse, not caring about something he cared about. So we didn’t say that. We asked him what his time was in June, at the very first meet of the year.
He didn’t know off the top of his head. That was useful. We pulled up the results app together, right there in the car at a red light, and looked at his times across the season: 71.4 in June, 70.1 in July, 69.5 in August, 67.2 in that one great race in September, and now 68.0. Five races, laid out in a line. He’d shaved more than three seconds off his 400 time since June. The 68.0 he was upset about was still faster than every single race except the one he’d fixated on.
One number is a moment. Five numbers are a trend, and a trend is what’s actually true about a season. We didn’t say that out loud in those words, because it would have sounded like a lecture. We just looked at the list together and let him do the math himself. He got quiet for a minute, which is usually a sign that something landed rather than a sign that he’d tuned out. Then he said “I guess that is pretty fast,” about the 68.0, in the specific tone of a kid revising an opinion he’d been sure of two minutes earlier.
The temptation in this exact spot is to overcorrect into stacked-on praise, piling reassurance onto the moment instead of trusting that the numbers had already made the point. We didn’t do that either. We asked him what he thought made the September race so fast, whether it was the weather, the competition in his heat, how he felt that morning, anything specific he remembered. He had theories. He remembered feeling good in his legs that day, remembered a kid next to him going out fast and pulling him along. That’s useful information for a runner. It’s more useful than a number sitting alone with no explanation attached to it.
We’re not saying the fixation goes away after one car ride. He still checks his time against that same race every single week, and some weeks it stings when he’s a few tenths off it. But something shifted a little after that conversation. He started asking about his splits instead of just his final time, started noticing when his first 200 was faster than usual even if the final number wasn’t his best. That’s a kid starting to read his own progress instead of measuring himself against a single ghost of a race three months gone.
A few weeks after that first car ride, he asked us to help him build his own version of the list, times from every meet going back to his first season the year before. He wanted it typed up, not just scrolled through on the app, said it was easier to see the shape of it that way. We sat at the kitchen table one evening and typed his times into a note on the phone while he called them out from memory, correcting us twice when we mistyped a tenth of a second. Watching him build that list himself, instead of us pulling it up for him in the car, felt like the actual turn. He wasn’t asking us to prove the trend to him anymore. He wanted to see it laid out in his own words.
That list came in handy a month later when he had a genuinely bad meet, a 70.3 that was slower than almost everything he’d run all season, and he pulled it up himself before we could say a word.
The gear guide for track and field is worth a look too. The right spikes will not fix a fixation on one number, but bad ones can cost real tenths.