She Did What Made Sense. That Was the Problem.
Why our reports start with the athlete's own words, and why coherence is not the same as understanding.
After a recent game I asked a young midfielder one simple question: why did you stop defending in the first half?
Her written answer was honest, and it made complete sense. We had been working on her dribbling. In the game before, a move finally worked for her, and she felt what it was like to beat a player. In this game she had more time on the ball than she could ever remember. And the other team looked harmless to her: they kept giving the ball away. So she stayed high and waited for the ball.
"After feeling that feeling of dribbling, it's the only thing I wanted to do… The only thing that was running through my mind was dribbling."
Every step of that story holds together. That is exactly the problem.
Coherence is not knowing
All of us do this, players and coaches alike. When the game moves faster than we can process it, we keep what seems important and build a story that holds together. A coherent story feels like understanding. But it quietly hides what it left out.
In her story, dribbling became the figure and defending became the background. Defending didn't disappear. She simply stopped seeing it.
The part that was mine
There is a second lesson here, and it is about me. I had told her she needed to dribble more. I meant: add this to your game. She heard: this is your game now.
As coaches, we know that everyone sees the game differently. Yet we expect our own words to land exactly as we meant them. I am no exception. The instruction was right. Without its purpose, it landed as something else.
So there were two gaps in this story. The first sits between what she lived and what she could say: she only found the words afterwards, in writing. The second sits between what I said and what she understood. The first gap is hers to close. The second is mine.
What nobody had to tell her
Her second reason is the one I keep thinking about. Nobody told her that a weak opponent means you don't have to defend. She learned it by watching. She had seen stronger players take it easy against weaker teams, so she did the same. In her environment, her story was perfectly coherent.
"I felt like they would lose the ball a lot with their own mistakes … so it gave me the confidence to stay higher up the field and try to focus more on attacking."
But what it left out is the most important part. An easier game is exactly the moment to test yourself, mentally and physically. Press harder, run more, win the ball back, and build the habits you will need when the opponent is better than you. The weaker the opponent, the bigger the chance to grow, not the smaller.
What she did next
Here is the part I admire. In her reflection she took her own reasoning apart. If the other team gives the ball away that often, she wrote, that is an even bigger reason to press, not to wait. Then she named her pattern herself: she tends to lock onto one thing and lose sight of everything else.
"Because they are bad with the ball, it should be an even bigger reason to drop back and try to defend."
"I'm not using it as an excuse, I'm stating why I was thinking what I was thinking."
"I always try to focus on just one thing … I know I'm going to get better at this, because I feel like I've been changing a little each game."
That is the most valuable question in development: what did I leave out? She asked it on her own.
It is an old idea. Nicholas of Cusa called it learned ignorance: knowing the limits of what you know. It keeps a story open instead of closed, and it is a habit, not a talent.
Her GPS data from that game agreed with her. Her high-intensity running was well below her usual. The numbers didn't tell her anything she hadn't already written. They confirmed that her own read was accurate, and that matters more.
Settling or holding
Her game had a contradiction inside it: the freedom to attack and express herself, and the duty to defend for her team. She settled it. She picked one side and let the other go, so she could act.
Most of us do the same, in sport and outside it. Settling lets us act quickly. Holding both sides at once is harder, and it is an achievement, not a given.
Holding, for her, would look like this: take players on when the moment is there, and when you lose the ball, be the first one to win it back. Not half of each, but the best balance for now, moment by moment.
I believe holding can be trained. On the field, through rules such as "lose it on a dribble, you have five seconds to win it back." Off the field, through reflection like hers. Her story is a great example of where that training starts: seeing that you settled, and asking what the other side needed.
Four questions instead of more information
More information isn't the answer. Meaning is. After every important moment we ask four questions:
What happened? I only wanted to dribble, and I stopped defending.
Where is it leading? Dribbling is a tool to break a line and create, and when the ball is lost, the first job is to win it back.
Why does it matter? That answer belongs to the athlete. We don't hand it to her.
What did I leave out? Defending, running, and the teammates around her.
The first question builds coherence. The other three turn it into meaning.
How we use this at Adaptiverse
This is why every Adaptiverse report now starts with the athlete's own words, before any numbers.
Capture: the athlete tells the story first, in a short reflection after games and training.
Expose: the data confirms or challenges that story, and shows what it left out.
Realize: we connect what happened with where it is leading and why it matters.
Navigate: we choose the best way for now, and we revisit it after the next game.
The goal is not a perfect player. It is a player who can read her own game, and who keeps asking what the story left out.
Her story is not only about soccer. We all take in more than we have time to make sense of, and when there is only time for coherence, we get stories that feel like knowing and hide what we don't know. More on that in the next post.
