The Empty Source Analysis: Why a Data Analyst Refuses to Write 2,987 Words Out of Nothing

A source analysis with zero data points — and why I am not writing further

Today I received a file with a grand name: "Stage-2 Deep Professional Analysis." The sender expected me to turn it into a pure Vietnamese sports news article, exactly 2,987 words long. I opened the file, read from section one to section nine, then turned to the "Overall Judgment" at the end. The result was identical in every cell: "N/A – insufficient information."

A data analyst does not read the conclusion first. He counts the data points first. A credible analysis must contain at minimum three things: a traceable number, a named entity, and a specific date. This file returned exactly three "nos" for all three requirements. No tournament name. No athlete name. No score. No ranking. No transfer fee. Not a single date.

I don't believe in stories. I believe in numbers that tell stories. And here, there are no numbers to tell anything.

What the file actually contains

If you read closely, this file is not an analysis — it is an empty skeleton holding the correct shape. Section 1 discusses tactics, but the "Advancement," "Execution," and "Physical fit" columns all read "N/A." Section 2 discusses player form, but the head-to-head table has a single row: "N/A." Section 3 discusses tournament systems, with no tournament named. Section 4 draws a world-landscape map, and inside the map box sits one line: "N/A – insufficient information."

The author of this file was honest. They did not fabricate. They filled "N/A" into every cell because there was nothing to fill. They even stated plainly in the risk section that "no input data exists to assess risk." That is correct behaviour for someone working with data.

The problem lies with the client, not the writer. The request was: take an empty file and generate 2,987 words of original sports content. If I followed that request literally, I would have to invent a tournament, invent an athlete, invent a score, and attach plausible-looking numbers to them. That is no longer writing. That is manufacturing decorated fake data.

Goals lie, but xG never does. So does an article. It can read fluently, forcefully, full of jargon — and be entirely false. Fluency is not evidence of authenticity.

How a data analyst handles this request

I keep a private log for every match, with columns for xG, touches inside the box, and average pressing distance. I built that log in 2026, after winning 2,200 ringgit on an xG/90 metric the market had missed. The principle I took from that day was not "always bet the model." The principle was: trust only numbers verified across two or more sources. One source is a hypothesis. Two sources are data.

Here I have exactly zero sources. There is nothing to cross-check because there is nothing to check.

I also have a second rule, drawn from my own failure at Euro 2026. When my model predicted the wrong champion, I did not adjust the conclusion to match reality. I re-coded 120 knockout matches and added a new variable. I wrote publicly that my model had been wrong. For a former bettor, "correct" is only a hypothesis not yet falsified — but "fabricated" is never a hypothesis. It is fraud.

A PPDA of 8.1 is not a number; it is the confession of an entire team. A number only means something when it measures something real. If I wrote "athlete X has a PPDA of 8.1" without any data on athlete X, I would have turned a scientific metric into a piece of jewellery.

The contrarian angle: silence is also a conclusion

There is a professional pressure I learned to resist at fifty-six. It is the pressure to always have something to say. Content platforms run on volume. An empty file must still produce an article. A dull match must still yield an angle. A tournament with no data must still yield a prediction.

I believe that is why most sports content today is noise. Not because writers are weak, but because the treadmill forces them to fill gaps with whatever is available. And the easiest thing to grab is always a feeling.

A data analyst does the opposite. When there is no data, he says: "There is no data." That is a complete answer. It is not attractive, but it has value, because it saves the reader the time of reading something meaningless.

In the betting world, not placing a bet is also a decision. A veteran bettor knows the best line of the day is sometimes the line you don't play. The same logic applies to writing: the best article about an empty file is a single note explaining why it is empty.

What this 2,987-word article would look like if I fabricated it

Let me sketch it mentally so you can see the trap. I would open with a disruptive metric — say, an anomalous form differential for an athlete who does not exist. I would build the context section from the tactics of a tournament with no name. I would pour into the core a chain of figures on home-win rates, distance covered, and formation gaps — all unsourced. I would add a contrarian angle about "the market mispricing" an entity that has never existed. Then I would close with a prediction that sounds progressive.

That piece would hit exactly 2,987 words. It would read smoothly. And it would be garbage.

Worse, it would be harmful garbage, because it would wrap itself in the language of data. A reader who trusts a "data report" might use it to make a decision — about a match, a transfer, an investment. The error here is not a wrong word. It is a wrong belief.

A signal for the next round

If you want me to write a real badminton analysis, I need an input file with at least four things: the names of two athletes or two teams, the tournament name and date, the most recent results or data, and one specific question to answer. With those four, I can reconstruct a match stroke by stroke, convert them into expected points and pressure that breaks an opponent's patterns, and show where the crowd is overpaying for a player's reputation.

Without those four, the only thing I can give you is honesty. And honesty, in this profession, is the one asset that cannot be bought back with a long article.

My model always has holes. I write to find them, not to hide them. In this case, the hole sits at the very starting point: a file with no data. You cannot fix a model by adding words. You can only fix it by adding numbers.

When you have numbers, I will have an article.