What the Scoreboard Leaves Out About a Young Soccer Player

Introduction

On weekends, as parents drive home from a game, they tend to talk about the score, as a measure of how the afternoon went. It is just one number the game keeps, and because it is kept, many take it as the measure.

For a developing player, the score answers a different question from the one you are asking. The score records what happened to be countable today. It says very little about whether the player, or even the team, is becoming better. If you want to know how to tell if a young soccer player is improving, it is in four habits you can watch from the sideline, all of which the player can repeat on purpose.

This article is the longer version of the first issue of our newsletter. It adds the counting conventions behind each habit and two drills from the library that build the first two.

Why the score is the wrong instrument

Results are lagging indicators. They arrive after the work, they swing with the opposition, the referee and the weather, and a bad day and a lucky day can produce the same number. Touches, scans, decisions and weak-foot reps are leading indicators. They are the things a player did, they can be repeated tomorrow, and over months they move before the results do.

There is a second reason to be careful with results, and it is about time. Junior results are a weak guide to senior outcomes. The evidence for that is stronger than for most things in youth development, and our methodology is built on it: how a player does at fourteen tells you little about the player they are at twenty-four. Judging a young player by this season's results is like judging a house by the scaffolding.

None of this means the player should stop wanting to win. They should want to win, and the wanting is part of what develops them. The distinction is about who keeps which score. The player competes for the result. The adults around the player measure something else, and trust that the results follow when the something else moves.

How to tell if a young soccer player is improving: four things to watch

Each of the four below comes with a way to notice or count it. Two rules apply to all of them. First, count for one player, your own, and compare that player only with themselves a few months ago. A count that compares two children is not a development indicator; it is a ranking, and it will change how you watch and what you say. Second, keep the count to yourself unless the player asks. The point is to change what you watch, not what you say on the drive home.

One: how often the player looks up from the ball

A scan is a look the player chooses to take away from the ball while it is still on its way. Not a glance at the ball carrier. A look at everything else: the space, the nearest opponent, the teammate about to move.

It is countable. One reception, one question: did the head turn away from the ball before the ball arrived? A scan somebody prompted counts to begin with; the aim is one nobody asked for. Players who scan have information before they have the ball. Players who do not scan gather it after the ball arrives, which is when the pressure is on, and they get described as slow to decide when the truth is that they looked late.

Also notice how often the game gave the player a chance to scan at all. A player who received the ball four times in a half has not had many chances to show the habit. That is a fact about the role and the game, not about the player.

The drill that builds this is the first one in our library, Scan-Decide-Receive (Two-Cone). Two players, one ball, a cone either side. The receiver has to look over both shoulders while the ball travels, because the first touch has to go toward one cone and the look is the only way to choose. It engineers the scan instead of shouting for it. If you want the habit explained in a game context, scanning while dribbling follows it through one professional's game.

Two: what the first touch makes possible

Watch what the touch made possible, not whether it looked clean. A clean touch that stops the ball under the feet with a defender arriving has just closed the next action. A slightly heavy touch that escaped the press has just opened one.

The counting convention here is the quality touch, which we define by intent: did the touch do what the player meant it to do? Intent belongs to the player, so the honest count is theirs, made in self-assessment, with a coach calibrating. From the sideline your part is the body before the ball arrives. A player about to take an intended touch is usually half turned before it gets there, hips open, able to go more than one way. A player square to the passer can only stop the ball or play it back.

The library drill is Directional First Touch (Three-Zone Receive). A served ball, three zones in a Y, and the zone is called at the moment of delivery, so the body has to be open before it knows where the ball is going. It runs with a partner or alone against a wall, both feet, and it counts the touches that missed the zone, which makes the player their own honest scorer.

Three: decisions under real pressure

A player who attempts the right pass and fails is learning something the player who makes ten safe passes backward is not. If the only thing that gets rewarded is the completion, the player learns to protect the completion, and that is how fear gets coached into a fourteen-year-old without anyone meaning to.

This one is harder to count and the convention says so: a decision moment is a possession where the player had more than one real option and chose before acting, and it is counted afterwards, on reflection or on video, not guessed from the sideline. So do not count it live. Notice it. When the player tries the harder option and it does not come off, that is the moment to say nothing on the drive home, or, if they raise it, to ask what they saw. The attempt was tuition. The environment decides whether the lesson gets extracted or hidden, and a parent's face after a failed through-ball is part of the environment.

Four: the week around the game

Sessions are perhaps a few hours a week. Development runs all week. Sleep, free play, individual practice, another sport: the environment around the player is training whether anyone calls it that or not, and most of it is built by parents.

Three of these are countable in the simplest way. Sleep: on how many nights this week bedtime landed inside roughly the same hour. Regularity is the point, not perfection. Free play and individual practice: whether they happened this week, for how long, unstructured, with no adult directing them. None of it needs an app. All of it says more about the years ahead than Saturday's score does.

What to do at the next game

Pick one of the four. Pick one player, your own, and one half. Watch for that one thing and nothing else. Do not count touches, passes or goals. If it is the scan, keep a tally. If it is the touch, watch the hips before the ball arrives. If it is decisions, notice the attempts. If it is the week, count the nights before the game, not the minutes in it.

Then do the same thing next month, for the same player. The number means nothing compared with another child and something compared with the same child in the spring. Over a season it becomes a scoreboard that actually says something about development.

If you want to give the player something to do with this, the drill library is built on the same four habits and filters by age band and by the space you actually have. And if the club has started talking about positions, develop the player, not the position explains why the four habits come first.