Words Before Data

When an athlete says "that was a disaster," they're not asking for an explanation.

Your athlete sends a workout report. The subject line is one word: "ugh." You open their file, check the numbers, and start writing an explanation for why their power dropped in the third interval.

You answered the wrong message.

Athletes who struggle with a session send two kinds of reports. One is a data question: what happened, and why didn't it go to plan? The other is an emotional signal: I feel like I'm failing. Sometimes coaches only respond to the data, regardless of which one they're actually receiving.

The difference lives in the words. "My legs felt dead" is a data report. "I feel so behind" is an emotional signal. "I just couldn't hold the pace" is data. "I don't know if I can do this" is not. A coach who addresses the physiology on that second type of message isn't wrong, they're just answering a question the athlete didn't ask.

When an athlete is losing confidence in the training, a clinical explanation doesn't land. It confirms there's a performance problem when what the athlete actually needs is for the coach to recognize that things are hard, but that it's OK. It was supposed to be. That acknowledgment doesn't have to be long. It just has to come first. The technical follow-up lands better after the athlete feels heard.

Most coaches come from sport, where the default response to difficulty is to push through it. That instinct is useful in competition. It doesn't transfer to coaching regular people as cleanly. When you move straight to analysis after an athlete tells you they don't know if they can do this, the advice doesn't stick, and the athlete learns not to send those messages. Once they stop reporting honestly, it's the beginning of the end.

The practical version is simple: before you open the data, read what the athlete wrote. Then ask yourself what kind of response the message is calling for. Sometimes it's analysis. Sometimes it's a coach who notices that things are hard.

If you haven't seen our new Claude and ChatGPT integration, it's ridiculously useful to surface situations like this. In Claude you could simply ask "Can you check my conversations with Cam over the last few months and find any messages where Cam had an emotional response to his training and I did not address it"

More demos of that new integration here