Netball Statistics

Statistics in junior sport have a bad reputation, and some of that reputation is deserved.

Used badly, numbers become a stick. They turn a twelve-year-old into a shooting percentage, they reward the players who already get the ball, and they hand parents a spreadsheet to argue with you about on a Sunday morning.

Used well, they do something much more interesting. They show a quiet player that she made more interceptions than anyone on court. They show a coach that the problem is not the shooters, it is that the ball never arrives in the circle in a usable position. They turn "I think we're improving" into something you can actually see across a season.

The difference is entirely in what gets measured and how it gets presented.

Every design decision on this comes back to one constraint.

Whoever is capturing the data is also doing something else.

They are coaching, or scoring, or managing a bench, or shouting encouragement, or dealing with a child who has just realised her shoelace is undone at the worst possible moment. They have one hand, poor light, occasionally rain, and about two seconds of attention per event.

That rules out most of what a normal sports app would do. No dropdowns. No modal dialogues. No "select player, select action, select outcome, confirm". No typing.

What is left is a very short list of enormous, unambiguous, thumb-sized taps, and a ruthless attitude to how much is worth capturing at all.

If a statistic cannot survive that, it does not go in.

The temptation is to record everything. Every pass, every position, every touch.

That is how you end up with a system nobody uses after week three.

The more useful exercise is working backwards from the questions a coach actually asks at a quarter break:

Who is getting the ball, and who is not? Where are we losing it? Are the shots we are taking the shots we want to be taking? Is the centre pass working? Did that positional change do anything?

You can answer most of that with a surprisingly small number of tracked events. And a small number of events is the only kind anybody will ever manage to record while also coaching.

The second half of the problem is presentation.

A table of numbers is not insight. It is homework.

What a coach needs at a quarter break is one screen, three things, and no interpretation required. What a coach needs on a Tuesday evening is a sense of direction across the season. What a player needs is her own progress, framed as something she is building rather than something she is being marked on.

Those are three different views of the same data, and none of them is a spreadsheet.

I want to be precise about this, because it would be very easy to write this page as though the thing exists.

Built: nothing, yet.

Prototyped: nothing, yet.

Planned: the match-day capture model — the short list of events, the one-thumb interface, the quarter-break view.

Idea: season trends, individual player development views, and anything resembling a product.

What genuinely exists is the coaching experience that makes the problem obvious, an existing club platform that would be the natural home for it, and a fairly stubborn conviction that the constraint is the design.

That is an honest state of play. It is also usually the stage where the interesting decisions get made.

Test the capture model on paper before writing a line of code.

If a coach cannot record a quarter with a pen, a printed grid and no loss of attention, no amount of software is going to rescue it. If they can, then the app is just a faster version of something already proven to work — which is a far better position to build from.

Possibly. Every club I have been near has the same problem, and none of them have a budget for the solutions that already exist.

But it is a long way from "this would be useful at our club" to "this is a product", and I have watched enough people skip that gap to be wary of it.

For now it is a design problem I enjoy thinking about at the side of a court.