Why inFORM Metrics Measures More Than Technical Ability

A player receives the ball near the touchline, takes a heavy first touch and loses possession.

From the sideline, the problem looks obvious.

First touch.

That might be exactly right. The player may need more work on receiving technique, body shape or how they prepare the ball for the next action.

But it might also be the wrong conclusion.

Maybe the player never checked their shoulder before the pass arrived. Maybe they received square when they could have opened their body. Maybe the defender arrived faster than expected. Maybe the player was tired. Maybe they knew what they wanted to do but hesitated under pressure.

The visible mistake was technical.

The cause may not have been.

This is one of the reasons inFORM Metrics looks at player development across four connected areas: Mindset, Technical, Tactical and Physical.

I did not want to build a system that told a coach, "This player has a first-touch problem," simply because the ball got away from them.

I wanted something that helps the coach preserve enough evidence to ask a better question:

What is actually causing the problem I am seeing?

Football actions rarely happen in isolation

Coaches naturally break the game into parts because we have to.

We work on first touch. Passing. Finishing. Scanning. Positioning. Speed. Agility. Confidence. Decision-making.

That helps us teach.

But the player does not experience the game as separate categories.

They experience one moment.

Take receiving under pressure.

The player may need the technical ability to control the ball cleanly. They may need the tactical awareness to scan and recognise the pressure before the ball arrives. They may need enough physical balance and movement quality to adjust their body. They may also need the confidence to demand the ball again after losing it two minutes earlier.

All four can affect the same action.

That matters because the coaching response changes depending on what is really happening.

If the problem is technical, more receiving practice might help.

If the player is not scanning, more isolated receiving repetitions may simply give them more practice solving the wrong problem.

If fatigue is affecting execution late in sessions, the first touch may look worse even though the underlying technical ability has not changed.

If hesitation appears only under pressure, the coach may need to understand why the player is becoming cautious before deciding what to train next.

The outcome gives us a clue.

Context helps us interpret it.

The danger of the single explanation

One of the easiest traps in coaching is to see the same outcome repeatedly and assume it always has the same cause.

A player loses the ball.

Poor technique.

A player stops making forward runs.

Poor effort.

A player makes a safe pass.

Poor decision-making.

A player fades late in a match.

Poor fitness.

Sometimes those explanations are correct.

Sometimes they are not.

The problem is that once we settle on an explanation, we naturally start noticing evidence that supports it.

If I decide a player lacks confidence, every hesitant action can start looking like proof.

If I decide a player has poor game understanding, I may interpret mistakes through that lens even when the real problem is execution.

Good coaching requires us to keep testing our own assumptions.

I think of this as the Connected Cause Test.

When an action keeps breaking down, ask four questions:

1. Technical: Can the player execute the action?
2. Tactical: Did the player recognise the situation and choose appropriately?
3. Physical: Did the player have the movement capacity to execute what they intended?
4. Mindset: Did confidence, resilience, communication or response to pressure affect the action?

The point is not to force every mistake into all four categories.

The point is to stop treating the first visible explanation as the only possible one.

Technical development still matters enormously

There is a reason technical work is such a major part of youth soccer.

Players need the ability to receive, pass, finish, carry and manipulate the ball.

If a player cannot execute the action, tactical understanding alone will not solve the problem.

That is why inFORM Metrics includes technical assessments.

But I am careful about what I expect a technical assessment to tell me.

Suppose a player completes a First Touch assessment and shows improvement over time.

That is useful evidence.

It suggests something about how their execution is developing in the assessment environment.

Now I compare that with what I see in training and matches.

Are they receiving more cleanly under pressure?

Are they setting the ball into better spaces?

Are they more consistent when the pass arrives at different speeds or angles?

Are they making the next action sooner?

If the assessment and coaching observations point in the same direction, my confidence grows.

If they do not, that is not a failure of the assessment.

It is a coaching question.

Maybe the player can execute the technique but struggles to recognise pressure early enough. Maybe they need more game-context practice. Maybe their execution changes when they are fatigued.

A useful measurement should help the coach investigate.

It should not end the investigation.

Tactical understanding changes what technical ability looks like

A player's technique can look completely different depending on what they know before the ball arrives.

Consider two players receiving the same pass.

The first player scans twice before receiving. They know a defender is closing from behind and a teammate is available inside. Their first touch takes the ball away from pressure.

The second player receives without scanning. The defender arrives, the player panics and their first touch runs loose.

If we only look at the result, we may say one player has better first touch.

Maybe they do.

But the first player's tactical preparation also created better conditions for the technical action.

That is why tactical development matters when interpreting what happens on the ball.

Scanning, positioning, support angles, recognition and decision-making can all change the difficulty of the next technical action.

As coaches, we already understand this.

The challenge is preserving enough of those observations over time to see whether the pattern is consistent.

One poor decision tells me very little.

Repeated evidence across different sessions tells me much more.

Physical development can change the same player

Young players are constantly changing physically.

They get faster. Stronger. More powerful. More coordinated.

They also go through periods where movement becomes less comfortable.

Anyone who has coached teenagers through a growth spurt has seen a player look completely different for a while.

A player who was sharp over the first few metres may suddenly look awkward.

A player who usually changes direction smoothly may need time to adapt.

A player who was technically clean may temporarily struggle to coordinate movements that used to feel automatic.

Without context, it is easy to interpret that as regression.

Sometimes it is.

Sometimes the player is simply adapting to a body that has changed.

Physical information does not explain everything, but it gives the coach another part of the picture.

The same is true with endurance.

If decision-making and technical execution drop late in sessions, I want to know whether fatigue may be contributing.

That does not mean every late-session mistake is a fitness problem.

It means physical development belongs in the conversation.

Mindset is visible in behaviour

Mindset is probably the easiest area to talk about vaguely.

We say things like:

"Great attitude."

"Needs more confidence."

"Has to be mentally stronger."

Those phrases can feel meaningful while telling us very little.

What I care about is the behaviour behind them.

After making a mistake, does the player ask for the ball again?

When challenged with something difficult, do they keep attempting it?

How do they respond to feedback?

Do they communicate when the game becomes uncomfortable?

Do they take responsibility for decisions?

Do they become more willing to try something they previously avoided?

Those are observations a coach can actually work with.

They also become more useful over time.

A single moment of frustration does not define a player's resilience.

A quiet session does not define their confidence.

But recurring behaviour across different situations can tell us something worth exploring.

This is why I do not want mindset reduced to a label.

The point is to give coaches enough structure to preserve what they are seeing, then let coaching judgment do the interpretation.

One outcome, four possible explanations

Imagine a winger repeatedly checks back instead of attacking the fullback.

It would be easy to call that a confidence issue.

But let us run the Connected Cause Test.

Technical: Does the player have the ball control and dribbling ability to attack at speed?

Tactical: Do they recognise when the defender is isolated and when the space is actually available?

Physical: Do they have the acceleration to exploit the gap once they create it?

Mindset: Are they reluctant to risk losing the ball because of a recent mistake, coaching instruction or fear of making the wrong choice?

Now the coaching conversation is better.

Maybe the player does need confidence.

Maybe they are making the correct decision because there is no support around them.

Maybe they know exactly what they want to do but cannot create separation physically.

Maybe they need technical work receiving on the move before they can attack the defender effectively.

The visible behaviour stays the same.

The development need changes.

The goal is not more data

This is important.

I do not think coaches need endless information.

Most of us already have more information than we can comfortably use.

The goal is better understanding.

That means capturing only the evidence that helps answer coaching questions.

If I am trying to understand why a player struggles under pressure, I do not need fifty unrelated numbers.

I need the observations and assessments that help me see the pattern.

What happens before the action?

What happens during it?

Does it change when the player is tired?

Does it change after mistakes?

Is the issue improving?

Does it appear in training, matches and assessments?

The value comes from connection, not volume.

That is how I want inFORM Metrics to work.

What a connected player picture gives the coach

When Technical, Tactical, Physical and Mindset information remain connected to the same player over time, several useful things can happen.

A coach can see whether different pieces of evidence support the same conclusion.

They can notice when one area may be influencing another.

They can avoid overreacting to a single bad performance.

They can revisit earlier observations instead of relying only on memory.

They can explain development to a player or parent with more context.

They can pass useful history to the next coach without telling that coach what they must think.

Most importantly, they can choose the next coaching action with a clearer understanding of why it matters.

That is the point.

Not to categorise the player.

To coach them better.

The four pillars should create questions, not labels

I never want a player to become:

"Strong Technical, weak Mindset."

That is too simplistic.

Players are not dashboards.

They are young people learning a difficult game in changing environments.

A useful development system should preserve complexity without making coaching more complicated.

For me, the four pillars do that by creating a better set of questions.

What can the player execute?

What do they recognise?

What can they physically support?

How do they respond when the game becomes difficult?

Then we keep watching.

Because the answer can change.

The player who lacked confidence in September may be demanding the ball by January.

The player who struggled technically may improve enough that the next limitation becomes tactical.

The player who looked slow may simply have needed time to adjust physically.

Development moves.

Our understanding has to move with it.

Why I built inFORM Metrics this way

When I first started thinking about inFORM Metrics, it would have been much easier to build a collection of tests.

Run the assessment.

Record the score.

Compare the result.

Move on.

But that never matched how I actually coach.

I do not look at a player and see four separate columns.

I see one player.

I see what they can do, what they understand, how they move, how they respond and how all of those things change depending on the situation.

The four pillars are there because they help preserve that whole-player view.

They give structure to the evidence without pretending the structure is the player.

And they make it easier to return to the question that matters most:

What does this player need next?

That answer may come from a technical assessment.

It may come from a tactical observation.

It may come from something physical.

It may come from a behaviour the coach has noticed repeatedly.

Most of the time, the strongest answer comes from connecting more than one of those things.

That is why inFORM Metrics measures more than technical ability.

Not because more measurements are automatically better.

Because player development is connected.

The better we understand those connections, the better chance we have of coaching the player in front of us.

Make Development Visible.