The Empty Report and the Analyst's Discipline

The Empty Report and the Analyst's Discipline

On Tuesday night I opened the match folder and found exactly one thing inside: 0 bytes. No clips, no rally-by-rally score sheet, not a single note from the camera operator. Four days earlier I had been handed the tactical breakdown of a quarter-final. Four days later I closed the draft and typed the first line of the report: not enough data to reach a conclusion.

This job taught me that sentence is harder to write than any compliment. A piece saying “Team A pressed well” always has a place and always finds a nodding reader. A piece saying “I cannot say anything yet” has no clean headline, no pre-cut clip, nobody to share it. Between those two choices, only one still holds value after the final point.

In a televised table tennis match, the camera has room for one ball and two paddles. What the audience receives is forty seconds of highlights, one coach's line after the match, and a ranking table updated every week. The table states a position, not a method. A player ranked twelfth may have climbed on service points won outright, or on long rallies past the fifth stroke. Both roads lead to the same line of text, and they lead two entirely different athletes there.

That is why I do not write when four groups of data are missing. Service points won must be split from receive points won, because a player can win seven of ten service points and still lose the match once the receiving half collapses. Rally-length distribution answers another question: how many points end within one or two strokes, how many stretch past the fifth. Win rate at deciding points, from nine-all onward, shows who keeps a steady hand in the tightest moment. And the receiving position plus the first footwork step after the ball leaves the opponent's paddle is the last thing I pull out of the raw footage.

Those four groups turn a meaningless sentence into a diagnosis. When two players leave the table with the same scoreline, two scripts may be running at once and the score sheet cannot tell them apart. The first player loses points in long rallies: past the fifth stroke the feet slow, the backhand falls short, and the long-rally win rate drops below four in ten. The second player loses points inside the first three strokes: the serve is read, the third ball is blocked, and the service-point win rate sits near half. The same scoreline can hide two completely different illnesses, and the score sheet cannot tell them apart. Next month's training plans for these two cannot be swapped: one needs endurance and footwork, the other needs service quality and a better third ball.

The map of a table tennis match does not live in the scoreline, but in the strokes the camera forgets. That is the gap between two contacts with the table, when a player rotates and picks a position. The camera has already moved on. The score sheet keeps no record. Only raw footage, uncut, without music, holds it.

When the match folder is empty, I have to process a different kind of information. An empty file is itself data: it says the recording chain broke, not that the match was empty. Those two facts have different consequences. If the match was empty, I wait. If the recording chain broke, I call the operator, ask for the original tape, and only then sit down at the desk.

This industry rewards certainty. A commentator who speaks firmly and gets it wrong still gets invited back next week. A commentator who says “not enough data” is read as lukewarm. I once sat in a meeting like that, and I did not argue. I waited until the footage arrived, then answered with a map. The work speaks for the person who made it.

I do not believe in a random point. Every point is a link in the chain of strokes before it — the stance, the spin direction, the adjusting step, the decision to hit the middle of the table or the open corner. The chain is long or short depending on the match, but it always exists. The analyst's job is to count it, not to guess it.

Empty stands turn a court into a laboratory. In that silence I could hear the ball meet the paddle and rubber grip the floor, sounds the usual roar covers up. I rebuilt the rhythm of the match and the tactical intent from audio, and for the first time I understood that data does not always arrive as a spreadsheet. It can arrive as an audio file nobody bothers to open.

But that audio is still data. It exists in a file, with a duration and a timestamp. An empty folder has nothing to listen to. The distance between those two situations is the entire border between analysis and invention.

What I took from Tuesday night sits in the process more than in any conclusion about the match. Before writing, I check three layers: is the raw footage in, does the rally-by-rally sheet reconcile, has the camera operator confirmed the duration. Miss one layer and the report stops at the line “not enough data to reach a conclusion.” Stopping there hurts more than writing something that sounds reasonable, but it keeps the next piece worth reading.

The match is over, but the record is still talking. That is what I keep for myself.

Next week's report will carry one new section: which data exists and which does not. Readers deserve to know how many square metres of evidence I stand on before they trust a conclusion. If that layer of evidence thickens round by round, a whole season will be read with different eyes — slower, closer, and much harder to fool.