Null Result: When a Vietnamese Basketball Analyst Chooses Silence Over Fabrication

Late at night in a sports newsroom in Hà Nội, the editor called me over: "The analysis sheet you sent is blank. Write something — readers are waiting." I looked again at the file I had just opened: the field-goal percentage column empty, the overtime metrics left blank, the lineup identification section without a single line. The source input genuinely had nothing to read.

The choice was clear. Either invent a plausible-sounding story, or return a null result and take the scolding. I chose the second.

This is not rare in sports data analysis. A standard analytical process has two steps. Step one deconstructs the source: identifying teams, players, coaches, events and timestamps. Step two is the deep analysis across dimensions, from tactics and individual data to team operations and tournament context. If the first step returns an empty table, the second has nothing to hold on to. Any conclusion drawn from there is a product of imagination.

For Vietnamese basketball, this is a constant problem. The VBA, the national professional basketball league, has grown strongly in presentation. But the data infrastructure remains thin. Many games lack a full set of advanced metrics. Player tracking data is almost unheard of. Metrics like eFG% or possession rate per quarter sometimes have to be recalculated from raw box scores. When the source is that thin, the writer's greatest temptation is to fill the gap with feeling.

I know that feeling better than most. In 2026, I wrote that Hanoi FC deserved to win 3-1 rather than scrape a lucky 1-0 against Quảng Nam, based on an xG of 2.87 versus 0.45, 68% possession and fourteen shots inside the box. The piece was mocked because "football is not mathematics". A week later, coach Chu Đình Nghiêm admitted he had rewatched the tape and adjusted his tactics based on that analysis. That night, the media called them soulless. xG said otherwise, and I chose to trust xG.

But it was precisely those wins with data that taught me the opposite lesson: knowing when data is not enough.

A null result, after all, is still a result — as long as it is drawn honestly. In basketball analysis, three situations force a null result.

First, the source has no entities. If no team, player or coach is named, any tactical analysis — Pick and Roll, Small Ball or Drop Coverage — is meaningless. You cannot evaluate a system without knowing whose system it is.

Second, the sample is too small. Basketball is a game of large samples. A player shooting 5/7 across two games is not a good shooter; that is noise. To speak of real efficiency, you must look at eFG%, TS%, and usage rate to separate impact from opportunity. Without those numbers, a verdict is just opinion dressed as statistics.

Third, the context is unclear. The same metric means different things against a dense or light schedule. Ignoring context is the fastest way to turn data into a false prophecy.

These three situations are real. In 2026, I built a prediction model for a major tournament based on accumulated xG and control metrics, confidently concluding that a team would advance from its group. That team was eliminated. In hindsight, the model was missing a key variable: the PPDA index reflecting the opponent's pressing intensity, which lay outside the dataset I had gathered before the tournament. I concluded while the data was incomplete. The price was three months rebuilding the entire system.

Since then, every analysis I write carries a mandatory section: "risks and gaps". That section exists for a reason. Every model has a border, and an honest writer must draw that border before readers stumble into it.

The counterintuitive part is this. In a sports press that runs on emotion and clickbait headlines, refusing to conclude is the strongest statement of all. Saying "not enough data" is harder than saying "this team will be champion". It does not give readers what they want, but it gives them what they need: a line between what is known and what is being guessed.

In Vietnamese basketball, the pressure is even heavier. One big game, one buzzer-beater, and the whole online community already has its conclusion. The analyst is pushed into picking a side. But numbers never need us to defend them. On the contrary, we need them so we do not deceive ourselves. When the data is silent, the most honest way to speak is to be silent along with it.

Someone will ask: then what is the analyst for? The value of an analyst lies not in always having a conclusion, but in knowing which conclusions have enough basis to be made. When the stands were empty, my model collapsed. I knew I had forgotten the human factor. That lesson only came from accepting that a model can be wrong. I do not believe in hunches. But I believe in whatever data confirms a hunch to be.

Going forward, as the major season approaches and public opinion heats up, I will keep an empty data file beside every piece I write. It reminds me that a model's limit is not a weakness but part of its accuracy. The question is not what we know, but whether we have enough to speak. When the answer is no, writing a null result may be the most correct thing an analyst can do.