The Sprint That Was Only Half a Sprint
Sequel to Inside the Athlete Blueprint. That post was about the trajectory what months of data reveal that a single test day cannot. This one is about the opposite end of the same telescope: a single moment, and what happens when you ask the athlete about it.
Here is a moment that appears on almost every GPS trace and gets read almost every time as nothing at all. A midfielder checks in for a ball played into space. The trace shows the acceleration as a real one, initiated, committed to. Then it shows the top speed reached during that effort: roughly half of what this athlete has recorded as their maximum. Not a jog. Not a sprint. Half a sprint.
This is not a player who cannot reach those speeds. This athlete's maximum sprinting speed is 29.5 km/h, and they cover 46.8 meters of sprint distance in an average game, 75.7 at their peak. The capacity is not in question. The question is what happened here, in a moment where arriving on time required more than half of what they had available.
This athlete reaches 25–28 km/h regularly — 46.8 m of sprint distance per game on average, 75.7 m at their peak. The capacity is not in question. In this particular moment it went unused: the effort topped out at 14.8 km/h, about half of maximum, and never crossed the 25.1 km/h threshold that would have counted it as a sprint. Half speed was not enough to arrive when the ball did.
Most systems will not flag it. It falls inside every acceptable range. Total distance looks fine. Sprint count is unaffected, because it never crossed the threshold to be counted as one. On a weekly report, it is invisible. It is also one of the most informative events of the session, and the number alone cannot tell you why it happened. What the trace establishes is narrow but exact: the ability was there and went unused. Why it went unused is a separate question, and the data cannot answer it.
The check-in at 61 minutes never crossed the sprint threshold, so it was never counted as a sprint. It did not lower the totals. It did not move any average. Every line above is accurate, and the most informative moment of the match is absent from all of them.
Three readings, one number
A half-speed check-in has at least three plausible explanations, and each requires a different response. It could be physical. Third match in five days, or a hamstring that has been quietly guarded since a knock two weeks ago. The body declined to go. If this is the cause, the response is load management and pushing harder is precisely the wrong move.
It could be perceptual. The athlete misread the situation. They did not see the space open early enough, so by the time they committed, the run was already late and full speed no longer made sense. If this is the cause, the response is decision work: video, scanning habits, recognizing the cue earlier.
It could be hesitation. They saw it, the body was available, and something stopped them — a hard tackle earlier, a mistake they are still carrying, a coach's reaction they are trying not to repeat. If this is the cause, no amount of conditioning or video changes anything.
Same data. Same acceleration profile. Same missing top-end. Three causes that look identical on the trace and share no treatment. This is the limit of measurement, and it is not a limit better instruments will remove. Force plates, timing gates, and heart rate straps all describe what the body did. None of them can report what the athlete was answering.
So we ask
In the cycle after that session, the athlete sees the trace. Not a summary, the actual moment, with the acceleration and the speed it reached. Then one question: what was happening there?
The answers we get are rarely vague. Athletes know. In our experience, they almost always know, and they are usually relieved that someone asked rather than assumed. The answer arrives in their own language: I didn't see the switch early enough, or my legs were there, but I didn't back myself, or third game that week and I was cooked.
That sentence is the missing variable. Not a soft supplement to the data, the interpretive half of it. The number establishes that something happened. The athlete establishes what it was.
What changes next
Load declined to go — third match in five days, or a knock still being guarded.
Ease the block and watch whether top-end returns as the schedule opens up.
Saw it late. By the time they committed, the run no longer justified full speed.
Scanning habits, cue recognition, video. Look for earlier commits on the next trace.
Saw it, body available, something stopped them — and it was not the legs.
What are they protecting themselves from, and do the conditions that made it sensible still hold?
Three causes that look identical on the trace and share no treatment. Choosing without asking is choosing at random.
The value of the answer is that it produces a different next four weeks. If it was physical, the following block manages load, and we watch whether top-end speed returns as the schedule eases. The data verifies the account.
If it was perceptual, the work is scanning and cue recognition, and we look for the same signature on the trace in a month. Fewer late commits, more runs initiated early enough to be worth full speed.
If it was hesitation, the work is neither conditioning nor video. It is the conversation about what they are protecting themselves from, and whether the conditions that made that protection sensible still hold. That is the slowest of the three and usually the most consequential.
And here is the part worth noticing: in every case, the next trace tests the interpretation. If the athlete said their legs were fine, and the top-end never returns across three cycles of light load, the account was wrong or incomplete, and we look again. The data checks the reflection just as the reflection explains the data. Neither gets the last word.
One of these is what happens next. The athlete said the legs were fine — that is a claim, and the following cycles test it. Neither path is a failure. A flat line is not a worse outcome than a rising one; it is the information that the first explanation was incomplete, arriving early enough to act on.
The data checks the reflection just as the reflection explains the data.
Reading this chart
The bottom line marks time this session, then testing four, eight, and twelve weeks later. Height is the fastest speed the athlete reached in each session. The dashed red line at 25.1 km/h is this athlete's sprint threshold: efforts above it count as sprints, efforts below it don't. In the session we've been discussing, the athlete topped out at 14.8, well under that line.
The two paths show what could happen from here. The gold one rises back over the threshold, which means the athlete's explanation was right and the speed came back as expected. The dashed grey one stays flat, which means it didn't — so the explanation was incomplete and we go looking for what we missed.
Either way, we know within twelve weeks instead of guessing.
GPS as a medium, not a verdict
This is what we mean when we say measurement is a medium of interaction rather than an assessment. A verdict is delivered. It closes a question: the athlete is a 7 out of 10, the output was down 15%, here is your report. A medium opens one. It gives the athlete something specific and undeniable to react to, and it gives the coach something better than you looked flat to open with.
The specificity matters enormously. "How was training?" gets fine. "Here is the moment at 61 minutes where you checked in and reached half your top speed; what was happening?" gets an actual answer, because the athlete cannot retreat into generality against a trace they recognize.
“My legs were there. I just didn’t back myself after the first tackle.”
The number establishes that something happened. The athlete establishes what it was.
Fourteen-year-olds are not evasive by nature. They are evasive when the question is too vague to answer honestly.
Where this sits in the process
The Blueprint post showed the trajectory: high-speed running from 412m to 847m, asymmetry from 14.2% to 5.8%, jump output climbing across six months. Those arcs are what accumulate. This is the mechanism underneath them. Each cycle runs the same four steps:
The session
Everything the GPS records, with nothing interpreted yet. The acceleration, the speed reached, the seven seconds it lasted.
The trace
The moment itself put in front of the athlete — not a weekly summary. Their data and their account of the same session, side by side.
The conversation
Where I played badly becomes I hesitated. A gap with a name is a gap you can work on.
The next block
Built around the gap that was actually named rather than the one assumed — and the next trace tests whether the account held up.
Common questions
Can performance data tell you whether an athlete is hesitating or just tired?
Not on its own. A hesitant effort and a fatigued one can produce nearly identical traces — the same initiated acceleration, the same missing top-end. The distinction requires the athlete's account, gathered close enough to the session that they still remember it. What the data does contribute is the prompt: it identifies the specific moment worth asking about, and it verifies the answer over the following cycles. An athlete who reports fatigue should show recovering output as load eases; if the output stays down, the explanation was incomplete.
How do you get a young athlete to talk honestly about their performance?
Ask about something specific enough that a vague answer is not available. Broad questions produce broad answers: fine, okay, I don't know. A particular moment on a trace the athlete recognizes produces a real one, because they were there and they remember. Two other conditions matter: the conversation happens close to the session, and the athlete's answer visibly changes what happens next. Athletes stop reporting honestly when reporting changes nothing.
What does an athlete's own reflection add to objective performance data?
Cause. Measurement establishes what happened with precision no coach's eye can match; it says nothing about why. Because the response to a physical cause, a perceptual one, and a psychological one share nothing in common, a program that skips reflection chooses an intervention at random and hopes. Reflection also builds something durable in its own right: an athlete who learns to name what they are experiencing with precision carries that capacity well beyond sport.
The figures and reflections in this post are illustrative. They are drawn from anonymised sample data used to demonstrate how our reporting works, and are not the record of any individual athlete. The pattern is real and common; the athlete is not.
Athlete data at Adaptiverse belongs to the athlete and their family. It is never published, and never used in marketing.
Adaptiverse runs performance testing and training in Fallbrook, North San Diego County — GPS, force plates, Kineo intelligent-load resistance, and timing gates, with the athlete's own account recorded beside every cycle
