Turning analysis into performance reports

Analysis that nobody acts on is not analysis; it is a document. The last and often hardest stage of performance analysis is communication — turning shortlists, dashboards and post-match packs into something a coach, a player or a board will actually read, understand and use.

This guide covers how analysts report their findings: what goes into a post-match pack, how a dashboard should be designed and how to communicate uncertainty without losing the message.

Knowing the audience

The same analysis has to be told differently to different audiences. A head coach wants a small number of actionable points tied to the next training session. A sporting director wants comparisons across players and matches. A board wants conclusions it can act on without needing a method lecture.

Good reporting therefore begins with an audience decision, not a data decision. The analyst asks who is reading, what decision they face and how much detail they can absorb, then chooses what to include. Reporting everything is a way of deciding nothing.

The post-match pack

A post-match pack is a short, structured document that summarises a game. It usually combines a handful of key metrics with selected clips and a written interpretation. The metrics give the shape of the match; the clips show the moments that explain it.

The discipline is in the selection. A pack that lists every metric buries the message. A pack that chooses three or four themes — how the press worked, where the space was, how the chances were created — gives the reader something to hold. Restraint is the analyst's most underrated skill.

Designing a dashboard that reads clearly

Dashboards fail in predictable ways: too many charts, no hierarchy, and values without context. A good dashboard answers a specific question with a small set of visuals, each labelled so that a reader knows what the number measures and how to read it.

Comparisons need a baseline. A number on its own says little; the same number next to a league average or a season trend becomes information. Analysts therefore build reference points into their visuals, so the reader sees not just the value but where it sits relative to something meaningful.

Communicating uncertainty honestly

Analysis deals in probabilities and small samples, and a report that ignores this misleads by omission. A short run of good results can look like a trend; a single strong match can look like a transformation. The report has to say so.

The practical approach is to state the sample, describe the strength of the evidence and separate observation from interpretation. "In the last five matches the team pressed higher" is an observation. "The team has changed its approach" is an interpretation that the sample may or may not support. Keeping the two apart is what makes a report trustworthy.

Principles of a usable analysis report

These habits turn findings into something a decision-maker can act on.

• Start from the audience and the decision at hand.
• Choose a small number of themes rather than listing everything.
• Pair numbers with clips that explain them.
• Always show a baseline for comparison.
• State the sample size behind every claim.
• Separate observation from interpretation explicitly.

What makes a report actionable

Reports succeed or fail on how they are shaped. The bars indicate the relative contribution of each quality to a report being used.

Tailoring the report to the reader

The same evidence is packaged differently for each audience.

The best analysis is falsifiable. A report that states its sample, its method and its uncertainty can be checked and challenged, and that is what makes it trustworthy.

Tooling matters less than process. Clubs that agree on what they measure, how they tag it and how they present it outperform clubs that simply buy more software.

Everything a workflow measures is a decision about what mattered. Those decisions deserve to be made deliberately rather than inherited by accident from whatever tool was installed first.

The output of analysis is a change in behaviour, not a document. If nothing changes on the training pitch, the workflow has not finished its job.

Analysts work in the gap between what the data proves and what the coach needs to know. Closing that gap honestly, without overclaiming, is the whole craft.

Analysis workflows are only as good as their consistency. A process that changes every week cannot produce comparable evidence, however sophisticated each individual step may be.

Reporting is the last, decisive step

A finding that never reaches a decision has no effect. Reporting well means choosing the audience, reducing the message to what it can carry and being honest about what the evidence supports. Do that, and the analysis stops being a document and starts changing what happens on the pitch.