Zero Is Also an Answer: The Discipline of a Table Tennis Writer When the Evidence Disappears

11 p.m. in Chengdu, and the screen in front of me returns an empty file. Forty rows of a nine-dimension analytical framework, every cell reading "insufficient information". I have sat long enough in this trade to recognize the feeling: the keyboard still warm, the deadline close, and a very agreeable voice in my head whispering that I should just write something, that readers will never notice.

I turned that voice off. But I understand why it exists. A table tennis analysis without data can still read smoothly. A nine-dimension table filled to the brim looks perfectly professional. That is the biggest trap of writing with data.

The numbers spoke first, but people only listen once the truth has become legend. The problem this time is that the numbers said nothing at all. They went absolutely silent.

Context: when the data pipeline returns zero

I work with table tennis because it is a sport where data can explain almost everything. A topspin loop can be measured by spin rate. A serve can be broken into spin, placement and rhythm. A player can be described by a foreign-match win rate, a deciding-game efficiency, a world ranking position under WTT's rolling 52-week points deduction.

But data does not generate itself. It must be retrieved, cross-checked and verified. In a modern sports-news workflow, that is a multi-layer chain: source, extraction, analysis, conclusion. The first layer — extraction — can fail in three different ways that outsiders rarely distinguish.

First, the original article sits behind a paywall, gets deleted, or is truncated during collection. Second, the source exists but is empty of information — a snippet with only a headline. Third, the pipeline itself is broken: extraction received the article but pulled no entities from it.

The three cases look identical from the outside, with the same result: an empty file. But the handling differs entirely. The first two need a re-fetch; the third needs a technical fix. And none of them may ever be "written over" with imagination.

When the stadium is empty, data is the only spectator that never leaves its seat. But when the data itself leaves, all a writer has left is his own honesty.

Core: the discipline of not inventing numbers

I learned this lesson at a concrete price. In 2026, still a student of sports journalism, I had a dataset from 14 rounds of a lower-tier league. I found a young striker who had scored 7 goals but whose expected-goals figure reached 12.4 — he was missing far too many clear chances. I wrote a 2,000-word piece full of charts. The editor replied with one line: "This is a financial report, not a sports story."

I spent the next month re-watching every one of his moves, cross-checking against the data, to understand something simple: a metric only means something when it is told as a story. Since then, every piece of mine opens with a concrete moment on the pitch, then filters it through data. The number stands behind the person, not in front of him.

But there is a flip side I needed years to recognize. Once you know how to tell stories with numbers, you also learn how to disguise the absence of numbers. A smooth paragraph, a few vaguely remembered metrics, an eminently reasonable conclusion — and no one can verify any of it. That is the boundary between a data writer and a data forger, and it is thin enough that many cross it without realizing.

I set myself a rule I call the ninety-percent discipline. I only make a claim when the evidence reaches nine-tenths certainty. The remaining tenth may not become an assertion; it must open into alternative scenarios. With a player, that means I can say he is in decline if his last ten matches show it, but I may not say he will lose the next one. I draw maps; I do not order the traveler around.

When the spreadsheet returns zero, the ninety-percent discipline forces me to write "insufficient information" instead of a pretty number. Sounds simple. But imagine a newsroom's pressure: readers need articles, algorithms need content, and an empty cell looks like failure. In that moment, inventing a number is far cheaper than leaving the cell empty.

There is a professional paradox here. In table tennis, high-level data is scarcer than in football. There is no expected-goals metric for a single serve. There is no standardized transfer-valuation model for a player. Most of what we have is rankings, head-to-head records and raw match stats. Precisely for that reason, every datapoint we obtain is more precious, and every datapoint we fake is more dangerous.

Take WTT's rolling 52-week points deduction. A player's points do not accumulate infinitely; they roll forward in time. A star can appear to hold a ranking position while old points expire and new ones fail to arrive. If I write about a player without a detailed points ledger, I cannot say a word about his points-defence pressure. And if I pretend to have that ledger, I am deceiving readers with something that sounds highly technical.

The history of the rules teaches the same lesson. In 2026 the ball grew from 38mm to 40mm. In 2026 the format shifted from 21 points to 11. In 2026 the hidden-serve ban arrived. In 2026 solvent-based speed glue was banned. In 2026 celluloid gave way to plastic. Each milestone is a variable that changed how an entire generation's numbers should be read. But if my subject touches no specific reform, reciting that whole list is showing off, not analyzing. Data must anchor to an event, or it floats.

This is why I oppose the style I still see everywhere: taking a perfect analytical framework and filling it with entities that do not exist. A China-versus-the-rest comparison table, its cells painted with plausible-sounding figures. A list of "rising" players with no sources. The structure is correct, but the truth is absent. And in my trade, a correct structure with absent truth is the worst thing of all — it is deceptively trustworthy.

Transfer value does not lie. It merely stays silent until someone asks the right question. In table tennis, the right question is usually: where did this data come from, and can I verify it? If the answer is no, the only honest act is to stop.

The counterintuitive point: absence is also data

Here lies the angle I consider most important, and it runs against most writers' instincts.

An empty file is not a failure. It is information. It says the source was locked, or deleted, or the pipeline broke. These three diagnoses lead to three different actions, and all of them are more useful than a fabricated article. The absence of data, read correctly, is itself data about the system.

I once thought the data-analysis crowd was marching into the locker room, and in many cases that is true — in the bad sense. We bring in models, tables, conclusions detached from a player's real rhythm. But the paradox is this: when data is scarce, the person most likely to stumble is the analyst, not the coach. Because an analyst needs numbers to exist, and when there are no numbers, the temptation to manufacture them is enormous.

What I learned over years is to separate two kinds of gaps. The first gap is "not yet retrieved" — the source may exist, we simply need to try again. The second gap is "non-existent" — the source genuinely holds no information. For the first, the task is to re-fetch. For the second, the task is to close the file and mark clearly: there is nothing to analyze. Confusing the two is the origin of most fake-data sports content online.

An editor's praise dries up, but my spreadsheet stays full of words. I choose to keep a spreadsheet that is genuinely full of words, rather than filling a page with fake ones.

Signals for the next cycle

When an analysis file returns zero, I do not treat it as an endpoint. I treat it as the start of another process: re-check the source, re-assess the pipeline, and record how often this error occurs. If an error repeats, it stops being an accident and becomes a signal about the system.

Three scenarios for the coming data cycle, and I state my felt probabilities clearly. The most likely is that the source is recovered and the analysis runs in full. The second is that the source cannot be recovered and the file is closed. The less likely but most worrying is that the empty file goes out wearing the mask of a complete analysis.

Emotion writes the script; data writes the map. I only draw the map. And sometimes the most honest part of a map is a blank marked clearly as a blank, not a mountain drawn in to fill the space.

Based on my experience following table tennis matches and rankings, a blank correctly marked is worth more than ten numbers invented to look good. Readers can forgive a piece that falls short on word count. They cannot forgive a number that lies.