When the Scorecard Is Blank: Lessons from an Analysis Without Data

I used to sit in the stands, shouting the names of stars. Now I sit in front of a screen, naming every gap. There was a night in Guangzhou when I opened a table tennis technical analysis file sent by a data team. The file was over a dozen pages, divided into nine sections, covering everything from technical-tactical analysis to industry transmission. But when I scrolled to the first line of the content section, everything was the same abbreviation: N/A. No data points, no player names, no match, no dates, no source. A perfect skeleton, clean, and empty. I sat still for about three minutes. Then I started reading it the way I read a match. Because in my profession, an empty data file is not a technical glitch. It is a warning. The first thing that file taught me was about the limits of structure. Nine sections, each with tables, columns, rows, confidence labels. If you only look at the form, it looks exactly like a professional report. But table tennis is not played with spreadsheets. Table tennis is played with a heavy backspin serve at 9-9, with a cross-court step to save a ball, with the breathing of an athlete after the seventeenth stroke. When all of that is replaced by empty symbols, what remains is not analysis. It is a clothes rack with no clothes. In eight years of following tournaments, I have seen many reports like this. They usually appear in two places: in internal briefing sessions where no one dares to say "we don't have the data yet," and in analyses written by people who never watched the match. Both share one characteristic: they look very much like the truth. The Guangdong U19 boy back then didn't need anyone to teach him how to play; he needed someone to believe he dared. I think that story applies to data too. A dataset doesn't need anyone to teach it how to look good. It needs someone brave enough to say: this is not enough, no conclusion can be drawn. The second thing that file taught me was about honesty in language. When an analyst has no data, there are three ways to respond. The first is to invent a plausible conclusion, based on feeling and what "people usually say." The second is to stay silent and not submit a report. The third is to submit the report with the full framework intact, and state clearly on every line: insufficient information, cannot assess. The third way is the hardest, and also the only correct one. It requires the writer to endure the feeling of submitting a product that looks useless. But it protects the most important thing in this profession: the reader's trust. Once you have read a fabricated analysis without knowing it, you will doubt every other analysis. And once readers doubt everything, our profession is over. There was one detail in that file that made me pause the longest. In the overall risk assessment section, the author wrote: "There is no basis to rate risk; the input contains no subject matter." It was a very cold, very dry, and very correct sentence. It did not try to salvage the situation. It did not add a concluding paragraph to make the report look fuller. It pointed out the truth and stopped. I remembered a youth team training session I once filmed. The coach stood in the middle of the pitch, holding a printed tactics sheet, and said to the sixteen-year-olds: "Today we don't have a specific opponent. But we have legs. Use your legs first." He did not invent an opponent to analyze. He acknowledged the gap, then worked with what he had. That is exactly the lesson. An empty analysis is not a failure. It is a reminder that in sports, as in everything else, the order must be: observe first, conclude later. Never the reverse. But there is one thing I disagree with in how that file handled the situation. The file chose to stop completely. It suspended every section, labeled everything N/A, and returned it to the sender with a request to re-run the first step. In principle, that is correct. But operationally, it missed an opportunity. When there is no data about a specific match, there is still one thing to analyze: the gap itself. Why is the data missing? Because the transmission line from the arena to the center was cut? Because the tournament does not publish detailed statistics? Because the writer was not granted access? Because the match has not happened yet? Every answer to this question is valuable information, and every answer leads to a different action. A data gap caused by missing recording infrastructure is a systemic problem. A gap caused by a tournament withholding statistics is a policy problem. A gap caused by the analyst not watching the match is a professional discipline problem. Three completely different causes, three completely different responses, but if you only write N/A on every line, all three are flattened into one. In the commentary profession, I learned a principle from my mentors: when you don't understand why a stroke failed, rewatch that stroke ten more times before saying anything. But if after ten times you still don't understand, say that you don't understand. And state clearly how many times you watched. That number ten is the only data you have. The third thing that file taught me was about the relationship between structure and trust. A report with all nine sections filled but an empty core will make the reader feel cheated, if they only skim. A short two-paragraph report that clearly says "I don't have the data yet, here is what I need to get it" will make the reader trust you, because they know exactly where they stand. I think this is the lesson that the sports data industry in our region needs most right now. We are at a stage where everyone wants beautiful data tables, beautiful charts, proprietary metrics with impressive names. But those things only have value when behind them is a match that was actually watched, an athlete who was actually followed, a stroke that was actually recorded at a frame rate slow enough to see the contact point between the ball and the rubber. Without those things, every metric is just decoration. Back to that empty analysis file that night. I closed it and never used it for any article. But I keep it in a separate folder, named simply "lesson." Every time I prepare to write a new analysis, I open it for thirty seconds, then close it. Those thirty seconds are enough to make me ask myself: have I actually watched this match, or am I just filling in a frame? And that question, I think, is the question every sports writer should ask themselves every morning, before opening their computer. There is one thing I have not yet been able to answer, and I will leave it open here. If an analysis is methodologically correct, honest about its data, but brings the reader nothing new — simply because there is nothing to say yet — should it be published? Or is silence the most professional answer? I don't have the answer. But I know one thing for certain: any answer to that question must begin with acknowledging that the match has not been watched. Not with pretending it has. Table tennis, like every sport, does not forgive conclusions that arrive before observation. A topspin at 10-10 will not care how many articles you have written about it. It only cares how many times you watched it, at what speed, and how honest you were with yourself when you wrote down what you saw.